wacli client outdated | Friends of the Crustacean 🦞🤝 | Page 1

wide star Apr 14, 2026, 7:39 AM

#

Client outdated (405) connect failure (client version: 2.3000.1030403648)
QR channel closed

lyric oceanBOT Apr 14, 2026, 7:39 AM

#

stray ospreyBOT Apr 14, 2026, 7:41 AM

#

That one is usually not a pairing/config mistake.

Client outdated (405) means WhatsApp rejected the Web client version, so the QR flow closes right after.

First, what does this print?

openclaw --version

Then, if you are not fully up to date, update OpenClaw and the WhatsApp plugin first, then retry:

openclaw plugins update @openclaw/whatsapp
openclaw doctor
openclaw channels status --probe

#

openclaw channels login --channel whatsapp

Also make sure you are running the gateway on Node, not Bun.

If it still fails after updating, paste:

openclaw status --all
openclaw logs --follow

Relevant docs:
https://docs.openclaw.ai/help/faq
https://docs.openclaw.ai/install/updating
https://docs.openclaw.ai/channels/whatsapp

#

If you paste the version + probe/log output, I can narrow it down fast.

wide star Apr 14, 2026, 7:42 AM

#

it is wacli

stray ospreyBOT Apr 14, 2026, 7:43 AM

#

Ah, got it, for wacli specifically this is a whatsmeow/WhatsApp Web compatibility problem, not a bad QR.

Client outdated (405) means WhatsApp rejected the client version your current wacli build is using. QR channel closed is just the follow-up symptom.

I’d check these first:

wacli --version
wacli doctor
wacli auth

And make sure you’re on the latest wacli build:

if installed via Homebrew, upgrade it
if built from source, rebuild from the latest main

If you’re already on the newest build and still get the same 405, it usually means upstream whatsmeow needs a compatibility bump, so there may not be a local fix yet.

#

Paste wacli --version and whether you installed via brew or source, and I’ll point you at the next step.

wide star Apr 14, 2026, 7:46 AM

#

@stray osprey

l ~ % wacli --version
wacli doctor
wacli auth
wacli 0.2.0
STORE /Users/lunardi/.wacli
LOCKED false
AUTHENTICATED false
CONNECTED false
FTS5 true
Starting authentication…
14:45:36.515 [Client/Socket ERROR] Error reading from websocket: failed to get reader: failed to read frame header: EOF
14:45:36.515 [Client ERROR] Client outdated (405) connect failure (client version: 2.3000.1030403648)
QR channel closed

stray ospreyBOT Apr 14, 2026, 7:46 AM

#

Nice, that narrows it down a lot.

Your local state looks fine, this is not a bad store or a stuck login.
The important bit is wacli 0.2.0 plus:

Client outdated (405)

That usually means your wacli build is behind the WhatsApp Web version currently being accepted.

I checked wacli main, and it already tracks a newer whatsmeow snapshot than the 0.2.0 release, so the next move is:

Update/rebuild wacli from latest main
Retry wacli auth

I would not wipe ~/.wacli yet, since you are not authenticated anyway.

If a fresh build from latest main still gives the same 405, then it is probably an upstream whatsmeow/WhatsApp break, not your machine. In that case, please file it here with the exact output:

#wacli client outdated