Nginx Proxy Manager App update to v1.2.4 causes startup hang with npm user warnings

Lion401 · July 1, 2025, 11:30pm

First Post so sorry if the tags are wrong!

I tried updating my Nginx Proxy Manager today and it just immediately get stuck and refuse to start. When checking the logs it seems to be a permissions issue which doesn’t make sense to me as I set 777 permission on NPM’s datasets.

Logs stated (I’m paraphrasing as I already fix the issue; sort of lol)

` - Configuring npm user
  - useradd warning: npm's uid 568 outside of the UID_MIN 1000 and UID_MAX 60000 range
  - Configuring npm group [0
  - Checking paths [0
  - Setting ownership [0`

I really couldn’t figure out how to solve it so I just rolled back to v1.2.3 and everything flawlessly worked.

Just wanted to give a warning to those upgrading your NPM install.

If anyone had a similar experience, please share how you solved it.

vcharette · July 2, 2025, 2:39am

I’m having the same issue. Rolling back to the previous version.

SmallBarky · July 2, 2025, 2:46am

Looks like listed as Bug and TrueNAS community catalog back to Version: 1.2.3

github.com/NginxProxyManager/nginx-proxy-manager

Update from 2.12.3 to 2.12.4 broke docker container startup

opened 09:02AM - 01 Jul 25 UTC

wolfmarco

bug

**Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manag…er:latest` docker image? - Yes (2.12.4) - 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** Docker container does not start anymore with log; ``` + . /etc/s6-overlay/s6-rc.d/prepare/10-usergroup.sh ++ set -e ++ log_info 'Configuring npm user ...' ++ echo -e '\E[1;34m❯ \E[1;36mConfiguring npm user ...\E[0m' ++ id -u npm [1;34m❯ [1;36mConfiguring npm user ...[0m ++ useradd -o -u 0 -U -d /tmp/npmuserhome -s /bin/false npm useradd warning: npm's uid 0 outside of the UID_MIN 1000 and UID_MAX 60000 range. [1;34m❯ [1;36mConfiguring npm group ...[0m ++ log_info 'Configuring npm group ...' ++ echo -e '\E[1;34m❯ \E[1;36mConfiguring npm group ...\E[0m' +++ get_group_id npm +++ '[' npm '!=' '' ']' +++ getent group npm +++ cut -d: -f3 ++ '[' 1000 = '' ']' ++ groupmod -o -g 0 npm ++ groupmod -o -g 0 npm +++ get_group_id npm +++ '[' npm '!=' '' ']' +++ getent group npm +++ cut -d: -f3 ++ '[' 0 '!=' 0 ']' ++ usermod -G 0 npm +++ id -g npm ++ '[' 0 '!=' 0 ']' ++ mkdir -p /tmp/npmuserhome ++ chown -R 0:0 /tmp/npmuserhome + . /etc/s6-overlay/s6-rc.d/prepare/20-paths.sh ++ set -e ++ log_info 'Checking paths ...' ++ echo -e '\E[1;34m❯ \E[1;36mChecking paths ...\E[0m' ++ '[' '!' -d /data ']' [1;34m❯ [1;36mChecking paths ...[0m ++ '[' '!' -d /etc/letsencrypt ']' ++ mkdir -p /data/nginx /data/custom_ssl /data/logs /data/access /data/nginx/default_host /data/nginx/default_www /data/nginx/proxy_host /data/nginx/redirection_host /data/nginx/stream /data/nginx/dead_host /data/nginx/temp /data/letsencrypt-acme-challenge /run/nginx /tmp/nginx/body /var/log/nginx /var/lib/nginx/cache/public /var/lib/nginx/cache/private /var/cache/nginx/proxy_temp ++ touch /var/log/nginx/error.log ++ chmod 777 /var/log/nginx/error.log ++ chmod -R 777 /var/cache/nginx ++ chmod 644 /etc/logrotate.d/nginx-proxy-manager + . /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh ++ set -e ++ log_info 'Setting ownership ...' ++ echo -e '\E[1;34m❯ \E[1;36mSetting ownership ...\E[0m' ++ chown root /tmp/nginx [1;34m❯ [1;36mSetting ownership ...[0m ++ chown -R 0:0 /data ++ chown -R 0:0 /etc/letsencrypt ++ chown -R 0:0 /run/nginx ++ chown -R 0:0 /tmp/nginx ++ chown -R 0:0 /var/cache/nginx ++ chown -R 0:0 /var/lib/logrotate ++ chown -R 0:0 /var/lib/nginx ++ chown -R 0:0 /var/log/nginx ++ chown -R 0:0 /etc/nginx/nginx ++ chown -R 0:0 /etc/nginx/nginx.conf ++ chown -R 0:0 /etc/nginx/conf.d ++ CERT_INIT_FLAG=/opt/certbot/.ownership_initialized ++ '[' '!' -f /opt/certbot/.ownership_initialized ']' ++ chown 0:0 /opt/certbot /opt/certbot/bin ++ find /opt/certbot/lib -type d -name site-packages ++ read -r SITE_PACKAGES_DIR ++ chown -R 0:0 /opt/certbot/lib/python3.11/site-packages ``` **Nginx Proxy Manager Version** Login not possible anymore after update from 2.12.3 to 2.12.4. **To Reproduce** Use `docker-compose.yaml` with version 2.12.3 and update to 2.12.4 afterwards. ``` services: app: image: 'jc21/nginx-proxy-manager:2.12.4' ports: - '80:80' - '81:81' - '443:443' volumes: - data:/data - letsencrypt:/etc/letsencrypt restart: always ``` **Expected behavior** Container should start. **Operating System** Virtual Machine on TrueNAS Dragonfish-24.04.2.5 Distributor ID: Ubuntu Description: Ubuntu 24.04.2 LTS Release: 24.04 Codename: noble Docker version 28.2.2, build e6534b4 **Additional context** Update from 2.12.3 to 2.12.4 broke the startup.

afrosheen · July 2, 2025, 4:46am

Yep bit me too. Not the first time NPM has dropped an update with bugs, but this was crippling. I rolled back at the first opportunity and now I’m considering other proxy managers, I just really like the way LetsEncrypt is worked into this and the elegance and simplicity of it…but hitting that upgrade button breaks it pretty often.

Ingbert · July 3, 2025, 1:48pm

Same here - Roll Back saved me…

Erahgon · July 4, 2025, 8:58am

Same here with the rollback!

The “useradd warning: npm’s uid 568 outside of the UID_MIN 1000 and UID_MAX 60000 range.” error exsists on the rolled-back version as well and doesn’t seem to be what’s causing the error.

Looks like it takes a while to get to this part of the logs, but it seems to be looping when it tries to deploy a CloudFlare container (I think the certbot). It’s giving me a dependency error, fails, and loops.

[Certbot  ] › ▶  start Installing cloudflare...
[Global   ] › ⬤  debug     CMD: . /opt/certbot/bin/activate && pip install --no-cache-dir cloudflare==2.19.* acme==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') certbot-dns-cloudflare==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+')  && deactivate

afrosheen · July 14, 2025, 7:55pm

A few threads on this I guess. For anyone stumbling across this, it’s solved in version 1.2.6 which has been available for a few days now.

JohnCahill · July 15, 2025, 3:09pm

Rollback failed for me. Tried to spin up a new container, this time taking the defaults and it fails. Now I’m just stuck! I suppose I could roll my own custom and pull the version I want to use - but that’s just a pain for me!

John

mavproductions · July 20, 2025, 12:07pm

v1.2.3 - > v1.2.6 fails for me. Allows me to go to login page, but fails to go any further after attempting actual login.

Rollback fixes. Any options besides starting from scratch?

MarkHoltz · July 21, 2025, 12:25am

After installing 1.2.6, try the following:

JohnCahill · July 21, 2025, 11:01am

GENIUS! That did it, now I just have to reconfigure all my proxy hosts

neofusion · July 21, 2025, 11:03am

Have you picked ixVolumes or Host Path Volumes as storage for the app?

JohnCahill · July 21, 2025, 11:40am

I always use host path unless I do not care to keep the config around. When I upgraded to 1.26 and hit the wall, when I attempted to roll back to 1.23 it was still stuck and would do nothing. I then attempted to search and after finding no answers, I started a new instance with ixVolumes … Same problem… Ultimately I copied down the proxy host configs, cleared out my host path data and same problem.

I was waiting to see if another ‘fixed’ version came out, nothing. Until I saw your post and that did the trick! I have not yet finished configuring NPM, it is running and I have Let’s Encrypt working again. Next I will check to see if I can just copy over the host configs or build them all out again.

John