[GH-ISSUE #11681] Nginx Proxy Manager - Cannot create admin user #2461

Closed
opened 2026-02-26 12:52:32 +03:00 by kerem · 7 comments
Owner

Originally created by @tiagodenoronha on GitHub (Feb 7, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11681

Have you read and understood the above guidelines?

Yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

Nginx Proxy Manager

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.1.5/80cf92a64bef6889 (running kernel: 6.17.4-2-pve)

📝 Provide a clear and concise description of the issue.

Upon running the default install script, and navigating to Nginx Proxy Manager's admin panel, it prompts me to create an account instead of using the default credentials (admin@example.com).

Image

However, whatever values I use, it returns a 500 because it tries to access api/users and fails

Image

🔄 Steps to reproduce the issue.

Run default script from https://community-scripts.github.io/ProxmoxVE/scripts?id=nginxproxymanager

Let the install finish

Navigate to :81

Try to create an account

Paste the full error output (if available).

The only error message I get from the call to api/users is {"error":{"message":"Internal Error"}} in the console. I have download the .har file if it's helpful, but I cannot attach it here it seems.

🖼️ Additional context (optional).

Attaching the verbose log from the install, if it helps!

nginx_install_log.txt

Originally created by @tiagodenoronha on GitHub (Feb 7, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11681 ### ✅ Have you read and understood the above guidelines? Yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? Nginx Proxy Manager ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.1.5/80cf92a64bef6889 (running kernel: 6.17.4-2-pve) ### 📝 Provide a clear and concise description of the issue. Upon running the default install script, and navigating to Nginx Proxy Manager's admin panel, it prompts me to create an account instead of using the default credentials (admin@example.com). <img width="752" height="827" alt="Image" src="https://github.com/user-attachments/assets/e4329ba3-6180-4b47-9cda-50d6250c307a" /> However, whatever values I use, it returns a 500 because it tries to access api/users and fails <img width="936" height="467" alt="Image" src="https://github.com/user-attachments/assets/bd12434b-2826-48bf-be36-cef2f1c55a80" /> ### 🔄 Steps to reproduce the issue. Run default script from https://community-scripts.github.io/ProxmoxVE/scripts?id=nginxproxymanager Let the install finish Navigate to <ip address>:81 Try to create an account ### ❌ Paste the full error output (if available). The only error message I get from the call to api/users is {"error":{"message":"Internal Error"}} in the console. I have download the .har file if it's helpful, but I cannot attach it here it seems. ### 🖼️ Additional context (optional). Attaching the verbose log from the install, if it helps! [nginx_install_log.txt](https://github.com/user-attachments/files/25156445/nginx_install_log.txt)
kerem 2026-02-26 12:52:32 +03:00
Author
Owner

@MickLesk commented on GitHub (Feb 7, 2026):

https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5284

<!-- gh-comment-id:3865721823 --> @MickLesk commented on GitHub (Feb 7, 2026): https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5284
Author
Owner

@MickLesk commented on GitHub (Feb 7, 2026):

Every new version the tool ist fucked up again.

<!-- gh-comment-id:3865722876 --> @MickLesk commented on GitHub (Feb 7, 2026): Every new version the tool ist fucked up again.
Author
Owner

@tiagodenoronha commented on GitHub (Feb 7, 2026):

Good catch! I'll keep an eye out on the nginx repo and wait for a fix on their side. Thanks!

<!-- gh-comment-id:3865727012 --> @tiagodenoronha commented on GitHub (Feb 7, 2026): Good catch! I'll keep an eye out on the nginx repo and wait for a fix on their side. Thanks!
Author
Owner

@unecc commented on GitHub (Feb 8, 2026):

default user and password doesn't works!

admin@example.com
changeme

<!-- gh-comment-id:3866892364 --> @unecc commented on GitHub (Feb 8, 2026): default user and password doesn't works! admin@example.com changeme
Author
Owner

@Shaalan15 commented on GitHub (Feb 8, 2026):

Facing the same issue. Happy to help any way I can!

<!-- gh-comment-id:3867681830 --> @Shaalan15 commented on GitHub (Feb 8, 2026): Facing the same issue. Happy to help any way I can!
Author
Owner

@bpctrl commented on GitHub (Feb 8, 2026):

Workaround:

  1. Open production.json nano /app/config/production.json
  2. change "client": "sqlite3" to "client": "better-sqlite3",
  3. save file
  4. restart service systemctl restart npm
<!-- gh-comment-id:3867751125 --> @bpctrl commented on GitHub (Feb 8, 2026): Workaround: 1. Open production.json `nano /app/config/production.json` 2. change ` "client": "sqlite3"` to ` "client": "better-sqlite3",` 3. save file 4. restart service `systemctl restart npm`
Author
Owner

@mudora23 commented on GitHub (Feb 8, 2026):

Workaround:

  1. Open production.json nano /app/config/production.json
  2. change "client": "sqlite3" to "client": "better-sqlite3",
  3. save file
  4. restart service systemctl restart npm

Thanks, it works.
This appears to be a script issue. Nginx Proxy Manager was updated to use the “better-sqlite3” client in knex, but the scripts are still hard-coded to use the old “sqlite3” client.

Additionally, the main script page still lists the “Default Login Credentials”, but these are no longer used as of commit github.com/NginxProxyManager/nginx-proxy-manager@0b2fa826e0

<!-- gh-comment-id:3867894845 --> @mudora23 commented on GitHub (Feb 8, 2026): > Workaround: > > 1. Open production.json `nano /app/config/production.json` > 2. change ` "client": "sqlite3"` to ` "client": "better-sqlite3",` > 3. save file > 4. restart service `systemctl restart npm` Thanks, it works. This appears to be a script issue. Nginx Proxy Manager was updated to use the “better-sqlite3” client in knex, but the scripts are still hard-coded to use the old “sqlite3” client. Additionally, the main script page still lists the “Default Login Credentials”, but these are no longer used as of commit https://github.com/NginxProxyManager/nginx-proxy-manager/commit/0b2fa826e0fe440cd27ce31528bca232d537a534
Sign in to join this conversation.
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/ProxmoxVE#2461
No description provided.