mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #2593] add Let's Encrypt ssl Prompt for this error,How can I solve this problem #1808
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#1808
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 @404ZenX on GitHub (Feb 6, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2593
add Let's Encrypt ssl Prompt for this error,How can I solve this problem
Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-24" --agree-tos --email "weng8858@qq.com" --domains "*.weerr.cn" --authenticator dns-dnspod --dns-dnspod-credentials "/etc/letsencrypt/credentials/credentials-24"
An unexpected error occurred:
ModuleNotFoundError: No module named 'zope'
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-x1vhtsg9/log or re-run Certbot with -v for more details.
@SteProTech commented on GitHub (Feb 6, 2023):
hope this get fixed soon, this also shows "Communication with the API failed" error. maybe it got something to do with the api
@davix3f commented on GitHub (Feb 11, 2023):
I'm getting the "Communication with API failed, are you sure NPM is running correctly" error too, I can't request any new certificate nor renew my existing ones. I didn't change anything in my docker compose or anything, this issue just came up by itself. I also can't find any solution on this on the internet.
@michi91 commented on GitHub (Feb 13, 2023):
same for me!
@davix3f commented on GitHub (Feb 13, 2023):
I "solved" the issue by destroying my docker container, destroying the proxmox lxc where npm was hosted, and starting all over again. I downloaded the certificates before, so I applied them as custom now. Took me some time, but luckily I was managing just 15 hosts so not to big of a deal, But I still wonder how can something break, if I don't touch any config file.
EDIT: "Test server reachability" Still does not work, at all, even on this brand new setup. I guess the funcionality is just uselessly broken at this point.
@oslo254804746 commented on GitHub (Mar 4, 2023):
Test server reachabilitydo not workingI change to use traefik with let`s encrypt, and it work finesl
@github-actions[bot] commented on GitHub (Jan 28, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Mar 14, 2025):
Issue was closed due to inactivity.