Skip to content

[BUG] BASE_URL not applied (white page) in 4.53.10 — init chowns wrong index.html path, regression of #124 #126

Closed

Description

@OKDaG

Is there an existing issue for this?

  • I have searched the existing issues

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

  1. Run linuxserver/ombi:4.53.10 with BASE_URL=/ombi and PUID/PGID set to a non-1001 user (e.g. 1000).
  2. Reverse-proxy the /ombi sub-path to the container.
  3. 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.

Activity

  1. github-actions commented on Jun 3, 2026

    @github-actions

    Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

  2. DRO34 commented on Jun 6, 2026

    @DRO34

    I have the same issue. How exactly do we fix this? I checked #124 but still don't understand what I am supposed to do. My ombi has worked fine for years now all of a sudden it stopped working around two days ago.

    Mine shows this

    /usr/bin/find: ‘/app/ombi/ClientApp/dist/index.html’: No such file or directory
    **** Permissions could not be set. This is probably because your volume mounts are remote or read-only. ****

    and also the base URL

    Error attempting to write Base URL, see here: https://docs.ombi.app/info/known-faults/#unauthorized-access-to-indexhtml

  3. mattgphoto commented on Jun 6, 2026

    @mattgphoto

    Ran into this as well. Claude gave me the workaround that works for now. I don't know the rules on posting AI based solutions, so I won't post it. This is #125 and I'm not sure how #124 helps, as it's been a few months with no downstream fix it seems like?

  4. DRO34 commented on Jun 6, 2026

    @DRO34

    Ran into this as well. Claude gave me the workaround that works for now. I don't know the rules on posting AI based solutions, so I won't post it. This is #125 and I'm not sure how #124 helps, as it's been a few months with no downstream fix it seems like?

    Sounds like using a different image works from #125? Roll back to the previous development build?

  5. moved this from Issues to Done in Issue & PR Trackeron Jun 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions