mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #3063] Cloudflare DNS challenge request for SSL certificate failed #2082
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#2082
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 @Aqr-K on GitHub (Jul 17, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3063
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
Using versions
2.9.19,2.10.3, and2.10.3: PR-2971cannot apply for CloudFlare SSL certificates properly, and the applications forexample.comand*. example.comhave also failedNginx Proxy Manager Version
2.9.19
2.10.3
20.10.3;pr-2971
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Can apply for cloud flare certificate normally
Operating System
x86 Debian11
Additional context
Docker started ipv6, but the host only has ipv4. The container shows that it has bridging ipv4 and ipv6, and ports 80 and 443 of the public IP are banned by the operator.
Docker version: 20.10.23
2.10.3:pr-2971 letsencrypt-log
@lug-gh commented on GitHub (Jul 19, 2023):
This looks like an error on your end, not a bug, it works fine for me.
Please check your API token, it must have at least the permission "Zone:DNS:Edit" for the zone "example.xyz".
@Aqr-K commented on GitHub (Jul 19, 2023):
@lug-gh
This should be a bug.
Because I am using the
Global API Key, which can manage all domain names on my cloudflare, and theddnsservice on my router also uses this token without any issues.@lug-gh commented on GitHub (Jul 19, 2023):
It is still not a bug.
The plugin requires an API token, not an API key. The global API key only works together with your Cloudflare account email address.
Please create a token, using the global API key is a potential security risk.
https://certbot-dns-cloudflare.readthedocs.io/en/stable/#credentials
Your router appears to also hold your Cloudflare email. This works, but is not good.
@Aqr-K commented on GitHub (Jul 19, 2023):
I tried it on version
2.9.19and found that it is indeed not a bug.I used the wrong method, after generating a token for the domain name, using the token can solve the problem.
I think there should be many people like me, using
keyinstead oftoken, I have seen many similar cases in lssues, this is a good solution.@lug-gh commented on GitHub (Jul 22, 2023):
I also think that detailed documentation for actual use is missing from NPM. It is an open source project, so everyone can do their part. I could write a manual, but I don't know where exactly to place it or how to structure it.
Are there any plans or guidelines for this @jc21?
Edit: I think this issue can be closed. I just installed NPM version 3, it uses acme.sh and the UI is much more user friendly.
But I wonder why acme.sh requires the account ID and email, or if it is just a "wrong" implementation in NPM.
@z0sen commented on GitHub (Aug 2, 2023):
how to upgrade to v3?
@lug-gh commented on GitHub (Aug 2, 2023):
@z0sen There's no way to upgrade (yet), and v3 is still under development - and is far from stable ;)
#1202
@z0sen commented on GitHub (Aug 3, 2023):
Well, anyway, i have no problem with the latest version of v2 now