Authenticated visit to /login shows 404 page instead of redirecting to dashboard (v2.15.1)

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

1. Log in normally, land on / (dashboard).
2. With the session still active, navigate directly to /login (e.g. via a bookmark, browser autofill, or typing the URL).
3. 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

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.