mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #120] Cloudflare DNS Lets Encrypt #106
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#106
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 @ikifar2012 on GitHub (Apr 18, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/120
Please add the ability to do a DNS challenge for lets encrypt
@rudyberkvens commented on GitHub (Apr 19, 2019):
I need this also. My ISP blocks port 80
@ikifar2012 commented on GitHub (Apr 19, 2019):
What ISP is that?
@rudyberkvens commented on GitHub (Apr 19, 2019):
SuddenLink
They also block 25 as well as others. They are not willing to unblock for me.
Thanks,
From: ikifar2012 notifications@github.com
Sent: Friday, April 19, 2019 3:15 PM
To: jc21/nginx-proxy-manager nginx-proxy-manager@noreply.github.com
Cc: rudyberkvens rudy@berkvens.us; Comment comment@noreply.github.com
Subject: Re: [jc21/nginx-proxy-manager] Cloudflare DNS Lets Encrypt (#120)
What ISP is that?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/jc21/nginx-proxy-manager/issues/120#issuecomment-485003316, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AF5DMUSGMFAFEXOFSFJSTL3PRIR43ANCNFSM4HGYXHMQ.
@jc21 commented on GitHub (Apr 23, 2019):
Time for a new ISP ;) Do they block 443 as well?
Check out #85 - it needs testing, you can pull the docker image for that PR and try
@rudyberkvens commented on GitHub (Apr 23, 2019):
Seems to be very common among residential ISPs. I wish there were other for me to pic from. No fortunately they leave 443 alone.
For now I’m manually requesting from https://www.sslforfree.com/ and importing into the proxy manager UI. It woks but not ideal.
From: jc21 notifications@github.com
Sent: Tuesday, April 23, 2019 4:25 PM
To: jc21/nginx-proxy-manager nginx-proxy-manager@noreply.github.com
Cc: rudyberkvens rudy@berkvens.us; Comment comment@noreply.github.com
Subject: Re: [jc21/nginx-proxy-manager] Cloudflare DNS Lets Encrypt (#120)
Time for a new ISP ;) Do they block 443 as well?
Check out #85https://github.com/jc21/nginx-proxy-manager/pull/85 - it needs testing, you can pull the docker image for that PR and try
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/jc21/nginx-proxy-manager/issues/120#issuecomment-485980801, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AF5DMUQYDHSPGDJDQAGOUFDPR55EJANCNFSM4HGYXHMQ.
@Deanosim commented on GitHub (Apr 25, 2019):
How do I go about testing this? I've pulled it but I don't know where to enter the the info for setting up dns requests via the cloudflare plugin.
@jc21 commented on GitHub (Apr 25, 2019):
According to the guy who wrote the PR, once you've pulled it you need to have your dns settings done and then go and add request a new LE cert from within the application. There's no new UI options.
@jc21 commented on GitHub (May 8, 2019):
Merged #85
@ikifar2012 commented on GitHub (May 9, 2019):
hey @jc21 hpw do I use the dns challange
@jc21 commented on GitHub (May 9, 2019):
The patch only tells letsencypt to search your dns settings for some authorization instead of inside the project via http. I personally don't use it but someone wanted it, made a PR, was told to test it and I didn't hear from them again so I merged it because it doesn't affect any pre-existing behavior.
@ikifar2012 commented on GitHub (May 9, 2019):
In order for Cloudflare to work you need a special package for certbot and it requires a cloudflare global API key
@OhHeyAlan commented on GitHub (May 11, 2019):
@ikifar2012 I’ll work on this tonight and try to submit a PR for it. Currently I use Certbot to generate a wildcard and install it as a custom cert.
@burkasaurusrex commented on GitHub (Jul 8, 2019):
FYI, it looks like Cloudflare posted a FAQ on this: https://support.cloudflare.com/hc/en-us/articles/214820528-Validating-a-Let-s-Encrypt-Certificate-on-a-Site-Already-Active-on-Cloudflare
@dcplaya commented on GitHub (Jan 10, 2020):
Is this working? I didnt see anything in the github wiki about it. I would love to use this but I need to have LetsEncrypt to auth with Cloudflare's DNS before I can switch over to it.
@rudyberkvens commented on GitHub (Jan 10, 2020):
I switched to using Let's Encrypt and NGINX Home Assistant SSL proxy add-ins in Home Assistant. These two together are working fine for me. Of course this wont help you if you are using this for something other than HA.
@dcplaya commented on GitHub (Jan 10, 2020):
I use HA but I also have about 15 other services running through my proxy. But I currently am unable to use this anyway, most of my services' ports are only opened to localhost and as far as I can tell, there is no way to have Nginx look at localhost of the parent machine and not the docker instance. So for now, implementing this is on hold.