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
/login while 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
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
/(dashboard)./login(e.g. via a bookmark, browser autofill, or typing the URL).Expected behavior
An authenticated user visiting
/loginshould be redirected to/(dashboard), same as pre-2.x-router behavior.Actual behavior
SPA router shows its catch-all 404 page.
Additional notes
/loginwhile logged out works fine (shows the login form)./while logged in works fine (shows the dashboard)./instead of/login.Environment
jc21/nginx-proxy-manager:2.15.1