mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #4617] Cannot install certbot-dns-cloudflare==4.0.0 and cloudflare==4.0.* #2942
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#2942
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 @SadPepeIRL on GitHub (Jul 1, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4617
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
Unable to create SSL certification.
Nginx Proxy Manager Version
2.12.4
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Cert created, but I get error message:
Terminal shows:
Screenshots
Operating System
TrueNas 25.04.1
Additional context
YAML used:
I have also tried previous versions and I am still receiving the same kind of errors.
I have completely deleted my container and redeployed with no success.
@MiguelTVMS commented on GitHub (Jul 1, 2025):
Getting the same here
It also made the nginx server to spike on DNS queries to the domains, pypi.org and files.pythonhosted.org.
@Kptweedy commented on GitHub (Jul 1, 2025):
I also found out about this due to a massive spike in dns requests.
@frenzybiscuit commented on GitHub (Jul 1, 2025):
Confirming the issue.
@tn1-au commented on GitHub (Jul 2, 2025):
also confirming, i have the same issue.
cheers.
@ZEUSGMJ commented on GitHub (Jul 2, 2025):
Same issue here too!
@lscholte commented on GitHub (Jul 2, 2025):
Also hitting this. Had to downgrade to 2.12.3 to stop it from happening.
@PikachuEXE commented on GitHub (Jul 2, 2025):
Same issue as https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4606
@SadPepeIRL commented on GitHub (Jul 2, 2025):
Sadly I get this error on 2.12.3
EDIT: I just used a global API key and that allowed me to create an SSL cert.
@philosophics commented on GitHub (Jul 2, 2025):
Also got the same issue while it also destroyed the db. Can confirm, downgrading to 2.12.3 brought it back up and usable again.
@GD2021 commented on GitHub (Jul 2, 2025):
我也遇到了这个问题。
@gleechad commented on GitHub (Jul 2, 2025):
same issue.
@ShotokanZH commented on GitHub (Jul 2, 2025):
You can check the fix here:
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4606#issuecomment-3025013155
@silentoplayz commented on GitHub (Jul 2, 2025):
Confirming this helped alleviate the issue for me until a proper solution is provided in a future update.
@Kieros commented on GitHub (Jul 2, 2025):
same here downgraded as mentioned above solved all issues
@WeskerC commented on GitHub (Jul 2, 2025):
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.
not working for me after trying the #4606, above is the log
@ShotokanZH commented on GitHub (Jul 2, 2025):
Your error seems completely different, in my case there was pip in loop trying to install a wrong version of the cloudflare module.
Are you sure your configs are ok and were not somehow corrupted?
@WeskerC commented on GitHub (Jul 2, 2025):
@ShotokanZH I am not sure as I have downgraded to 2.13.3 and it works for now, I am solving other internal error issues at the moment TT
@busybody-sash-july commented on GitHub (Jul 2, 2025):
I confirm the bug also for me. Downgrade to 2.14.3
@SadPepeIRL commented on GitHub (Jul 2, 2025):
Sadly I can't get that to work within truenas :( Ended up downgrading and was able to get it to work.
@error420 commented on GitHub (Jul 2, 2025):
Same issue.
ERROR: Cannot install certbot-dns-cloudflare==4.0.0 and cloudflare==4.0.* because these package versions have conflicting dependencies.
@FedorAdo commented on GitHub (Jul 2, 2025):
Same issue.
@av1155 commented on GitHub (Jul 2, 2025):
Same issue, I cannot login, says bad gateway. All hosts are still working fine.
@TheIceMagmaCube commented on GitHub (Jul 2, 2025):
Solution : rolling back to jc21/nginx-proxy-manager:2.12.3 until further correction.
Worked for me.
@witch7685 commented on GitHub (Jul 2, 2025):
for docker: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4606#issuecomment-3025013155
@lynstrob commented on GitHub (Jul 3, 2025):
Same issue, rolling back to v2.12.3 worked.
@eallion commented on GitHub (Jul 3, 2025):
Same
@AcrimoniousMirth commented on GitHub (Jul 3, 2025):
Happened to me as well, updating to V1.2.4 on TrueNAS. Can't deploy the app at all now, meaning the NAS is offline.
Rolled back to V1.2.3 and didn't fix, interestingly. Will be investigating further.
@mathieumaf commented on GitHub (Jul 3, 2025):
Same issue
@flimofly commented on GitHub (Jul 3, 2025):
Did work for me on Truenas Scale Fangtooth 25.04.1
@AcrimoniousMirth commented on GitHub (Jul 3, 2025):
Follow-up to earlier. I ran this solution as suggested above and fixed for now, back to operational.
@Arimanio commented on GitHub (Jul 3, 2025):
Also confirmed.
UPDATE: Tried this single line fix from @ShotokanZH and it worked:
docker exec -it nginx sh -c "sed -i 's/cloudflare==4.0.*/cloudflare/' /app/global/certbot-dns-plugins.json" && docker restart nginx
(Replace nginx with the name of your container)
LOG ATTACHED:
[7/3/2025] [12:37:02 PM] [Migrate ] › ℹ info Current database version: none
[7/3/2025] [12:37:02 PM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-1' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo '# Cloudflare API token dns_cloudflare_api_token=- > '/etc/letsencrypt/credentials/credentials-1' && chmod 600 '/etc/letsencrypt/credentials/credentials-1'; }
[7/3/2025] [12:37:02 PM] [Certbot ] › ▶ start Installing cloudflare...
[7/3/2025] [12:37:02 PM] [Global ] › ⬤ debug CMD: . /opt/certbot/bin/activate && pip install --no-cache-dir cloudflare==4.0.* acme==$(certbot --version | grep -Eo '0-9+') certbot-dns-cloudflare==$(certbot --version | grep -Eo '0-9+') && deactivate
[7/3/2025] [12:37:03 PM] [Certbot ] › ✖ error ERROR: Cannot install certbot-dns-cloudflare==4.0.0 and cloudflare==4.0.* because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
[7/3/2025] [12:37:03 PM] [Global ] › ✖ error Some plugins failed to install. Please check the logs above CommandError: Some plugins failed to install. Please check the logs above
previous: undefined,
code: 1,
public: false
@tomsteenbakkers commented on GitHub (Jul 3, 2025):
Same issue running Ubuntu and nginx-proxy-manager is running as a docker container. Revert back to
jc21/nginx-proxy-manager:2.12.3@Chris-LewisI commented on GitHub (Jul 3, 2025):
same issue for me! Downgraded to 2.12.3 and fixed it
@goluftwaffe commented on GitHub (Jul 3, 2025):
Same Issue here, downgrading work for me too. I'm on Docker Compose
@phazejeff commented on GitHub (Jul 4, 2025):
hi @tomsteenbakkers , i love you and i hope you have many great things in your life.
@Travel-dev159 commented on GitHub (Jul 4, 2025):
The solution seems to be good, but I'm running Nginx on Truenas from the catalogue and it's a fresh install, so for me downgrading is not an option now, normally it would be.
Can anyone suggest anything so that I can create the SSL certificate with Cloudflare?
@Tu5k4rr commented on GitHub (Jul 4, 2025):
To confirm as many others have downgrading back to jc21/nginx-proxy-manager:2.12.3 will resolve the issue.
Remember if your using watchtower either temporarily disable or add an ignore statement to not update nginx manager until fixed.
@Travel-dev159 commented on GitHub (Jul 4, 2025):
Yes, but this is a fresh install. I don't have ealier snapshots/versions. Truenas catalogue lets me install the latest version. How should I install an earlier version?
This was working very good on another system. I really need to get this up and running with this new install.
Please suggest what I could do.
@Sedation6612 commented on GitHub (Jul 4, 2025):
Hey y'all, fresh install here as well, getting the same issue.
Happened when trying to use Cloudflare DNS challenge.
When creating the cert using cloudflare via the cert page, this is the error that appears:
@strasharo commented on GitHub (Jul 5, 2025):
This solved it for me:
docker exec -it nginxpm sh -c "sed -i 's/cloudflare==4.0.\*/cloudflare/' /app/global/certbot-dns-plugins.json" && docker restart nginxpm@jtabox commented on GitHub (Jul 6, 2025):
That fix seems to work fine, at least it looks like the SSL cert renew process is working again.
@lucasnasc2 commented on GitHub (Jul 7, 2025):
This did work but is not permanent, if you need to restart the container for whatever reason, the issue comes back. I guess rolling back is the best option for now.
UPDATE: @strasharo thanks for the correction. Restarting is okay, but recreating will break the fix. I did a docker compose down and up again to test it, and it broke.
@strasharo commented on GitHub (Jul 7, 2025):
Looks like it works for restarts but a container recreation will break it for sure.
@Liziloo commented on GitHub (Jul 7, 2025):
I'm getting this same thing after running the recommended CLI command to fix the original issue.
@lucasnasc2 commented on GitHub (Jul 7, 2025):
@Liziloo Have you downgraded to the working version? If it's a new install, just set the version that works on the docker compose file and pull the image again.
@Liziloo commented on GitHub (Jul 7, 2025):
I got it working with the current image, the CLI command, and my global API key.
@SloPOS commented on GitHub (Jul 8, 2025):
This will be the second Git project I started using the day it went down. I think I'm bad luck - searched for hours for this issue last week and assumed it was a setup issue and now it's recognized. Was able to fix my proxmox pve for nginxpm using the instructions above. For those not using Docker - the command searches the file /app/global/certbot-dns-plugins.json for any line containing cloudflare==4.0. followed by any other characters, and replaces that entire string with simply cloudflare. You can do this manually with nano on an Ubuntu vm.
@AcrimoniousMirth commented on GitHub (Jul 9, 2025):
Having previously solved this I just upgraded to 1.2.5 with the hope it would be safe as the issue would be fixed in this very swiftly released update. Unfortunately the issue resurfaced so now redoing the fix.
EDIT: It would appear the fix needs run every time the container is restarted... which makes troubleshooting other issues that have arisen quite tedious.
@AEnterprise commented on GitHub (Jul 9, 2025):
updating to 2.12.5 fixed the issue for me
@SirWobbyTheFirst commented on GitHub (Jul 9, 2025):
Updating to 2.12.5 has fixed this issue for me and I'm able to boot the container up again.
@vzool commented on GitHub (Oct 12, 2025):
Same issue here:
@ShotokanZH commented on GitHub (Oct 12, 2025):
Seems like a "you" problem. Does the container have network access?
It is clearly a DNS resolution issue on PIP so not an issue