starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 01:15:51 +03:00

[GH-ISSUE #4548] Postgres password hashing issue #2907

New issue

Open

opened 2026-02-26 07:37:09 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 07:37:09 +03:00

Owner

Originally created by @XaFFaX on GitHub (May 20, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4548

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
When setting new password for user in UI console the password is being saved but it cannot be used. When entering to log in it always fails. Seems to be an issue with hashing of the password in the database. When I manually enter the password hash into the auth table of the database, the password works fine (using: update auth set secret='[hashed_secret]' where id='[id]';).

What I believe is important is that I am using ARM device as host for NPM running under Docker with Postgres 17 database. According to the documentation there were no requirements concerning version of Postgres database and this platform (ARM64) is supported. The CPU used for the deployment is Rockchip RK3566 with 8GB of RAM.

Nginx Proxy Manager Version
2.12.3

To Reproduce
Steps to reproduce the behavior:

Run new instance of NPM.
Login using default credentials (works fine).
Create new user and password.
Logout.
Login does not work with new password.

Workaround

Generate the same (or any other) password using bcrypt hash generator.
Insert into auth table generated password as indicated above.
Login with new password works fine.

Summary
Pre-generated hashes work fine, hashes generated and saved in the database by the application do not work and do not match with password when checked with hash validation tools.

Expected behavior
Able to login with changed password.

Screenshots
Not applicable.

Operating System
Linux DietPi 5.10.160-legacy-rk35xx #1 SMP Wed Jul 10 09:57:26 UTC 2024 aarch64 GNU/Linux

Additional context
Not needed.

Originally created by @XaFFaX on GitHub (May 20, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4548 **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** When setting new password for user in UI console the password is being saved but it cannot be used. When entering to log in it always fails. Seems to be an issue with hashing of the password in the database. When I manually enter the password hash into the auth table of the database, the password works fine (using: `update auth set secret='[hashed_secret]' where id='[id]';`). What I believe is important is that I am using ARM device as host for NPM running under Docker with Postgres 17 database. According to the documentation there were no requirements concerning version of Postgres database and this platform (ARM64) is supported. The CPU used for the deployment is Rockchip RK3566 with 8GB of RAM. **Nginx Proxy Manager Version** 2.12.3 **To Reproduce** Steps to reproduce the behavior: 1. Run new instance of NPM. 2. Login using default credentials (works fine). 3. Create new user and password. 4. Logout. 5. Login does not work with new password. **Workaround** 1. Generate the same (or any other) password using bcrypt hash generator. 2. Insert into auth table generated password as indicated above. 3. Login with new password works fine. **Summary** Pre-generated hashes work fine, hashes generated and saved in the database by the application do not work and do not match with password when checked with hash validation tools. **Expected behavior** Able to login with changed password. **Screenshots** Not applicable. **Operating System** Linux DietPi 5.10.160-legacy-rk35xx #1 SMP Wed Jul 10 09:57:26 UTC 2024 aarch64 GNU/Linux **Additional context** Not needed.

kerem added the

stale

bug

labels

2026-02-26 07:37:09 +03:00

kerem commented

2026-02-26 07:37:10 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 11, 2025):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Dec 11, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#2907

No description provided.

Rows
Columns