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.
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.
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.