Hi,
I have this error when clicking “Show QR” trying to configured the Whatsapp channel in Openclaw:
Error: web login provider is not available
Is it working for you?
for me nothing is working on Openclaw on Umbrel. Maybe I am the issue but not sure. For sure it is a big pain
I tried to install openclaw but the system stuck and froze.
View your umbrelOS System Logs … maybe it will point out the error it is having with the install:
To view the logs from within Umbrel:
Settings, Troubleshoot, umbrelOS (View OS log)
It’s working now. I had tto edit manually openclaw.json. I can talk to the openclaw AI agent via Whatsapp.
Umbrel’s sandboxed packaging of OpenClaw (via its App Store and the getumbrel/openclaw-umbrel fork) introduces several limitations beyond just the restricted communication channels (e.g., only Telegram working reliably, WhatsApp unsupported). These stem from Umbrel’s design philosophy: prioritizing ease-of-use, security isolation, and minimal user intervention in a home-server context. This comes at the cost of flexibility compared to a native/direct install from the official openclaw/openclaw repo.The main additional limitations as I understand them:
1. Configuration Changes Often Ignored or Not Persisted
2. Limited or Broken CLI/Onboarding Functionality
3. Restricted Tool/Skill Execution and Integration
4. Model/Backend Flexibility Reduced
5. Update and Maintenance Quirks
6. General Sandbox Trade-Offs (Not Unique to OpenClaw but Amplified)
In short, Umbrel OpenClaw is great if you want zero-effort setup + Telegram-only + basic chat/skills in a plug-and-play home server. But for anything more — custom models, full channels, persistent configs, advanced tools/security tweaks, or CLI-driven workflows — the sandbox creates friction that native installs avoid.
1 Like