-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DNS Challenge Fail #4437
Comments
I’m experiencing the same issue. |
1 similar comment
I’m experiencing the same issue. |
Not sure if I can help but I did a wildcard for my domain via Lets encrypt with cloudflare dns challenge and it worked perfectly? This is how I inserted mine?
And are you certain you setup the zone rules correctly? |
Same issue here. I even tried the global token. |
I am facing the same issue using NPM as LXC on my proxmox server, I ensured token is valid and active with curl, I also put adguard as DNS server for NPM and i see the DNS queries reach cloudflare. I changed back to my gateway as DNS after that same issue. Has anyone found anything yet? |
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug
When I go to pull a new SSL certificate from Cloudflare via DNS Challenge I get the following error:
I know my token is correct. I tested via curl.
Nginx Proxy Manager Version
v2.12.3
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A certificate from LetsEncrypt
I am using Ubuntu 22 server.
The text was updated successfully, but these errors were encountered: