Environment:
WUD version: 8.3.1
Image: getwud/wud:8.3.1
Deployment: Docker Compose, direct port mapping (no reverse proxy)
Browser: tested in Firefox, reproduces in private/incognito mode too (not a caching issue)
Description:
When navigating directly between sub-pages under /configuration/ (e.g. Watchers → Triggers → Server → Registries → Auth) using the in-app menu, clicking a link sometimes does nothing — the page doesn't update and no error is shown to the user.
Steps to reproduce:
Load the app fresh from the root URL: http://:3001/
Navigate via the left menu to Configuration → Watchers (loads fine)
From there, click to another Configuration sub-page (e.g. Triggers, Server, Registries, or Auth)
The click does nothing — the page stays on the previous view
Workaround found:
Navigating back to the root URL (http://:3001/) first, then clicking directly into the target sub-page from the home menu, works correctly every time.
Root cause (from DevTools inspection):
When the failure happens, the Network tab shows a request like:
GET http://:3001/configuration/js/500.49c26bea.js
Status: 200 OK
Content-Type: text/html
Instead of returning the actual JS chunk, the server falls back to serving index.html (SPA fallback), which the browser then fails to execute as a script. This looks like an asset path resolution issue — a lazy-loaded chunk reference is being resolved as relative to the current route (/configuration/) instead of the site root (/), so the browser requests /configuration/js/.js instead of /js/.js. The server has no route for that nested path and falls back to the SPA catch-all, returning HTML with a 200 status instead of a proper 404 or the actual asset.
When loading fresh from /, all asset paths resolve correctly and navigation between Configuration sub-pages works without issue — the bug only appears when a client-side navigation happens while already on a nested /configuration/* route.
Expected behavior:
All Configuration sub-pages should be reachable by clicking directly between them, without needing to return to the home page first.
Environment:
WUD version: 8.3.1
Image: getwud/wud:8.3.1
Deployment: Docker Compose, direct port mapping (no reverse proxy)
Browser: tested in Firefox, reproduces in private/incognito mode too (not a caching issue)
Description:
When navigating directly between sub-pages under /configuration/ (e.g. Watchers → Triggers → Server → Registries → Auth) using the in-app menu, clicking a link sometimes does nothing — the page doesn't update and no error is shown to the user.
Steps to reproduce:
Load the app fresh from the root URL: http://:3001/
Navigate via the left menu to Configuration → Watchers (loads fine)
From there, click to another Configuration sub-page (e.g. Triggers, Server, Registries, or Auth)
The click does nothing — the page stays on the previous view
Workaround found:
Navigating back to the root URL (http://:3001/) first, then clicking directly into the target sub-page from the home menu, works correctly every time.
Root cause (from DevTools inspection):
When the failure happens, the Network tab shows a request like:
GET http://:3001/configuration/js/500.49c26bea.js
Status: 200 OK
Content-Type: text/html
Instead of returning the actual JS chunk, the server falls back to serving index.html (SPA fallback), which the browser then fails to execute as a script. This looks like an asset path resolution issue — a lazy-loaded chunk reference is being resolved as relative to the current route (/configuration/) instead of the site root (/), so the browser requests /configuration/js/.js instead of /js/.js. The server has no route for that nested path and falls back to the SPA catch-all, returning HTML with a 200 status instead of a proper 404 or the actual asset.
When loading fresh from /, all asset paths resolve correctly and navigation between Configuration sub-pages works without issue — the bug only appears when a client-side navigation happens while already on a nested /configuration/* route.
Expected behavior:
All Configuration sub-pages should be reachable by clicking directly between them, without needing to return to the home page first.