Closed elamje closed 8 months ago
This isn't possible due to how the plugin works. If you set a dns provider, then goacme/lego
(what we use under the hood) will use that to retrieve a cert for every requested domain. Dokku itself only uses 1 certificate per app when using the letsencrypt plugin + the default nginx router, so we wouldn't be able to accommodate different modes depending on whether the dns is possible to use for a given domain or not.
That said, Dokku's openresty plugin is probably more suited to what you want. It doesn't do dns-based certificate retrieval, but does just-in-time retrieval of certificates for any domain, meaning you don't have to run an extra command to get a cert.
If - for business reasons - you still want to use this app + a different certificate depending on the hostname being requested, consider sponsoring the work. I'm always happy to sit down with users to figure out how Dokku can better enable their workflows while improving the Dokku ecosystem.
Description of problem
For subdomain wildcarding, I must use
dokku letsencrypt:set --global dns-provider-CLOUDFLARE_EMAIL
and set the api key. This works great since I control the domain I need this on. However, for my business clients, I need to set up their websites to point to my same Dokku app.I can easily add their domain to my app, but when I need to add SSL, using this plugin, it tries to retrieve SSL certs via Cloudflare DNS authentication instead of standard HTTP auth.
How reproducible
Steps to Reproduce
1. 2. 3.
Actual Results
Expected Results
blog.myclient.dev
(non-wildcarded, client-owned) subdomainIt seems that this plugin has assumed that each app will EITHER use DNS auth OR HTTP auth for SSL validation.
Environment Information
dokku report listings
outputHow (deb/make) and where (AWS, VirtualBox, physical, etc.) was Dokku installed?:
Digital Ocean Droplet