mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #2886] Container terminates with error at night #1977
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#1977
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 @ZoXx on GitHub (May 5, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2886
Good morning everyone,
i'm running the latest stable version of the image and for the last three days i've been having the problem that the container always stops working at around 3 o'clock at night. i've copied the error message. can anyone help me here?
As soon as i restart the container in the morning, everything runs smoothly again until late at night.
atProcess.ChildProcess._handle.onexit (node:internal/child_process:304:5) [5/5/2023] [2:10:56 AM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [5/5/2023] [2:10:56 AM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [5/5/2023] [2:10:56 AM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [5/5/2023] [2:10:56 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [5/5/2023] [2:10:56 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [5/5/2023] [2:10:56 AM] [Nginx ] › ℹ info Reloading Nginx [5/5/2023] [2:17:00 AM] [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. Failed to renew certificate npm-10 with error: Some challenges have failed. Failed to renew certificate npm-15 with error: Some challenges have failed. Failed to renew certificate npm-16 with error: Some challenges have failed. Failed to renew certificate npm-17 with error: Some challenges have failed. Failed to renew certificate npm-18 with error: Some challenges have failed. Failed to renew certificate npm-19 with error: Some challenges have failed. Failed to renew certificate npm-2 with error: Some challenges have failed. Failed to renew certificate npm-20 with error: Some challenges have failed. Failed to renew certificate npm-21 with error: Some challenges have failed. Failed to renew certificate npm-22 with error: Some challenges have failed. Failed to renew certificate npm-23 with error: Some challenges have failed. Failed to renew certificate npm-24 with error: Some challenges have failed. Failed to renew certificate npm-25 with error: Some challenges have failed. Failed to renew certificate npm-30 with error: Some challenges have failed. Failed to renew certificate npm-31 with error: Some challenges have failed. Failed to renew certificate npm-32 with error: Some challenges have failed. Failed to renew certificate npm-33 with error: Some challenges have failed. Failed to renew certificate npm-34 with error: Some challenges have failed. Failed to renew certificate npm-35 with error: Some challenges have failed. Failed to renew certificate npm-59 with error: Some challenges have failed. Failed to renew certificate npm-81 with error: Some challenges have failed. Failed to renew certificate npm-83 with error: Some challenges have failed. Failed to renew certificate npm-84 with error: Some challenges have failed. Failed to renew certificate npm-85 with error: Some challenges have failed. Failed to renew certificate npm-9 with error: Some challenges have failed. All renewals failed. The following certificates could not be renewed: /etc/letsencrypt/live/npm-1/fullchain.pem (failure) /etc/letsencrypt/live/npm-10/fullchain.pem (failure) /etc/letsencrypt/live/npm-15/fullchain.pem (failure) /etc/letsencrypt/live/npm-16/fullchain.pem (failure) /etc/letsencrypt/live/npm-17/fullchain.pem (failure) /etc/letsencrypt/live/npm-18/fullchain.pem (failure) /etc/letsencrypt/live/npm-19/fullchain.pem (failure) /etc/letsencrypt/live/npm-2/fullchain.pem (failure) /etc/letsencrypt/live/npm-20/fullchain.pem (failure) /etc/letsencrypt/live/npm-21/fullchain.pem (failure) /etc/letsencrypt/live/npm-22/fullchain.pem (failure) /etc/letsencrypt/live/npm-23/fullchain.pem (failure) /etc/letsencrypt/live/npm-24/fullchain.pem (failure) /etc/letsencrypt/live/npm-25/fullchain.pem (failure) /etc/letsencrypt/live/npm-30/fullchain.pem (failure) /etc/letsencrypt/live/npm-31/fullchain.pem (failure) /etc/letsencrypt/live/npm-32/fullchain.pem (failure) /etc/letsencrypt/live/npm-33/fullchain.pem (failure) /etc/letsencrypt/live/npm-34/fullchain.pem (failure) /etc/letsencrypt/live/npm-35/fullchain.pem (failure) /etc/letsencrypt/live/npm-59/fullchain.pem (failure) /etc/letsencrypt/live/npm-81/fullchain.pem (failure) /etc/letsencrypt/live/npm-83/fullchain.pem (failure) /etc/letsencrypt/live/npm-84/fullchain.pem (failure) /etc/letsencrypt/live/npm-85/fullchain.pem (failure) /etc/letsencrypt/live/npm-9/fullchain.pem (failure) 26 renew failure(s), 0 parse failure(s) 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) s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service nginx: stopping s6-rc: info: service frontend: stopping s6-rc: info: service backend: stopping s6-rc: info: service frontend successfully stopped s6-rc: info: service backend successfully stopped s6-rc: info: service nginx successfully stopped s6-rc: info: service prepare: stopping s6-rc: info: service prepare successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped [5/5/2023] [3:04:09 AM] [Global ] › ℹ info PID 131 received SIGTERM [5/5/2023] [3:04:09 AM] [Global ] › ℹ info Stopping. s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service prepare: starting ❯ Configuring npmuser ... 0 usermod: no changes ❯ Checking paths ... ❯ Setting ownership ... s6-rc: fatal: timed out s6-sudoc: fatal: unable to get exit status from server: Operation timed out /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.@github-actions[bot] commented on GitHub (Jan 21, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Mar 7, 2025):
Issue was closed due to inactivity.