OpenClaw v2026.3.22 Breaks Dashboard UI and WhatsApp. Here's the Fix.
If you just ran npm i -g openclaw@latest and your dashboard is throwing 503s or your WhatsApp channel went silent — you're not alone. v2026.3.22 shipped with two packaging bugs that break things th...

Source: DEV Community
If you just ran npm i -g openclaw@latest and your dashboard is throwing 503s or your WhatsApp channel went silent — you're not alone. v2026.3.22 shipped with two packaging bugs that break things that worked fine in v2026.3.13. Here's what's broken, why, and how to fix it in 30 seconds. Symptom 1: Dashboard Returns 503 After upgrading to v2026.3.22, hitting your gateway's web UI gives you: 503 Service Unavailable Control UI assets not found No dashboard. No web interface. Just that error. Root cause: The dist/control-ui/ directory is missing from the npm tarball. The built frontend assets simply weren't included in the package. If you diff the v2026.3.13 tarball against v2026.3.22, you'll see the entire dist/control-ui/ tree is absent. This is tracked at github.com/openclaw/openclaw/issues/52808. Symptom 2: WhatsApp Channel Is Dead Your WhatsApp integration stops working entirely. Gateway logs show: plugin not found: whatsapp (stale config entry ignored) Messages aren't sent. Messages a