[GH-ISSUE #1253] Logic issue with NTFY_PASSWORD on pass-change? #885

New issue

Open

opened 2026-05-07 00:28:27 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-07 00:28:27 +02:00

Owner

Originally created by @pixitha on GitHub (Jan 6, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1253

🐞 Describe the bug
I have ntfy running in a docker container (fly.io) and was adding a 2nd user via terminal inside of the docker container. Running the change-pass function with the ntfy server client was never asking for a password. I didn't realize that I had set the ENV variable for this, to run on the initial setup, but after the initial setup it never gets used. This created a silent failure (on my part) that whenever I try to change any user password, it always uses the original ENV variable.

💻 Components impacted
ntfy server/user auth

💡 Screenshots and/or logs

ntfy user change-pass testuser
changed password for user testuser

This leads to a slightly confusing silent password change, it might be worth adding some output to the user.go code to reflect when its using the env variable, since it can be a bit confusing why its not prompting for the password like you would expect?

🔮 Additional context

Originally created by @pixitha on GitHub (Jan 6, 2025). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1253 :lady_beetle: **Describe the bug** I have ntfy running in a docker container (fly.io) and was adding a 2nd user via terminal inside of the docker container. Running the change-pass function with the ntfy server client was never asking for a password. I didn't realize that I had set the ENV variable for this, to run on the initial setup, but after the initial setup it never gets used. This created a silent failure (on my part) that whenever I try to change any user password, it always uses the original ENV variable. :computer: **Components impacted** ntfy server/user auth :bulb: **Screenshots and/or logs** ``` ntfy user change-pass testuser changed password for user testuser ``` This leads to a slightly confusing silent password change, it might be worth adding some output to the user.go code to reflect when its using the env variable, since it can be a bit confusing why its not prompting for the password like you would expect? :crystal_ball: **Additional context**