starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #2514] DNS challenge ClouDNS produces an error #1753

New issue

Closed

opened 2026-02-26 07:32:20 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 07:32:20 +03:00

Owner

Originally created by @ghost on GitHub (Jan 1, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2514

Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-57" --agree-tos --email "ctl@ctl.email" --domains "infologie.net" --authenticator dns-cloudns --dns-cloudns-credentials "/etc/letsencrypt/credentials/credentials-57"
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Encountered exception during recovery: dns.resolver.LifetimeTimeout: The resolution lifetime expired after 5.402 seconds: Server 127.0.0.11 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.11 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.11 UDP port 53 answered The DNS operation timed out.
An unexpected error occurred:
dns.resolver.LifetimeTimeout: The resolution lifetime expired after 5.402 seconds: Server 127.0.0.11 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.11 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.11 UDP port 53 answered The DNS operation timed out.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/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 Socket. (node:internal/child_process:458:11)
at Socket.emit (node:events:513:28)
at Pipe. (node:net:301:12)

Originally created by @ghost on GitHub (Jan 1, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2514 Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-57" --agree-tos --email "ctl@ctl.email" --domains "infologie.net" --authenticator dns-cloudns --dns-cloudns-credentials "/etc/letsencrypt/credentials/credentials-57" Saving debug log to /var/log/letsencrypt/letsencrypt.log Encountered exception during recovery: dns.resolver.LifetimeTimeout: The resolution lifetime expired after 5.402 seconds: Server 127.0.0.11 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.11 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.11 UDP port 53 answered The DNS operation timed out. An unexpected error occurred: dns.resolver.LifetimeTimeout: The resolution lifetime expired after 5.402 seconds: Server 127.0.0.11 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.11 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.11 UDP port 53 answered The DNS operation timed out. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/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 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:20 +03:00

closed this issue
added the
stale
label

kerem commented

2026-02-26 07:32:20 +03:00

Author

Owner

@rightsaidfred99 commented on GitHub (Jan 3, 2023):

This bug has been happening for half a year. Best to revert back to at least 2.9.14 and just freeze it. Although someone correct me if there's a better way as I'd love to know!

@rightsaidfred99 commented on GitHub (Jan 3, 2023): This bug has been happening for half a year. Best to revert back to at least 2.9.14 and just freeze it. Although someone correct me if there's a better way as I'd love to know!

kerem commented

2026-02-26 07:32:20 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 31, 2024):

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

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

kerem commented

2026-02-26 07:32:20 +03:00

Author

Owner

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

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Aug 14, 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#1753

No description provided.

Rows
Columns