Let's Encrypt Cloudflare Provider

[SN4RK]

Describe the bug
I'm trying to get a Let's Encrypt certificate through DNS Provider Cloudflare. I created the token and entered it, in general, I did everything right. The problem is with certbot. I just downloaded NPM and didn't change anything. I use image in docker.

Nginx Proxy Manager Version
2.11.2

Screenshots

Operating System
Docker Desktop (docker compose)

Additional context
2024-05-16 09:46:20 self.cf = CloudFlare.CloudFlare(token=api_token)
2024-05-16 09:46:20 /opt/certbot/lib/python3.11/site-packages/certbot_dns_cloudflare/_internal/dns_cloudflare.py:107: PendingDeprecationWarning:
2024-05-16 09:46:20 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2024-05-16 09:46:20 !! You're seeing this warning because you've upgraded the Python package 'cloudflare' to version !!
2024-05-16 09:46:20 !! 2.20.* via an automated upgrade without version pinning. Version 2.20.0 exists to catch any !!
2024-05-16 09:46:20 !! of these upgrades before Cloudflare releases a new major release under the release number 3.x. !!
2024-05-16 09:46:20 !! !!
2024-05-16 09:46:20 !! Should you determine that you need to revert this upgrade and pin to v2.19.* it is recommended !!
2024-05-16 09:46:20 !! you do the following: pip install --upgrade cloudflare==2.19.* or equivilant. !!
2024-05-16 09:46:20 !! !!
2024-05-16 09:46:20 !! Or you can upgrade to v3.x. NOTE: Release 3.x will not be code-compatible or call-compatible !!
2024-05-16 09:46:20 !! with previous releases. To see more about upgrading to next major version, please see: !!
2024-05-16 09:46:20 !! https://github.com/cloudflare/python-cloudflare/discussions/191 !!
2024-05-16 09:46:20 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2024-05-16 09:46:20 self.cf = CloudFlare.CloudFlare(token=api_token)
2024-05-16 09:46:20 Some challenges have failed.
2024-05-16 09:46:20 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.

[gouthamravee]

I am getting the same error, nothing new to report other than my install isn't new.

CommandError: Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
/opt/certbot/lib/python3.11/site-packages/certbot_dns_cloudflare/_internal/dns_cloudflare.py:107: PendingDeprecationWarning: 
       !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!   WARNING  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
       !! You're seeing this warning because you've upgraded the Python package 'cloudflare' to version  !!
       !! 2.20.* via an automated upgrade without version pinning. Version 2.20.0 exists to catch any    !!
       !! of these upgrades before Cloudflare releases a new major release under the release number 3.x. !!
       !!                                                                                                !!
       !! Should you determine that you need to revert this upgrade and pin to v2.19.* it is recommended !!
       !! you do the following: pip install --upgrade cloudflare==2.19.* or equivilant.                  !!
       !!                                                                                                !!
       !! Or you can upgrade to v3.x. NOTE: Release 3.x will not be code-compatible or call-compatible   !!
       !! with previous releases. To see more about upgrading to next major version, please see:         !!
       !! https://github.com/cloudflare/python-cloudflare/discussions/191                                !!
       !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  self.cf = CloudFlare.CloudFlare(token=api_token)
/opt/certbot/lib/python3.11/site-packages/certbot_dns_cloudflare/_internal/dns_cloudflare.py:107: PendingDeprecationWarning: 
       !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!   WARNING  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
       !! You're seeing this warning because you've upgraded the Python package 'cloudflare' to version  !!
       !! 2.20.* via an automated upgrade without version pinning. Version 2.20.0 exists to catch any    !!
       !! of these upgrades before Cloudflare releases a new major release under the release number 3.x. !!
       !!                                                                                                !!
       !! Should you determine that you need to revert this upgrade and pin to v2.19.* it is recommended !!
       !! you do the following: pip install --upgrade cloudflare==2.19.* or equivilant.                  !!
       !!                                                                                                !!
       !! Or you can upgrade to v3.x. NOTE: Release 3.x will not be code-compatible or call-compatible   !!
       !! with previous releases. To see more about upgrading to next major version, please see:         !!
       !! https://github.com/cloudflare/python-cloudflare/discussions/191                                !!
       !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  self.cf = CloudFlare.CloudFlare(token=api_token)
Some challenges have failed.
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:519:28)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5)

[sdh91]

Same issue. Certificate generation and renewal appears to be broken because of this.

[tabishz]

yea I just got the same error here when generating a certificate using cloudflare DNS. I've create one the same way few days ago without any problem. On the same version of Nginx Proxy Manager. I'm using docker image jc21/nginx-proxy-manager:2.11.1

[ransbachm]

This is fixed in the dev branch, you can close the issue

#3763 (comment)

[phillf]

When will this be pushed to a release.

[github-actions]

Issue is now considered stale. If you want to keep it open, please comment 👍