mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 01:15:51 +03:00
[GH-ISSUE #4625] Not able to get the ssl from cloudflare #2949
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#2949
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 @singhchandan27 on GitHub (Jul 3, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4625
Hello Team,
Getting below after updating to latest tag , while requesting the ssl certificate from Cloudflare
CommandError: 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
I don't know if i m doing it right
@EMP83 commented on GitHub (Jul 3, 2025):
I have same same error
@Kelerion-UK commented on GitHub (Jul 3, 2025):
this is the same as #4617
@ricanwarfare commented on GitHub (Jul 3, 2025):
same, waiting for fix.
@8270647 commented on GitHub (Jul 3, 2025):
Same issue - waiting.
@goluftwaffe commented on GitHub (Jul 3, 2025):
Same here
@speedrapide10 commented on GitHub (Jul 3, 2025):
Same issue using
Image: jc21/nginx-proxy-manager:latest@sha256:597383e1610c1b2e74504e482fceceace25d477cec9b4c9937de0aea0938d652
@singhchandan27 commented on GitHub (Jul 4, 2025):
is there any time line to fix this issue
@github-actions[bot] commented on GitHub (Jan 5, 2026):
Issue is now considered stale. If you want to keep it open, please comment 👍