starred/nginx-proxy-manager-NginxProxyManager

Fork 0

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

[GH-ISSUE #4056] Just updated to 2.12.0 and login credentials aren't working #2640

New issue

Open

opened 2026-02-26 07:36:18 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 07:36:18 +03:00

Owner

Originally created by @sluflyer06 on GitHub (Oct 11, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4056

Hi, not sure where to go, I just updated to 2.12 and I can no longer login to admin console, the container is running and serving RP, but I can't login with my normal credentials or the default user with changeme password. It says "not found"

jc21/nginx-proxy-manager:latest

app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
network_mode: host
ports:
# These ports are in format :
- '80:80' # Public HTTP Port
- '443:443' # Public HTTPS Port
- '81:81' # Admin Web Port
# Add any other Stream port you want to expose
# - '21:21' # FTP

Originally created by @sluflyer06 on GitHub (Oct 11, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4056 Hi, not sure where to go, I just updated to 2.12 and I can no longer login to admin console, the container is running and serving RP, but I can't login with my normal credentials or the default user with changeme password. It says "not found" jc21/nginx-proxy-manager:latest app: image: 'jc21/nginx-proxy-manager:latest' restart: unless-stopped network_mode: host ports: # These ports are in format <host-port>:<container-port> - '80:80' # Public HTTP Port - '443:443' # Public HTTPS Port - '81:81' # Admin Web Port # Add any other Stream port you want to expose # - '21:21' # FTP

kerem added the

stale

bug

labels

2026-02-26 07:36:18 +03:00

kerem commented

2026-02-26 07:36:18 +03:00

Author

Owner

@sluflyer06 commented on GitHub (Oct 11, 2024):

If I change back to 2.11.3 it works again.

I did notice in log that it keeps saying port 3000 is already in-use if that's impactful, I'm not seeing that in 2.11.3

@sluflyer06 commented on GitHub (Oct 11, 2024): If I change back to 2.11.3 it works again. I did notice in log that it keeps saying port 3000 is already in-use if that's impactful, I'm not seeing that in 2.11.3

kerem commented

2026-02-26 07:36:18 +03:00

Author

Owner

@silentdis commented on GitHub (Dec 28, 2024):

I'm having the exact same problem

switching back to 2.11.3 i guess

@silentdis commented on GitHub (Dec 28, 2024): I'm having the exact same problem ![image](https://github.com/user-attachments/assets/2456b696-0708-471c-8568-035a339e0636) switching back to 2.11.3 i guess

kerem commented

2026-02-26 07:36:18 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 27, 2025):

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

@github-actions[bot] commented on GitHub (Jul 27, 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#2640

No description provided.

Rows
Columns