mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #36] LE wildcard certs #31
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#31
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ZeroInputCtrl on GitHub (Dec 13, 2018).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/36
Does this container support using wildcards for the LE certs? Can it do the dns challenge for google? I looked through the images for the LE interfaces but i don't see anything that would allow this.
@jc21 commented on GitHub (Dec 13, 2018):
Unfortunately no. Because LE wildcards require DNS setups, I don't bother supporting them in this project. You can specify multiple domains for a single LE certificate however.
@ZataH commented on GitHub (Dec 21, 2018):
Will you support it at some point?
@koshia commented on GitHub (Dec 30, 2018):
I would like to +1 on this request; however low priority. @jc21 I do agree it lets you add multiple domains/sub-domains, but i believe you are still limited to 10 per 90 days, iirc. I'm already @ 8 subdomains and can see adding another 4-6 in the future.
@jc21 commented on GitHub (Jan 3, 2019):
The project's initial goal was to let beginners create ssl reverse proxies. Using LE wildcards requires that the app force users to leave it, add entries to dns, then come back and finish any setup. At this point, it doesn't feel "simple" and as such, very low priority for me.
@ZeroInputCtrl commented on GitHub (Jan 3, 2019):
That's true if you want to arbitrarily use wildcard certs. I use https://hub.docker.com/r/linuxserver/letsencrypt/ with the google plugin. You give the credentials, it passes those through to certbot and uses these scripts https://github.com/certbot/certbot/tree/master/certbot-dns-google to automatically create and destroy dns records in order to do dns validation for the wildcard certs. Maybe just the sites that have scripts to do these automatic records be a good start?
@jc21 commented on GitHub (Jan 3, 2019):
Yeah that's an interesting point. Supporting AWS and Google Cloud to begin with might be easiest. As long as the user understands the security implications of saving their service credentials and the UI process is simple.
@vrelk commented on GitHub (May 6, 2019):
Take a look at this project, either for collaboration or inspiration.
https://github.com/Neilpang/acme.sh
@jc21 commented on GitHub (May 8, 2019):
Refer to #85 and #120.
@toxic0berliner commented on GitHub (Aug 30, 2020):
sadly, neither #85 not #120 enable support for LE wildcard certificate.
I'd be very interested to have the gui to do this in nginx-proxy-manager, for the time beeing I cannot request any certificate for *.example.com since the ui doesn't let me, I've also seen some javascript alert message somewhere explicitely telling me it doesn't support it....
Any luck of reopening the issue and implementing it now that DNS challenge seems to be working ?