OpenClaw WhatsApp QR not working? Here is the fix

If your OpenClaw WhatsApp QR code never appears, expires instantly, or scans but never connects, the cause is almost always one of four things: stale session credentials, a gateway that is crash-looping, a protocol-version mismatch, or a phone that needs re-linking. Work through them in order — the first fix solves most cases.

Fix 1 — Clear stale WhatsApp session credentials (most common)

OpenClaw connects to WhatsApp through the Baileys library, which caches a session on disk. When that session goes stale, OpenClaw retries a silent login loop roughly every 30 seconds and never renders a fresh QR — the QR screen "thinks" forever with no WhatsApp activity in the logs. Stop the gateway, remove the WhatsApp auth/session folder for the channel, and restart to force a brand-new QR, then re-scan from your phone.

Symptom: QR spinner stuck, no [whatsapp] lines in the log, ~30s retry loop
Cause: stale Baileys session that can no longer resume
Fix: stop gateway → clear the WhatsApp session/creds folder → restart → re-scan a fresh QR

Fix 2 — Make sure the gateway is actually healthy

A WhatsApp QR can fail because the OpenClaw gateway itself is restarting in a loop. Bloated agent memory (oversized session logs or workspace files) makes every cold start take 40+ seconds, starves the event loop, and kills channel connectors before a QR renders. A "200 OK" on a public health URL does not prove the gateway is alive — a proxy can return 200 while the gateway behind it is dead. Check the process directly for crash-restart cycles.

Fix 3 — Rule out a control-UI protocol mismatch

Different OpenClaw builds speak different control-UI wire protocols. If the client offering the QR negotiation speaks a protocol the gateway does not, the gateway closes the socket instead of replying and the QR never completes. If you upgraded OpenClaw and WhatsApp pairing broke at the same time, suspect this — align your client and gateway versions or use a version-agnostic handshake.

Fix 4 — Re-link the device from your phone

If the QR scans but the session drops minutes later, the link is unstable. On your phone open WhatsApp → Linked devices, remove old entries, scan the fresh QR once, and keep the phone online during the first sync.

Or skip the whole problem

Every fix above is something you do yourself, at the moment WhatsApp breaks, on a server you maintain. ClawBud runs OpenClaw for you on a dedicated machine and handles WhatsApp pairing, stale-credential recovery, health monitoring and version upgrades automatically.

One-click WhatsApp pairing with managed credential recovery
Gateway health monitoring + automatic restart on crash-loops
Version-agnostic control-UI handshake
A dedicated VM per agent — not a shared container

Frequently asked questions

Why does my OpenClaw WhatsApp QR code never appear?

Most often a stale Baileys session is blocking a fresh QR — OpenClaw keeps trying to silently resume the old login. Stop the gateway, clear the WhatsApp session/credentials folder, and restart to force a brand-new QR. If that does not help, confirm the gateway is not crash-looping.

My QR scans but WhatsApp disconnects after a few minutes — why?

Usually an unstable link or a gateway restarting underneath it. Remove old linked-device entries on your phone, scan a fresh QR once, and confirm the OpenClaw gateway is healthy and not restarting every few minutes from memory bloat.

Can I avoid OpenClaw WhatsApp setup issues entirely?

Yes — a managed OpenClaw platform like ClawBud handles WhatsApp pairing, stale-credential recovery, health monitoring and upgrades for you on a dedicated machine, so these failure modes are handled automatically.

Start your free trial · See pricing