Summary

On a self-hosted Plane Community instance, opening /god-mode without the trailing slash returns the SPA shell but React Router does not render the route. The page appears stuck on the initial loading/spinner state.

Opening /god-mode/ works correctly.

Environment

• Plane Community Edition
• Version: v1.3.0
• Image: makeplane/plane-aio-community:stable
• Deployment: self-hosted AIO, Railway template
• Browser: Chrome

Steps to reproduce

1. Deploy a self-hosted Plane AIO instance.

2. Open the admin setup route without a trailing slash:

   https://<host>/god-mode

3. Observe that the page does not render the setup/sign-in UI.

4. Open the same route with the trailing slash:

   https://<host>/god-mode/

5. The setup/sign-in UI renders correctly.

Actual behavior

/god-mode returns HTTP 200 and loads the SPA shell, but the frontend does not render content. Chrome console shows:

<Router basename="/god-mode/"> is not able to match the URL "/god-mode" because it does not start with the basename, so the <Router> won't render anything.

Expected behavior

/god-mode should either redirect to /god-mode/, or the app/router should normalize the route so both URLs render the same admin setup/sign-in page.

Notes

The backend was healthy during reproduction: /api/instances/ returned 200. The issue is specific to the trailing slash mismatch on the god-mode route.