mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #378] Add DNS-Challenge For LetsEncypt Cert #321
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#321
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 @MapGuy11 on GitHub (Apr 17, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/378
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When Getting a cert it's obviously going to block me since my ISP blocks 443,80, and 8080. Also when I do it on my own it won't input the files.
Describe the solution you'd like
A clear and concise description of what you want to happen.
I would like the choice if Lets Encrypt cert fails the first time it will ask if you want to try via DNS.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I haven't really found an alternative solution the only one is getting the cert from certbot yourself but then it won't input!
Additional context
Add any other context or screenshots about the feature request here.
I want to say thank you for this amazing piece of software!
@robertlynch3 commented on GitHub (Apr 29, 2020):
I am currently using Synology's reverse proxy feature because of how easy it is with Certs, its biggest flaw is I need to manually open port 80 and then close it when I am done, so auto-renew doesn't work. I run my things on port 8080 mainly for a little added security (I know that that isn't much) and because Synology can't do port 80 or 443, but it would be even better to DNS Challenges.
Ideally (and I know this varies depending on how a DNS providers API works) but Nginx-Proxy-Manager would have prebuilt code such that a user would just need to edit the API call in-order for the functionality to be automated.
@MapGuy11 commented on GitHub (Apr 29, 2020):
@rml596 I have found a really easy solution using https://www.sslforfree.com/ Then Getting a wildcard cert all you have to do is *.example.com to get a wildcard cert which is easy to have one cert to renew every 3 months. Then import manually.
@andriej commented on GitHub (Apr 30, 2020):
I really would like to see this feature with DNS-Challenge to not have to have port 80 forwarded.
@michis0806 commented on GitHub (May 12, 2020):
+1
a posibility to create wildcard-certificates with letsencrypt would be very useful!
@sea3pea0 commented on GitHub (Jun 5, 2020):
+1 for adding the dns-challenge method for issuing/renewing letsencrypt certs. My ISP blocks port 80 so http verification doesn't work for me
@Na0mir commented on GitHub (Jul 2, 2020):
+1 my ISP (all ISP in China) also block 80 and 443 ports, must use DNS challenge for Let's Encrypt
@chaptergy commented on GitHub (May 9, 2021):
This is possible since the end of 2020.