Open WebUI v0.6.0 Crashes After Initialization on Umbrel - Port 8080 Not Accessible
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12k
- Forks
- 793
- PR merge metrics
- No merged PRs in 30d
Description
Hi Umbrel team,
I'm running Open WebUI v0.6.0 on Umbrel, and it consistently crashes after initialization. The logs show it loading WEBUI_SECRET_KEY, SQLite database, and environment variables, ending with a CORS warning (WARNING: CORS_ALLOW_ORIGIN IS SET TO '*'), but then it restarts in a loop without starting the web server. Port 8080 is not open (verified with nc -l -p 8080), and the proxy (open-webui_app_proxy_1) fails with "The address 'open-webui_web_1' cannot be found", resulting in Connection reset by peer when accessing http://localhost:2876.
What I’ve tried: Restarted, reinstalled Open WebUI, updated Umbrel, stopped all other apps except Ollama (which works fine at 10.21.0.4:11434).
Status: Container shows Up X seconds (health: starting) then likely restarts (no shell access to debug further).
Logs: Attached below from sudo docker logs open-webui_web_1.
Any ideas on what’s causing this or how to fix it? Thanks!
LOGS:
WARNING: CORS_ALLOW_ORIGIN IS SET TO '*' - NOT RECOMMENDED FOR PRODUCTION DEPLOYMENTS.
Loading WEBUI_SECRET_KEY from file, not provided as an environment variable.
Loading WEBUI_SECRET_KEY from .webui_secret_key
/app/backend/open_webui
/app/backend
/app
INFO [alembic.runtime.migration] Context impl SQLiteImpl.
INFO [alembic.runtime.migration] Will assume non-transactional DDL.
INFO [open_webui.env] 'DEFAULT_LOCALE' loaded from the latest database entry
INFO [open_webui.env] 'DEFAULT_PROMPT_SUGGESTIONS' loaded from the latest database entry
WARNI [open_webui.env]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported sudo docker logs open-webui_web_1 output and the Open WebUI v0.6.0 container and proxy status. Reproduce the restart loop while checking port 8080 and the open-webui_app_proxy_1 connection; done means identifying the startup failure and restoring a reachable web server through the proxy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100