Issue with ACME-DNS: cannot use wildcard for a DNS-challenged cert

gctwnl

Member
Aug 24, 2022
78
12
13
I am running acme-dns to update the certificates in my landscape, I run my own acme-dns service and thus can get wildcard certificates. This means I can create certificates for subdomains that are locally known, but not on the outside. I just create a cert for '*.domain.tld'. These I use for the various internal systems and services.

I have successfully implemented this on macOS, OPNsense, Linux (with docker, where also my acme-dns service is running).

I am running into an issue when extending this to PVE: I cannot enter a wildcard domain. in the GUI under Datacenter->ACME->Challenge Plugins. But the name of the PVE server isn't known on the outside (and doesn't need to be). So, I was thinking about manually editing the plugin via the shell and changing the name from 'domain.tld' to '*.domain.tld', but I am unable to find where this is stored.

Is there a way I can manipulate this via the command line so that the cert is requested for a wildcard?
 
I suspect I can edit /etc/pve/local/config where now it says
Code:
acmedomain0: pve.domain.tld,plugin=pluginname
and I could edit that to become:
Code:
acmedomain0: *.domain.tld,plugin=pluginname

But given that I now first have to make sure the GUI works at all after my disastrous attempt to upload a cert, I cannot test that yet.
 
After investigating (i.e. reading perl files) it seems this is deep in proxmox and not easily circumvented. Hmm