Is there an existing issue for this?
Current Behavior
When running behind a sub-path reverse proxy (BASE_URL set, e.g. /ombi), the web UI serves a blank/white page.
The served index.html keeps <base href="/">, so all JS/CSS assets are requested from the domain root instead of the sub-path and return 404 (the proxy only routes the sub-path to the container).
Startup logs show:
Base Url: /ombi
Error attempting to write Base URL, see here: https://docs.ombi.app/info/known-faults/#unauthorized-access-to-indexhtml
Root cause (verified): the init script /etc/s6-overlay/s6-rc.d/init-ombi-config/run chowns the wrong path:
lsiown abc:abc /app/ombi/ClientApp/dist/index.html
In 4.53.10 the Angular build output moved into a browser/ subfolder. The actual file is /app/ombi/ClientApp/dist/browser/index.html, still owned by 1001:1001. Because the real file is never chowned to abc (PUID), Ombi cannot rewrite it on startup, so the <base href> is never updated.
This is exactly what #124 already fixed (changing the path to dist/browser/index.html), but the current 4.53.10 image ships the old path again — the fix appears to have regressed (the later LSIO_READ_ONLY_FS change reintroduced the pre-#124 path).
Expected Behavior
With BASE_URL set, Ombi rewrites index.html to the correct <base href> and the UI loads behind the sub-path (as it did in 4.53.5).
Steps To Reproduce
- Run
linuxserver/ombi:4.53.10 with BASE_URL=/ombi and PUID/PGID set to a non-1001 user (e.g. 1000).
- Reverse-proxy the
/ombi sub-path to the container.
- Open the sub-path → blank page; the served
index.html still has <base href="/">.
Environment
OS: Linux
Image: linuxserver/ombi:4.53.10 (also tagged latest)
Verification
# 4.53.5 (works): index.html sits flat in dist/, matching the hardcoded chown path
/app/ombi/ClientApp/dist/index.html 1001:1001
# 4.53.10 (broken): index.html moved under browser/, chown path unchanged
/app/ombi/ClientApp/dist/browser/index.html 1001:1001
The init-ombi-config/run script is otherwise identical between 4.53.5 and 4.53.10; only the on-disk location of index.html changed.
Suggested fix
Re-apply #124: point the chown in init-ombi-config/run at /app/ombi/ClientApp/dist/browser/index.html.
Is there an existing issue for this?
Current Behavior
When running behind a sub-path reverse proxy (
BASE_URLset, e.g./ombi), the web UI serves a blank/white page.The served
index.htmlkeeps<base href="/">, so all JS/CSS assets are requested from the domain root instead of the sub-path and return 404 (the proxy only routes the sub-path to the container).Startup logs show:
Root cause (verified): the init script
/etc/s6-overlay/s6-rc.d/init-ombi-config/runchowns the wrong path:In
4.53.10the Angular build output moved into abrowser/subfolder. The actual file is/app/ombi/ClientApp/dist/browser/index.html, still owned by1001:1001. Because the real file is never chowned toabc(PUID), Ombi cannot rewrite it on startup, so the<base href>is never updated.This is exactly what #124 already fixed (changing the path to
dist/browser/index.html), but the current4.53.10image ships the old path again — the fix appears to have regressed (the laterLSIO_READ_ONLY_FSchange reintroduced the pre-#124 path).Expected Behavior
With
BASE_URLset, Ombi rewritesindex.htmlto the correct<base href>and the UI loads behind the sub-path (as it did in4.53.5).Steps To Reproduce
linuxserver/ombi:4.53.10withBASE_URL=/ombiandPUID/PGIDset to a non-1001user (e.g. 1000)./ombisub-path to the container.index.htmlstill has<base href="/">.Environment
Verification
The
init-ombi-config/runscript is otherwise identical between4.53.5and4.53.10; only the on-disk location ofindex.htmlchanged.Suggested fix
Re-apply #124: point the chown in
init-ombi-config/runat/app/ombi/ClientApp/dist/browser/index.html.