Repository navigation
[BUG] Ombi not loading #125
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
Page does not load, white screen, logs show no issues.
Expected Behavior
Home page splash screen should load when accessing
Steps To Reproduce
Latest development build seems to have triggered this issue, not sure what went wrong.
Rolling back to [development-v4.55.2-ls448] seems to fix the issue for me
Environment
- OS: Unraid
- How docker service was installed:
Unraid Community AppsCPU architecture
x86-64
Docker creation
Used default CA settingsContainer logs
Connection to 127.0.0.1 3579 port [tcp/*] succeeded!
[migrations] started
[migrations] no migrations found
───────────────────────────────────────
██╗ ███████╗██╗ ██████╗
██║ ██╔════╝██║██╔═══██╗
██║ ███████╗██║██║ ██║
██║ ╚════██║██║██║ ██║
███████╗███████║██║╚██████╔╝
╚══════╝╚══════╝╚═╝ ╚═════╝
Brought to you by linuxserver.io
───────────────────────────────────────
To support the app dev(s) visit:
Ombi - Patreon: https://patreon.com/tidusjar
Ombi - PayPal: https://paypal.me/PlexRequestsNet
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 99
User GID: 100
───────────────────────────────────────
Linuxserver.io version: v4.55.2-ls448
Build-date: 2026-02-14T22:47:18+00:00
───────────────────────────────────────
[custom-init] No custom files found, skipping...
Hello, welcome to Ombi
Valid options are:
Ombi 4.55.2+b3779577b36abb979af22d77a702da8c03b54a7b
Copyright (C) 2026 Ombi
--host (Default: http://*:5000) Set to a semicolon-separated (;) list of
URL prefixes to which the server should respond. For example,
http://localhost:123. Use "localhost" to indicate that the server
should listen for requests on any IP address or hostname using
the specified port and protocol (for example,
http://localhost:5000). The protocol (http:// or https://) must
be included with each URL. Supported formats vary between
servers.
--storage Storage path, where we save the logs and database
--baseurl The base URL for reverse proxy scenarios
--demo Demo mode, you will never need to use this, fuck that fruit
company...
--migrate Will run the migrations then exit the application
--help Display this help screen.
--version Display version information.
Base Url: /ombi
Wrote new baseurl at /app/ombi/ClientApp/dist/index.html
We are running on http://*:3579
/app/ombi
[ls.io-init] done.
Activity
github-actions commentedon Mar 13, 2026
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
goose-ws commentedon Mar 19, 2026
I believe this is an issue related to PUID/PGID not being properly set? Looking at the
index.htmlin the container shows it as being owned by UID/GID 1001:1001. In my case, I have my env vars set to1003:998respectively.Edit 1:
Rolling back to amd64-4.53.4 fixes it for me.
Edit 2:
I looks like PR 124 solves this, but the PR was merged on March 4, and the current
:developmentimage tag is from March 1. I think it's just a case of needing a new image to be build/pushed?rollo1996 commentedon Mar 22, 2026
i have the same ish issue, it states "Unauthorized access to Index.html". since its running in a container i dont know if i can persistently change write rights?
Stylee32 commentedon Mar 22, 2026
@rollo1996 You can enter the container and run the following: chown -R PUID:PGID /app/ombi/ClientApp/dist (replacing them with what you've set them to), restart and it should work. Obviously, this is only a short term solution as if the container is removed etc then the changes are lost.
thespad commentedon Mar 22, 2026
#124 was targeted against the wrong branch. Development has changed the index.html path, stable hasn't.
I've pushed fixes to both branches that should have resolved the issue (at least until the next stable release).
rollo1996 commentedon Mar 22, 2026
Issue has been solved for me now. Running the container on unraid
devilsaintus commentedon Mar 25, 2026
Issue resolved on latest (development-v4.57.3)
Many thanks