Nginx Proxy Manager - Update error

[di5cord20]

I got the following error when trying to update the container. Any thoughts on what's causing the error or how to fix?

[ERROR] in line 127: exit code 3: while executing command wget -q "https://github.com/just-containers/s6-overlay/releases/download/v3.1.5.0/s6-overlay-noarch.tar.xz"

[tteck]

No idea, exit code 3 suggests that there was a problem with the wget command execution, but the URL is valid.

[di5cord20]

I restored a backup to try again. As per the first try, I got the following error. I forgot about that error and only posted the subsequent error on the 2nd try (which again shows for me now on the restored version). Perhaps this new information can point to a root cause??

[ERROR] in line 137: exit code 1: while executing command yarn install --network-timeout=30000 &> /dev/null

[di5cord20]

I think I figured out the issue. After another restore, I noticed the Bootsize disk was running low (had 4G storage). I did a clean restore from my backup, upped storage to 6G, then ran the update script. This time it completed successfully.

@tteck , not sure if it's possible, perhaps a check on free space before running the script to ensure sufficient space available?

[tteck]

I'll look into that. If you utilize the "Proxmox VE LXC Updater" it shows disk information.

[Stephan-4711]

Mine shows 79% full and I have the same issue after update the contianer.
systemctl status nginx gives me a:

x nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; preset: enabled)
Active: failed (Result: timeout) since Mon 2023-11-06 09:40:25 CET; 32s ago
Docs: man:nginx(8)
Process: 131 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Process: 184 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
CPU: 311ms

Nov 06 09:38:53 nginxproxymanager systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server...
Nov 06 09:38:55 nginxproxymanager systemd[1]: nginx.service: Can't open PID file /run/nginx.pid (yet?) after start: No such file or directory
Nov 06 09:40:25 nginxproxymanager systemd[1]: nginx.service: start operation timed out. Terminating.
Nov 06 09:40:25 nginxproxymanager systemd[1]: nginx.service: Killing process 198 (nginx) with signal SIGKILL.
Nov 06 09:40:25 nginxproxymanager systemd[1]: nginx.service: Killing process 199 (nginx) with signal SIGKILL.
Nov 06 09:40:25 nginxproxymanager systemd[1]: nginx.service: Killing process 200 (nginx) with signal SIGKILL.
Nov 06 09:40:25 nginxproxymanager systemd[1]: nginx.service: Killing process 201 (nginx) with signal SIGKILL.
Nov 06 09:40:25 nginxproxymanager systemd[1]: nginx.service: Failed with result 'timeout'.
Nov 06 09:40:25 nginxproxymanager systemd[1]: Failed to start nginx.service - A high performance web server and a reverse proxy server.y

it's the second time after updating the container, that it is broken after the update.
During starting the service, nginx is shortly working an then crashes.

[Stephan-4711]

after restore of the old verison systemctl status still shows it's not working. but the nginx services started. looks like it's trying to start twice?

nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Mon 2023-11-06 10:12:47 CET; 2min 52s ago
Docs: man:nginx(8)
Process: 155 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Process: 169 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=1/FAILURE)
CPU: 273ms

Nov 06 10:12:46 nginxproxymanager nginx[169]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Nov 06 10:12:46 nginxproxymanager nginx[169]: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
Nov 06 10:12:46 nginxproxymanager nginx[169]: nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
Nov 06 10:12:46 nginxproxymanager nginx[169]: nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
Nov 06 10:12:46 nginxproxymanager nginx[169]: nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use)
Nov 06 10:12:46 nginxproxymanager nginx[169]: nginx: [emerg] bind() to [::]:81 failed (98: Address already in use)
Nov 06 10:12:47 nginxproxymanager nginx[169]: nginx: [emerg] still could not bind()
Nov 06 10:12:47 nginxproxymanager systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Nov 06 10:12:47 nginxproxymanager systemd[1]: nginx.service: Failed with result 'exit-code'.
Nov 06 10:12:47 nginxproxymanager systemd[1]: Failed to start nginx.service - A high performance web server and a reverse proxy server.

[tteck]

Address already in use?