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 #5323] First-run admin setup fails with "Invalid email or password" and locks instance #3167

New issue

Open

opened 2026-02-26 07:38:01 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 07:38:01 +03:00

Owner

Originally created by @jesperbruhn on GitHub (Feb 18, 2026).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5323

At first startup, I enter my information:

Name, email and password.

And press Save, but immediately get the error Invalid email or password, but am sent to the login screen, and then I can't proceed.

Originally created by @jesperbruhn on GitHub (Feb 18, 2026). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5323 At first startup, I enter my information: Name, email and password. And press Save, but immediately get the error Invalid email or password, but am sent to the login screen, and then I can't proceed. <img width="620" height="845" alt="Image" src="https://github.com/user-attachments/assets/f321b2c8-32a4-4252-9dd0-9aa8e3d7e52e" />

kerem added the

bug

label

2026-02-26 07:38:01 +03:00

kerem commented

2026-02-26 07:38:01 +03:00

Author

Owner

@arthurbrazil commented on GitHub (Feb 19, 2026):

I am also experiencing this issue.

@arthurbrazil commented on GitHub (Feb 19, 2026): I am also experiencing this issue.

kerem commented

2026-02-26 07:38:01 +03:00

Author

Owner

@jesperbruhn commented on GitHub (Feb 19, 2026):

[Bug] First-run admin setup fails with "Invalid email or password" and locks instance

Description

On a fresh installation, Nginx Proxy Manager opens directly in the first-run admin setup wizard.
After entering name, email and password and pressing Save, the UI returns "Invalid email or password" and redirects to the login screen.
The instance becomes locked because no credentials work afterwards.

It appears the admin record is partially written to the SQLite database, leaving it in an inconsistent state.

Expected behaviour

Setup wizard creates the admin account successfully
User is redirected to the dashboard

Actual behaviour

Error message appears after pressing Save
Redirect to login page
Login fails with the newly created credentials

Steps to reproduce

Fresh install of Nginx Proxy Manager
Open web UI (setup wizard appears)
Enter name, email and password
Click Save
Observe error and failed login

Environment

Installation method: Docker + Docker Compose
Host: Proxmox LXC (unprivileged)
OS: Debian 12
Database: SQLite (default)
Browser: Chrome (also tested Incognito)

Workaround

docker compose down
sqlite3 /opt/npm/data/database.sqlite "UPDATE user SET is_deleted=1;"
docker compose up -d

Notes

Using lowercase email and avoiding browser autofill prevented the issue after reset.
Possibly related to how the initial admin user is written during setup.

@jesperbruhn commented on GitHub (Feb 19, 2026): ### [Bug] First-run admin setup fails with "Invalid email or password" and locks instance ### Description On a fresh installation, Nginx Proxy Manager opens directly in the first-run admin setup wizard. After entering name, email and password and pressing **Save**, the UI returns **"Invalid email or password"** and redirects to the login screen. The instance becomes locked because no credentials work afterwards. It appears the admin record is partially written to the SQLite database, leaving it in an inconsistent state. ### Expected behaviour - Setup wizard creates the admin account successfully - User is redirected to the dashboard ### Actual behaviour - Error message appears after pressing Save - Redirect to login page - Login fails with the newly created credentials ### Steps to reproduce 1. Fresh install of Nginx Proxy Manager 2. Open web UI (setup wizard appears) 3. Enter name, email and password 4. Click Save 5. Observe error and failed login ### Environment - Installation method: Docker + Docker Compose - Host: Proxmox LXC (unprivileged) - OS: Debian 12 - Database: SQLite (default) - Browser: Chrome (also tested Incognito) ### Workaround docker compose down sqlite3 /opt/npm/data/database.sqlite "UPDATE user SET is_deleted=1;" docker compose up -d ### Notes - Using lowercase email and avoiding browser autofill prevented the issue after reset. - Possibly related to how the initial admin user is written during setup.

kerem commented

2026-02-26 07:38:01 +03:00

Author

Owner

@IDEDARY commented on GitHub (Feb 20, 2026):

I am also experiencing this issue. Not the greatest first impression with this software to be honest.

@IDEDARY commented on GitHub (Feb 20, 2026): I am also experiencing this issue. Not the greatest first impression with this software to be honest.

kerem commented

2026-02-26 07:38:01 +03:00

Author

Owner

@Momentum6890 commented on GitHub (Feb 23, 2026):

Same issue here

@Momentum6890 commented on GitHub (Feb 23, 2026): Same issue here

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#3167

No description provided.

Rows
Columns