Skip to content
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

Open
martone65 opened this issue Mar 14, 2025 · 5 comments
Open

DNS Challenge Fail #4437

martone65 opened this issue Mar 14, 2025 · 5 comments
Labels

Comments

@martone65
Copy link

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes / No
  • Are you sure you're not using someone else's docker image?
    • Yes / No
  • Have you searched for similar issues (both open and closed)?
    • Yes / No

Describe the bug

When I go to pull a new SSL certificate from Cloudflare via DNS Challenge I get the following error:

CommandError: Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
Error determining zone_id: 6003 Invalid request headers. Please confirm that you have supplied valid Cloudflare API credentials. (Did you copy your entire API token/key? To use Cloudflare tokens, you'll need the python package cloudflare>=2.3.1. This certbot is running cloudflare 2.19.4)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.

    at /app/lib/utils.js:16:13
    at ChildProcess.exithandler (node:child_process:430:5)
    at ChildProcess.emit (node:events:518:28)
    at maybeClose (node:internal/child_process:1104:16)
    at ChildProcess._handle.onexit (node:internal/child_process:304:5)

I know my token is correct. I tested via curl.

Nginx Proxy Manager Version

v2.12.3

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

A certificate from LetsEncrypt

I am using Ubuntu 22 server.

@martone65 martone65 added the bug label Mar 14, 2025
@danielraffel
Copy link

danielraffel commented Mar 14, 2025

I’m experiencing the same issue.

1 similar comment
@MIAOBUSI
Copy link

I’m experiencing the same issue.

@conotoium
Copy link

conotoium commented Mar 21, 2025

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?

# Cloudflare API token
dns_cloudflare_api_token=**********************************************

And are you certain you setup the zone rules correctly?

@avilesj
Copy link

avilesj commented Mar 26, 2025

Same issue here. I even tried the global token.

@zefuros1991
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants