Hi, for some reason my OpenWebUI Installation is not reachable anymore under http://umbrel:2876/ on my raspberry pie. It used to work fine and I already tried to uninstall and reinstall ollama and OpenWebUI but no success…
Any ideas appreciated how to get this running again.
It sounds frustrating that your OpenWebUI installation on your Raspberry Pi isn’t reachable at http://umbrel:2876/ anymore, especially since it was working before. Let’s troubleshoot this step-by-step to get it running again. Since you’ve already tried uninstalling and reinstalling both Ollama and OpenWebUI without success, we’ll dig into common issues that could persist beyond a reinstall, focusing on networking, configuration, and system state. I’ll assume you’re still on the same network you had been on when it was working, and that you could reach it at the name:port like you’ve shown. Trying it by IP would be my first recommendation but… there’s more.
1. Verify the Services Are Running
First, let’s confirm that both Ollama and OpenWebUI are actually running on your Umbrel setup:
SSH into your Raspberry Pi: Use a terminal on another device and type ssh umbrel@umbrel.local (or replace with your Pi’s IP if .local doesn “‘t resolve).
Check running containers: Run docker ps to list active Docker containers. Look for entries with ollama/ollama and Package open-webui · GitHub (or similar, depending on the exact image versions from the Umbrel App Store).
If either is missing, it’s not starting properly. Check stopped containers with docker ps -a to see if they’re exiting immediately.
For any stopped container, view logs with docker logs <container_name> (e.g., docker logs open-webui). Look for errors like port conflicts, missing dependencies, or network issues.
2. Check Port and Networking
OpenWebUI on Umbrel typically runs on a custom port like 2876 (as you mentioned), assigned by Umbrel’s app management. If it’s not reachable:
Port conflict: Another service might have taken port 2876. Run sudo netstat -tuln | grep 2876 to see if anything’s listening on it. If something else is, you’ll need to stop that service or reconfigure OpenWebUI’s port via Umbrel’s app settings (if available) or Docker config.
Docker networking: Umbrel uses Docker, and sometimes the network configuration can glitch. Try restarting Docker: sudo systemctl restart docker. Then restart the apps via the Umbrel dashboard or with docker restart <container_name> for both Ollama and OpenWebUI.
Host resolution: Since you’re using http://umbrel:2876/, ensure your Pi’s hostname (umbrel) is still resolvable. From your client device (e.g., your laptop), ping it: ping umbrel.local. If it fails, use the Pi’s IP instead (e.g., http://192.168.x.x:2876/). Find the IP with hostname -I via SSH.
3. Umbrel App Store Reinstallation Check
Reinstalling via the Umbrel App Store should reset configs, but let’s ensure it’s clean:
Clear old data: Uninstalling doesn’t always remove persistent data. After uninstalling OpenWebUI and Ollama again (via the dashboard), check for leftover volumes: docker volume ls. If you see volumes like open-webui or ollama, remove them with docker volume rm <volume_name> (only if you don’t mind losing settings/models). Then reinstall.
App Store glitch: Occasionally, Umbrel’s app deployment can fail silently. After reinstalling, confirm the apps start by checking docker ps again.
4. Ollama Connection
OpenWebUI relies on Ollama as its backend. If Ollama isn’t running or reachable, OpenWebUI will fail:
Test Ollama standalone: By default, Ollama listens on port 11434. From your Pi, run curl http://localhost:11434/. You should see “Ollama is running.” If not, Ollama’s broken—check its logs (docker logs ollama).
OpenWebUI config: OpenWebUI needs to know where Ollama is. Umbrel usually sets this automatically, but post-reinstall, it might be misconfigured. Access OpenWebUI’s settings (if you can get it running briefly via IP) under “Settings > Connections” and ensure the Ollama URL is http://localhost:11434 (or the container name/IP if on a different network setup). If you can’t access the UI, you’d need to edit the Docker environment variable OLLAMA_BASE_URL—more on that below.
5. Raspberry Pi Resource Issues
Since it’s a Raspberry Pi, resource constraints could be at play:
Memory/CPU: Run htop or top via SSH to check if RAM or CPU is maxed out. OpenWebUI and Ollama can be heavy, especially with models loaded. If memory’s tight, try a lighter Ollama model (e.g., gemma:2b instead of larger ones) or free up resources by stopping other Umbrel apps.
SD card corruption: Frequent reinstalls or crashes can corrupt the SD card. If other Umbrel apps are also acting up, consider reflashing the Umbrel OS (back up data first via the dashboard).
6. Manual Docker Fix (Advanced and a bit crazy since the app store prob works okay)
If Umbrel’s App Store keeps failing, try a manual Docker setup to isolate the issue:
Stop and remove the Umbrel-installed containers: docker stop open-webui ollama && docker rm open-webui ollama.
Run Ollama: docker run -d -p 11434:11434 --name ollama ollama/ollama.
Run OpenWebUI: docker run -d -p 2876:8080 -e OLLAMA_BASE_URL=http://172.17.0.1:11434 --name open-webui Package open-webui · GitHub (adjust the IP—172.17.0.1 is Docker’s default gateway; use docker inspect ollama to find its exact IP if needed).
Test: http://:2876/. If this works, Umbrel’s deployment is the issue.
7. Logs and Community Help
If none of the above work, the logs are your best friend. Share the output of docker logs open-webui and docker logs ollama (first 20-30 lines or any errors) here or r/umbrel on Reddit. Mention your Pi model (e.g., Pi 4, 8GB) and Umbrel version (check via dashboard or cat /umbrel/version).
Quick Next Steps
Start with:
SSH in, run docker ps and docker logs for both apps.
