NGINX Proxy Manager won't start after upgrading from v2.12.3 to v2.12.4

[googlejam]

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • Yes
• Are you sure you're not using someone else's docker image?
  • Yes
• Have you searched for similar issues (both open and closed)?
  • Yes

Describe the bug
NGINX Proxy Manager won't start after upgrading from v2.12.3 to v2.12.4

Here is the log

2025-07-07 19:07:01.188640+00:00�[1;34m❯ �[1;36mConfiguring npm user ...�[0m
2025-07-07 19:07:01.734356+00:00useradd warning: npm's uid 568 outside of the UID_MIN 1000 and UID_MAX 60000 range.
2025-07-07 19:07:02.286829+00:00�[1;34m❯ �[1;36mConfiguring npm group ...�[0m
2025-07-07 19:07:02.358665+00:00�[1;34m❯ �[1;36mChecking paths ...�[0m
2025-07-07 19:07:02.515136+00:00�[1;34m❯ �[1;36mSetting ownership ...�[0m
2025-07-07 19:07:04.599315+00:00/etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh: line 41: syntax error: unexpected end of file
2025-07-07 19:07:04.599518+00:00s6-rc: warning: unable to start service prepare: command exited 2
2025-07-07 19:07:04.600893+00:00/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.

Nginx Proxy Manager Version
v2.12.4

Operating System
TrueNAS 25.04.1

Additional context
Rolled back to v2.12.3 and was able to start the proxy manager.

[jc21]

This error is very perplexing.. It suggests that the file contents are incomplete, yet I can confirm that the bash script is full and syntactically correct, passing shellcheck as well.

On my production servers (amd64 and arm64) this script runs and completes successfully.

Can you run this on your NAS:

docker run --rm -ti \
 --entrypoint= \
  jc21/nginx-proxy-manager:2.12.4 \
  cat /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh

The output should be the same as the repo file.

The script was missing a trailing newline, which is common practice. There's a slim chance that it's a problem with your setup, so try using the develop branch build image and see if it's still happening:

nginxproxymanager/nginx-proxy-manager-dev:develop

[focustense]

The "unexpected end of file" error is the result of trying to run the S6_STAGE2_HOOK sed workaround described in #3154 on the new version of the ownership script. In the old version, the chown command was on the last line but as of 2.12.4 the last line is a fi, so removing it breaks the loop. Unclosed loop = unexpected EOF.

Lots of discussion in the latest comments on the other thread.