mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #2070] Dependency Build Errors for Cloudflare DNS Challenge #1492
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#1492
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 @vicchi on GitHub (May 24, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2070
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
The tl;dr version is that installing
cloudflareandcertbot-dns-cloudflarefail becausePython.his missing becausepython3-devis missing from the container image. This is closely related and even possibly a duplicate of #1955 although that issue is DuckDNS related rather than CloudFlare but the dependencies and root cause at least seem the same.Nginx Proxy Manager Version
v2.9.18To Reproduce
Steps to reproduce the behavior:
dns_cloudflare_api_token=<redacted>Expected behavior
An SSL certificate to be generated via Cloudflare's DNS challenge
Screenshots
Operating System
Additional context
Workaround ...
Be prepared with much ☕ as the build of the wheel for
cryptographytakes a while, at least on an RPiAfter completion of the dependencies install, issuing SSL certs works and all is good
@Reupireup commented on GitHub (Jun 9, 2022):
I have the same issue with OVH dns-challenge (and same environment Rpi4, docker and NPM version) and same trace.
the workaround worked for me (adapted for ovh)
docker exec -it nginx_proxy_manager /bin/bashapt updateapt-get install -y build-essential libssl-dev libffi-dev python3-dev cargopip install certbot-dns-ovh==$(/usr/bin/certbot --version | grep -Eo '[0-9](\.[0-9]+)+') ovh@jeffshee commented on GitHub (Jul 13, 2022):
I have the same issue. Besides, I also couldn't install cryptography without updating the pip and setuptools, as shown in the error message below.
Workaround:
pip install pip setuptools --upgradeIMO, it will be nice to have the certbots included in the image, as it requires lots of time to build and install otherwise.
Error message:
@R-ens commented on GitHub (Sep 15, 2022):
I followed all above steps to get Cloudflare DNS challange working but get another new error while installing dependencies.
Whats going on and who can help me further?
Why isn't this been solved in the Docker image already? There is no new version released since months....
@vascozorrinho commented on GitHub (Sep 17, 2022):
Same problem here. did you find a solution?
tried
pip install rust --upgrade
but got this error
`[root@docker-5e9444045b64:/app]# pip install rust --upgrade
Collecting rust
Using cached RUST-0.1.1.tar.gz (13 kB)
Preparing metadata (setup.py) ... done
Collecting matplotlib
Using cached matplotlib-3.5.3.tar.gz (35.2 MB)
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [132 lines of output]
error: subprocess-exited-with-error
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.`
@R-ens commented on GitHub (Sep 17, 2022):
@vascozorrinho
I used this command and that works for me.
pip install certbot-dns-cloudflare --index-url https://www.piwheels.org/simple --prefer-binaryPlease keep in mind that you have to use this command again after restarting your Docker image otherwise you will get a Bad Gateway error.
Hope for a decent fix soon...
@vascozorrinho commented on GitHub (Sep 17, 2022):
wow! that worked :D
I think you saved my life!
thanks
@h00bi commented on GitHub (Dec 5, 2022):
had similiar problems with netcup
i opened the npm container shell and installed latest certbot-dns-netcup which is 1.2.0
With this, i can get a wildcard certificate using shell commands.
Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/npm-4/fullchain.pem
Key is saved at: /etc/letsencrypt/live/npm-4/privkey.pem
This certificate expires on 2023-03-05.
These files will be updated when the certificate renews.
Unfortuately, this certificate will not be shown in the gui.
When i run the gui wizard again for netcup dns challenge, it will downgrade certbot-dns-netcup to 1.0.1 which will fail again.
I suggest you set TTL to a very low value during testing, like 60s, but don't forget to increase later.
Please update certbot-dns-netcup install routine for this container.
@vascozorrinho commented on GitHub (Dec 16, 2022):
@renslinden you just saved me again.. i'm surprised this is still a problem
@h00bi commented on GitHub (Dec 16, 2022):
Actually, this ist solved in the amd64 docker Container, which already has certbot 2.1.0
It's just the armv7 i guess.
I run this inside an amd64 lxc Container and it works great.
@vascozorrinho commented on GitHub (Dec 16, 2022):
Damn! I'm running this on a 32 bits RP 3 and that device is not powerful enough to run a 64bit os. I actually tried that.. Maybe in the future I'll upgrade but since this doesn't happen that often, for now, this will work
@palepinkdot commented on GitHub (Dec 22, 2023):
Update for you, this worked for me on an RPi 4 under Portainer on the latest docker tag.
Appears to be related to arm7, worked fine on amd64.
@github-actions[bot] commented on GitHub (Aug 8, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Aug 16, 2025):
Issue was closed due to inactivity.