Authenticated visit to /login shows 404 page instead of redirecting to dashboard (v2.15.1)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start at the client-side SPA route handling for /login and inspect how an active session is handled when that route is opened directly. Verify that authenticated visits reach / (the dashboard), while logged-out visits still show the login form, and confirm the catch-all 404 is no longer shown for authenticated users.
Written by the indexing model from the issue text.
Description
Description
When a user with a valid session (cookie/token still active) navigates directly to /login, the app shows the SPA's 404 page ("Oops... You just found an error page") instead of redirecting to the dashboard, which is what older versions did.
Steps to reproduce
- Log in normally, land on
/(dashboard). - With the session still active, navigate directly to
/login(e.g. via a bookmark, browser autofill, or typing the URL). - Observe: 404 page is shown instead of the dashboard.
Expected behavior
An authenticated user visiting /login should be redirected to / (dashboard), same as pre-2.x-router behavior.
Actual behavior
SPA router shows its catch-all 404 page.
Additional notes
- Visiting
/loginwhile logged out works fine (shows the login form). - Visiting
/while logged in works fine (shows the dashboard). - The bug is purely a client-side routing issue — no data or backend functionality is affected (proxy hosts, redirection hosts, etc. all intact).
- Workaround: bookmark
/instead of/login.
Environment
- Image:
jc21/nginx-proxy-manager:2.15.1 - Upgraded from: v2.8.0
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 22h 6m
- Merged PRs (30d)
- 22
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NginxProxyManager/nginx-proxy-manager
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
NginxProxyManager/nginx-proxy-manager#5856 · 3 reactions ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NginxProxyManager/nginx-proxy-manager#5748 · 2 comments ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
NginxProxyManager/nginx-proxy-manager#5628 · 2 comments ·
All issues in NginxProxyManager/nginx-proxy-manager
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100