[GH-ISSUE #2593] add Let's Encrypt ssl Prompt for this error,How can I solve this problem #1808

Closed
opened 2026-02-26 07:32:32 +03:00 by kerem · 7 comments
Owner

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.

at ChildProcess.exithandler (node:child_process:402:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1100:16)
at Socket. (node:internal/child_process:458:11)
at Socket.emit (node:events:513:28)
at Pipe. (node:net:301:12)
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. at ChildProcess.exithandler (node:child_process:402:12) at ChildProcess.emit (node:events:513:28) at maybeClose (node:internal/child_process:1100:16) at Socket. (node:internal/child_process:458:11) at Socket.emit (node:events:513:28) at Pipe. (node:net:301:12)
kerem 2026-02-26 07:32:32 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@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

<!-- gh-comment-id:1419835345 --> @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
Author
Owner

@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.

<!-- gh-comment-id:1426888491 --> @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.
Author
Owner

@michi91 commented on GitHub (Feb 13, 2023):

same for me!

<!-- gh-comment-id:1427679897 --> @michi91 commented on GitHub (Feb 13, 2023): same for me!
Author
Owner

@davix3f commented on GitHub (Feb 13, 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.

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.

<!-- gh-comment-id:1427737016 --> @davix3f commented on GitHub (Feb 13, 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. 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.
Author
Owner

@oslo254804746 commented on GitHub (Mar 4, 2023):

Test server reachability do not working

[3/4/2023] [11:26:38 AM] [SSL      ] › ℹ  info      Renew Complete
`QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0
`QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0
QueryBuilder#omit is deprecated. This method will be removed in version 3.0
Model#$omit is deprected and will be removed in 3.0.
[3/4/2023] [11:33:24 AM] [SSL      ] › ℹ  info      Testing http challenge for xxx.xxx.cn
Uncaught SyntaxError: Unexpected end of JSON input

FROM
./run: line 19:   617 Trace/breakpoint trap   (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

I change to use traefik with let`s encrypt, and it work finesl

<!-- gh-comment-id:1454711603 --> @oslo254804746 commented on GitHub (Mar 4, 2023): `Test server reachability` do not working ```shell [3/4/2023] [11:26:38 AM] [SSL ] › ℹ info Renew Complete `QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0 `QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0 QueryBuilder#omit is deprecated. This method will be removed in version 3.0 Model#$omit is deprected and will be removed in 3.0. [3/4/2023] [11:33:24 AM] [SSL ] › ℹ info Testing http challenge for xxx.xxx.cn Uncaught SyntaxError: Unexpected end of JSON input FROM ./run: line 19: 617 Trace/breakpoint trap (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js ``` I change to use traefik with let`s encrypt, and it work finesl
Author
Owner

@github-actions[bot] commented on GitHub (Jan 28, 2024):

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

<!-- gh-comment-id:1913407521 --> @github-actions[bot] commented on GitHub (Jan 28, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Mar 14, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2723141243 --> @github-actions[bot] commented on GitHub (Mar 14, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1808
No description provided.