starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #2850] dnspod Internal Error #1955

New issue

Closed

opened 2026-02-26 07:33:25 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 07:33:25 +03:00

Owner

Originally created by @zzy19868 on GitHub (Apr 22, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2850

`Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-5" --agree-tos --email "@.com" --domains "..ren,*.ren" --authenticator dns-dnspod --dns-dnspod-credentials "/etc/letsencrypt/credentials/credentials-5"
Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
Encountered exception during recovery: requests.exceptions.ConnectionError: HTTPSConnectionPool(host='dnsapi.cn', port=443): Max retries exceeded with url: /Record.List (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused'))
An unexpected error occurred:
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='dnsapi.cn', port=443): Max retries exceeded with url: /Record.Create (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused'))
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.

at ChildProcess.exithandler (node:child_process:402:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1100:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)`

Originally created by @zzy19868 on GitHub (Apr 22, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2850 `Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-5" --agree-tos --email "****@****.com" --domains "*.****.ren,****.ren" --authenticator dns-dnspod --dns-dnspod-credentials "/etc/letsencrypt/credentials/credentials-5" Saving debug log to /tmp/letsencrypt-log/letsencrypt.log Encountered exception during recovery: requests.exceptions.ConnectionError: HTTPSConnectionPool(host='dnsapi.cn', port=443): Max retries exceeded with url: /Record.List (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused')) An unexpected error occurred: requests.exceptions.ConnectionError: HTTPSConnectionPool(host='dnsapi.cn', port=443): Max retries exceeded with url: /Record.Create (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused')) 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. at ChildProcess.exithandler (node:child_process:402:12) at ChildProcess.emit (node:events:513:28) at maybeClose (node:internal/child_process:1100:16) at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)`

kerem

2026-02-26 07:33:25 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:33:26 +03:00

Author

Owner

@shaojs321 commented on GitHub (Jun 18, 2023):

一样的问题有人解决了吗

@shaojs321 commented on GitHub (Jun 18, 2023): 一样的问题有人解决了吗

kerem commented

2026-02-26 07:33:26 +03:00

Author

Owner

@Tinaglet commented on GitHub (Sep 5, 2023):

我也是同样问题，openwrt下docker里装的。。。两天了没找到解决路子

@Tinaglet commented on GitHub (Sep 5, 2023): 我也是同样问题，openwrt下docker里装的。。。两天了没找到解决路子

kerem commented

2026-02-26 07:33:26 +03:00

Author

Owner

@zzy19868 commented on GitHub (Sep 6, 2023):

我也是同样问题，openwrt下docker里装的。。。两天了没找到解决路子

暂时找不到办法，拉了一个
acme.sh 手动部署

@zzy19868 commented on GitHub (Sep 6, 2023): > 我也是同样问题，openwrt下docker里装的。。。两天了没找到解决路子暂时找不到办法，拉了一个 acme.sh 手动部署

kerem commented

2026-02-26 07:33:26 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 14, 2024):

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

@github-actions[bot] commented on GitHub (Apr 14, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:33:26 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 10, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Jun 10, 2025): Issue was closed due to inactivity.

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#1955

No description provided.

Rows
Columns