nginx-proxy-manager: s6-sudoc: fatal: unable to get exit status from server: Operation timed out

Came here to add another vote that I am experiencing this issue

@jc21 - this issue needs to be reopened.

This issue is not fixed and has been a problem for the last 2 weeks now. It works when you delete all your files and start new but it seems the first restart it comes back. It is quite disappointing that this issue would be closed without actually fixing anything.

Faced the same issue, docker only works when restarted again

Just editing my comment to let you know that pruning the cert folder worked for me:

 docker exec -ti npm_app cert-prune

npm_app is the name of my docker container for the jc21/nginx-proxy-manager:latest image. Change it according to your environment.

Yep , I removed it and did a reinstall but same problem. So now deleted it and switch to Cloudflare Tunnels.

Same here. Version 2.10.3 seems to be working ok. Thanks!

Updating to 2.10.3 completely fixed this issue for me as well

can confirm this issue persisted for months and seems to be gone after updating today. from 2.10.3 change notes:

• Improved startup scripts, hopefully prevent failure on startup for more systems

why is this closed, the issue still exists or is there some other fix I didn’t find about

Same problem here, the log says:

❯ Configuring npmuser … id: ‘npmuser’: no such user 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.

Thanks. Going back to 2.9.19 worked for me with Ubuntu 64 bit. I tried 2.9.22 but it didn’t work as you said.

Apparently the problem has been introduced in the version 2.9.21. The version 2.9.20 is working fine too. There was another issue opened (#2743) for that with the exact same issue (can’t reboot the container for version > 2.9.20). Now both issues are closed but it is not fixed yet. I don’t know why both were closed as the problem is still there. We should maybe open a new one (WDYT @jc21) ?

Just editing my comment to let you know that pruning the cert folder worked for me:

 docker exec -ti npm_app cert-prune

npm_app is the name of my docker container for the jc21/nginx-proxy-manager:latest image. Change it according to your environment.

This worked for me. Let’s see how long it lasts!

Also agree, I had to downgrade to 2.9.22 to get everything working again, not sure why this is being closed if it is an issue on latest

I get same error as above on rpi arm64.

github-develop does not fix it for me.

❯ Configuring npmuser ...
id: 'npmuser': no such user
❯ Checking paths ...
❯ Setting ownership ...
s6-rc: fatal: 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.
s6-sudoc: fatal: unable to get exit status from server: Operation timed out

Update: The only way I could get it working asap was to run the container as root. e.g.:

services:
  app:
    user: root

I’m not sure if this is an intented side effect of the github-develop docker tag but it does work and the proxy configs work. However if you login to the management then the user account is the admin@example with the changeme password again.

If you login it shows 0 proxy hosts but there are proxy hosts from the old config.

If I change my docker tag to 2.9.22 then everything goes back to normal

this is on github-develop

this is on 2.9.22

the only change was the docker tag.

Also have the problem. Tried stopping / restart Docker. Restart Synology NAS but keeps coming back. Because of that all my program’s are not running anymore that works with the proxy so hopping you find a fix

Log: 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

Assuming this is happening on your existing stacks that have been running for a while, I’m guessing that the script that checks ownership at startup is taking longer than expected due to the size of your letsencrypt folder.

Certbot doesn’t clean up older certs and just leaves them there after each renewal, so this folder can get filled with files although they are not too big.

The second restart would be faster if the files were fresh in storage caches, perhaps.

See the release notes for 2.9.20 for instructions to prune this folder.

In the meantime I’ll look at fixing the timeout.

Same problem here. It does work if you restart the container. It does not work when first started (ie. after a computer reboot). It also doesn’t work again when starting after an update. Currently on version 2.9.22. I’m not sure where these logs it refers to are located. A big problem is that the container doesn’t restart on its own. It just hangs there not working until it is restarted.

This is still an issue. I would recommend opening it back up.