webui via reverse proxy path

[slavsl]

I have difficulty running the webui via reverse proxy behind some path (e.g. https://reverseproxyaddr.com/upbrr)
The webUI seems to link the css/js files via absolute paths e.g.:
href="/assets/index-BLbQdymX.css"
and this of course doesn't work if there's some extra path.
Any ideas how to circumvent this, or is it not possible in the current version?

[krotname]

I don't think mounting the current Web UI under a path prefix is supported as-is.

There are two root-relative parts in the current code:

• gui/frontend/vite.config.ts has no base, so the production build uses Vite's root-relative asset paths like /assets/....
• The embedded web server registers API routes at root (/api/auth/status, /api/events, /api/app/...) and serves the SPA fallback from /. The frontend also calls those same root paths, for example fetch("/api/auth/status"), fetch("/api/events"), and /api/app/....

So a plain reverse proxy at /upbrr will still have the browser requesting assets and API/SSE endpoints from the domain root.

The reliable workaround is to expose it at / or on a subdomain, e.g. https://upbrr.example.com/. A proxy-only workaround would need path stripping plus response/JS path rewriting, which is fragile across updates. Proper prefix support would likely need both a configurable Vite base and matching server-side route prefix handling.

[Vyerni]

Following