Why is WhatsApp stuck at logging in after QR/linking succeeds?

A stale session or incomplete reconnect state can leave the channel marked as linked while runtime status stays disconnected or logged out.

What is the fastest recovery path?

Stop the channel, remove old session state, start again, and relink once from a fresh browser/device session.

How do I verify the fix?

Dashboard should show Linked: Yes, Running: Yes, Connected: Yes, and test send/receive should succeed.

Fix WhatsApp Linking Stuck at "logging in"

Common Symptoms

Linking ... logging in never finishes
Dashboard shows Linked: Yes but Running: No or Connected: No
Error eventually becomes logged out

This usually means the WhatsApp session state is inconsistent: pairing partially succeeded, but runtime reconnect failed. A clean reset and single relink flow resolves most cases.

Field report: openclaw/openclaw#4686.

Next Step

Fix now, then reduce repeat incidents

If this issue keeps coming back, validate your setup in Doctor first, then harden your config.

Open Doctor Harden Config

Need proactive alerts? Join Monitor early access.

Jump to Fix

Step 1: Stop channel + gateway Step 2: Clear stale session state Step 3: Start and relink once Step 4: Verify connected state

Step 1: Stop channel and gateway

Stop before reset

openclaw gateway stop
openclaw gateway status

Step 2: Clear stale WhatsApp session state

Remove only WhatsApp session artifacts for the affected channel/profile, then restart. If you are unsure about exact file names, back up your config directory first.

Backup then clean session state

# backup first
cp -R ~/.openclaw ~/.openclaw.backup.$(date +%Y%m%d%H%M%S)

# then remove stale whatsapp auth/session cache for the broken channel
# (path differs by install mode; remove only whatsapp session artifacts)

Step 3: Start and relink once (clean flow)

Clean relink

openclaw gateway start
openclaw gateway status

# Open dashboard, trigger WhatsApp link, scan QR once
# Avoid parallel relink attempts from multiple devices/sessions

If state flips between linked and logged out repeatedly, do not retry in a loop. Stop, clear stale session state once, then relink from a single fresh session.

Step 4: Verify success

Dashboard status: Linked Yes / Running Yes / Connected Yes

No logged out error after restart

Incoming and outgoing WhatsApp test messages succeed

Related Guides

Gateway Status on Headless Linux

systemctl --user unavailable and service runtime issues

Connection Errors

ECONNREFUSED and localhost reachability checks

Did this guide solve your problem?