mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #554] Letsencrpyt with DNS challenge #467
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#467
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 @jiatao99 on GitHub (Aug 12, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/554
I managed to make the WebGui works with letsencrypt with dns challenge. However, I found a bug in your
backend/internal/certificate.jsline 735:Those two line is unnecessary and should be removed because those two value can be specified in line 731:
'--config "' + le_config + '" ' +By just install the
certbot-dns-cloudflarein the docker build and modify the ini file with the above changes, I make the dns challenge works with existing GUI.I you want, I can create a branch and pull request for my changes.
Thanks for your great project.
@jiatao99 commented on GitHub (Aug 12, 2020):
Also is it possible to allow user to set renew interval (from configure)? It is now hard coded here
Since the cert expires every 90 days. Set it to 1 hour is way too much.
@cristiangauma commented on GitHub (Aug 20, 2020):
I would be really interested in this feature. Would the DNS challenge work for wildcard domains? (*.foo.bar)
@jiatao99 commented on GitHub (Aug 21, 2020):
yes. wild card letsencrypt work on my docker. But I must change their source code. It seems like the owner of this repo does not care about this feature.
@gregfr commented on GitHub (Aug 24, 2020):
I would love to be able to use wildcard certs automatically, because I use NPM for several servers reachable with the same name.
@micha1983 commented on GitHub (Aug 25, 2020):
would be cool if you share it. i'm also very interested in this feature. i also use cloudflare for DNS.
@jiatao99 commented on GitHub (Aug 25, 2020):
I am using a 3rd party docker image (from jlessage) which allows me to reference the cloudflare secret outside the docker. I shared the process here: https://github.com/jlesage/docker-nginx-proxy-manager/issues/101. Hopefully the owner of that project will provide a docker image which allows cloudflare or other dns plugins
@chaptergy commented on GitHub (May 9, 2021):
DNS challenges for many providers are available since mid to end of 2020, which should have also fixed this issue.