mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #3681] Can't login anymore. #2436
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#2436
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @alessiodam on GitHub (Apr 6, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3681
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
When pressing the login button, I am welcomed with this very satisfying error message:
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON dataNginx Proxy Manager Version
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should log me in like it did before
Screenshots

Operating System
Ubuntu 22.04 LTS Pro
Additional context
Docker version:
Docker version 24.0.5, build 24.0.5-0ubuntu1~22.04.1Browser:
Firefox 124.0.2 (64-bit) - Up To DateLast time I logged in was 4 days ago I think.
@alessiodam commented on GitHub (Apr 6, 2024):
This issue is somehow fixed and I didn't do nothing??
@thebino commented on GitHub (Apr 12, 2024):
Have you checked the docker logs? There might be any hint as to why the backend service can't start properly. That's why this error appears most likely.
@alessiodam commented on GitHub (Apr 13, 2024):
I noticed that nginx proxy manager requires port 3000, which was in use by another service, I changed the port of the other service and now it works.