renewing certs error with no message
ronlawrence3 opened this issue · 6 comments
Problem/Motivation
Error renewing certs
Expected behavior
renewal or understandable error message
Actual behavior
Error without explanation
Steps to reproduce
make a cert and verify it, allow your api key to expire or some other issue with your creds, then try to renew.
Proposed changes
Display the stacktrace or something that people don't have to know to go to devtools and look at payloads 😄
Screenshots
devtools response output on call:
{
"error": {
"message": "Internal Error"
},
"debug": {
"stack": [
"Error: Command failed: certbot renew --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-4" --disable-hook-validation --no-random-sleep-on-renew ",
"Saving debug log to /tmp/letsencrypt-log/letsencrypt.log",
"Failed to renew certificate npm-4 with error: Error finding domain using the DigitalOcean API: Unable to authenticate you (Did you provide a valid API token?)",
"All renewals failed. The following certificates could not be renewed:",
" /etc/letsencrypt/live/npm-4/fullchain.pem (failure)",
"1 renew failure(s), 0 parse failure(s)",
"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:422:12)",
" at ChildProcess.emit (node:events:517:28)",
" at maybeClose (node:internal/child_process:1098:16)",
" at ChildProcess._handle.onexit (node:internal/child_process:303:5)"
]
}
}
I have the same error.
the "Test Server Reachability", return "Communication with the API failed, is NPM running correctly?"
thanks
I get the same error. As a workaround, it helps to deactivate the corresponding server entry for the renewal of the certificate.
Hi,
Have sort of same issue - any plan for a fix?
[13:54:23] INFO: Starting the Manager...
[13:54:23] INFO: Starting NGinx...
s6-rc: info: service legacy-services successfully started
[8/16/2024] [1:54:24 PM] [Global ] › ℹ info Using Sqlite: /config/database.sqlite
[8/16/2024] [1:54:25 PM] [Migrate ] › ℹ info Current database version: none
[8/16/2024] [1:54:25 PM] [Setup ] › ℹ info Logrotate Timer initialized
[8/16/2024] [1:54:25 PM] [Setup ] › ℹ info Logrotate completed.
[8/16/2024] [1:54:25 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services...
[8/16/2024] [1:54:25 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[8/16/2024] [1:54:25 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4
[8/16/2024] [1:54:26 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6
[8/16/2024] [1:54:26 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized
[8/16/2024] [1:54:26 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry...
[8/16/2024] [1:54:26 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized
[8/16/2024] [1:54:26 PM] [Global ] › ℹ info Backend PID 159 listening on port 3000 ...
[8/16/2024] [1:59:17 PM] [SSL ] › ✖ error Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --preferred-challenges "dns,http" --disable-hook-validation
Failed to renew certificate npm-1 with error: Some challenges have failed.
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/npm-1/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
at ChildProcess.exithandler (node:child_process:422:12)
at ChildProcess.emit (node:events:517:28)
at maybeClose (node:internal/child_process:1098:16)
at ChildProcess._handle.onexit (node:internal/child_process:303:5)
Identical problem over here, same type of error/messages,