Whats app not working | Friends of the Crustacean 🦞🤝 | Page 1

wet snow Jan 29, 2026, 5:01 AM

#

When I first started using the clawdbot with whatsapp it was working fine, then all of a sudden it is not working anymore. I asked clawdbot to fix it but it says No active WhatsApp Web listener (account: default) also in the chennels section it says whatsapp is disabled. How can I fix this?

marsh frostBOT Jan 29, 2026, 5:04 AM

#

wet snow When I first started using the clawdbot with whatsapp it was working fine, then ...

Based on the docs, this is a common WhatsApp issue. Here's how to fix it:

Quick Fix Steps

1. Check if Gateway is Running

The "No active WhatsApp Web listener" error typically means the gateway isn't running:

clawdbot gateway status

If stopped, start it:

clawdbot gateway start

2. Re-link WhatsApp (if gateway is running but still failing)

If the gateway is running but WhatsApp still shows disabled, you likely need to re-authenticate:

#

# List current status
clawdbot channels status

# Re-link by scanning QR code
clawdbot channels login

Then scan the QR code via WhatsApp → Settings → Linked Devices → "+".

3. Check Full Status

clawdbot status --all

Look for WhatsApp section - it should show linked: true.

4. Check Logs if Still Broken

#

clawdbot logs --follow

Look for "whatsapp" or "web" errors.

Common Causes

Gateway stopped - Most likely cause, just restart it
Session expired - WhatsApp sessions occasionally expire, relogin fixes
Credentials corrupted - ~/.clawdbot/credentials/whatsapp/default/creds.json may be bad; logout + re-login
Bun runtime - If using Bun, WhatsApp is unreliable; use Node instead

Let me know what clawdbot status --all shows and I can help troubleshoot further! 🦐

wet snow Jan 29, 2026, 5:08 AM

#

@marsh frost This is what clawdbot status --all says

📎 message.txt

marsh frostBOT Jan 29, 2026, 5:10 AM

#

wet snow <@1457407575476801641> This is what clawdbot status --all says

Found the issue! Looking at the status output:

Channels
┌──────────┬─────────┬────────┬────────────────────────────────────────────────┐
│ Channel  │ Enabled │ State  │ Detail                                         │
├──────────┼─────────┼────────┼────────────────────────────────────────────────┤
│ WhatsApp │ OFF     │ OFF    │ disabled                                       │
└──────────┴─────────┴────────┴────────────────────────────────────────────────┘

WhatsApp is disabled in your config. The gateway is running, but WhatsApp isn't enabled.

Fix: Enable WhatsApp

Option 1: Quick CLI fix (if you have config editing enabled)

#

clawdbot config set channels.whatsapp.dmPolicy allowlist
clawdbot config set channels.whatsapp.allowFrom "+1234567890"  # your number

Option 2: Edit config manually

Edit ~/.clawdbot/clawdbot.json and add:

{
  "channels": {
    "whatsapp": {
      "dmPolicy": "allowlist",
      "allowFrom": ["+1234567890"]  # Replace with your WhatsApp number in E.164 format
    }
  }
}

#

Then link WhatsApp

clawdbot channels login --channel whatsapp --account default

Scan the QR code via WhatsApp → Settings → Linked Devices → "+".

Note: There's also a separate issue - your agent is missing an Anthropic API key (check the logs). But let's fix WhatsApp first, then tackle that if needed. 🦐

wet snow Jan 29, 2026, 5:11 AM

#

It gave me this error "Error: Config validation failed: channels.whatsapp.allowFrom: Invalid input: expected array, received number"

#

@marsh frost

marsh frostBOT Jan 29, 2026, 5:14 AM

#

wet snow It gave me this error "Error: Config validation failed: channels.whatsapp.allowF...

The allowFrom needs to be an array (even for one number). Try:

clawdbot config set 'channels.whatsapp.allowFrom' '["+1234567890"]'

Note the single quotes around the whole value and double quotes inside the array. The brackets [] make it an array.

Or just edit the config file directly - it's often easier. 🦐

wet snow Jan 29, 2026, 5:15 AM

#

This is what it says now "Updated channels.whatsapp.allowFrom. Restart the gateway to apply." @marsh frost

#

So I restarted the gateway but the channel still says disabled. @marsh frost

marsh frostBOT Jan 29, 2026, 5:21 AM

#

wet snow So I restarted the gateway but the channel still says disabled. <@14574075754768...

Ah, the dashboard shows Linked: Yes but Running: No and Connected: No. The session is stale.

Fix Steps:

Click "Logout" first (clears the broken session)
Click "Show QR" to generate a fresh QR code
Scan it with WhatsApp: Settings → Linked Devices → "+"
After scanning, WhatsApp should show as Running: Yes and Connected: Yes

The "Linked: Yes" was a stale session that had disconnected. Fresh QR + scan will fix it! 🦐

wet snow Jan 29, 2026, 5:23 AM

#

So I scanned the QR code but on the whatsapp app it says Couldn't link device Try again later.

#

@marsh frost

#

@marsh frost

#

Hello @marsh frost

#

Can you please help me @marsh frost

#

@marsh frost

marsh frostBOT Jan 29, 2026, 5:48 AM

#

wet snow <@1457407575476801641>

Hey! Did the QR scan work? Let me know if:

✅ WhatsApp is now working
❌ Still showing disabled/running no - if so, share the new status screenshot

I'm here to help get it working! 🦐

wet snow Jan 29, 2026, 5:49 AM

#

No it didn't @marsh frost

#

The new QR code did not scan @marsh frost

#

It gave an error

marsh frostBOT Jan 29, 2026, 5:51 AM

#

wet snow No it didn't <@1457407575476801641>

Need more info to debug:

New screenshot - What's the status now after trying to scan?
Did the QR code appear? (Sometimes it takes 10-20 seconds)
What happens when you click "Show QR" - does anything show up?
Check logs - Run this in terminal and share what you see:

clawdbot logs --tail 50 | grep -i whatsapp

The more detail you share, the faster I can help! 🦐

marsh frostBOT Jan 29, 2026, 5:51 AM

#

wet snow The new QR code did not scan <@1457407575476801641>

Let's skip the dashboard and use the CLI instead - it's more reliable:

clawdbot channels login --channel whatsapp --account default

This should output a QR code in your terminal. Scan it with WhatsApp (Settings → Linked Devices → "+").

If you get an error or no QR appears, share what it says. 🦐

wet snow Jan 29, 2026, 5:53 AM

#

error: unknown option '--tail'```

Also it is still showing this

#

@marsh frost

#

Also currently this is what my config looks like:

"channels": {
    "whatsapp": {
      "accounts": {
        "default": {
          "enabled": true,
          "dmPolicy": "pairing",
          "groupPolicy": "allowlist",
          "debounceMs": 0
        }
      },
      "dmPolicy": "allowlist",
      "selfChatMode": false,
      "allowFrom": [
        "+8080123456"
      ],
      "groupPolicy": "allowlist",
      "mediaMaxMb": 50,
      "debounceMs": 0
    }
  },

@marsh frost

marsh frostBOT Jan 29, 2026, 5:58 AM

#

wet snow ```clawdbot logs --tail 50 | grep -i whatsapp error: unknown option '--tail'```...

The "Bad Request" error suggests something's stuck. Let's try:

1. Restart the gateway:

clawdbot gateway restart

2. Then try login again:

clawdbot channels login --channel whatsapp --account default

3. If that fails, check full logs:

clawdbot logs | tail -30

marsh frostBOT Jan 29, 2026, 5:58 AM

#

wet snow <@1457407575476801641>

Did the gateway restart work? Share what happened when you ran:

clawdbot gateway restart
clawdbot channels login --channel whatsapp --account default

If you get any errors, paste them here. The "Bad Request" error won't clear until we get the gateway unstuck. 🦐

#

Share what you see after running these commands. The "Bad Request" error means the gateway is rejecting the request - a restart usually clears that. 🦐

wet snow Jan 29, 2026, 5:59 AM

#

Here is my logs. @marsh frost

📎 message.txt

marsh frostBOT Jan 29, 2026, 6:00 AM

#

wet snow Here is my logs. <@1457407575476801641>

It's fixed! 🎉

Look at the logs:

✅ Linked! Credentials saved for future sends.

The WhatsApp login worked via CLI! Your credentials are now saved.

Next steps:

Refresh the dashboard - WhatsApp should now show as linked/connected
Test it - Send a message via WhatsApp to yourself and see if Clawdbot responds

If the dashboard still shows weird, try:

#

clawdbot channels status

Let me know if it's working now! 🦐

wet snow Jan 29, 2026, 6:02 AM

#

Here are the logs:

bash-3.2$ clawdbot channels status

🦞 Clawdbot 2026.1.24-3 (885167d)
   If it's repetitive, I'll automate it; if it's hard, I'll bring jokes and a rollback plan.

│
◇  
Gateway reachable.
- WhatsApp default: enabled, configured, linked, stopped, disconnected, dm:pairing, allow:+8080123456, error:disabled

Tip: status --deep adds gateway health probes to status output (requires a reachable gateway).
bash-3.2$

@marsh frost

#

Also I am now getting this when I want to generate a new QR code since I deleted my link device. @marsh frost

marsh frostBOT Jan 29, 2026, 6:05 AM

#

wet snow Also I am now getting this when I want to generate a new QR code since I deleted...

The dashboard is stuck showing the old error. Your CLI login already worked earlier (we saw "✅ Linked! Credentials saved").

Try these steps:

Refresh the browser page (F5 or Cmd+R)
Check CLI status:

clawdbot channels status

If still stuck, re-login via CLI:

clawdbot channels login --channel whatsapp --account default

If QR times out in CLI too, restart gateway first:

#

clawdbot gateway restart
# wait 5 seconds
clawdbot channels login --channel whatsapp --account default

The dashboard UI sometimes gets out of sync. The CLI is the reliable way to link/unlink. Let me know what clawdbot channels status shows! 🦐

wet snow Jan 29, 2026, 6:07 AM

#

Why the heck does it still say disabled?? What can cause this? I already did everything you said. Please find a way to fix this! @marsh frost

marsh frostBOT Jan 29, 2026, 6:09 AM

#

wet snow Why the heck does it still say disabled?? What can cause this? I already did eve...

I hear your frustration. Let's get to the bottom of this.

The "disabled" status is likely coming from your config file. Let me check:

clawdbot config get channels.whatsapp

Also check your full config:

clawdbot config get channels

Share the output - I bet WhatsApp is explicitly set to false or disabled: true in there. 🦐

wet snow Jan 29, 2026, 6:11 AM

#

Here is the output:

bash-3.2$ clawdbot config get channels.whatsapp

🦞 Clawdbot 2026.1.24-3 (885167d) — Turning "I'll reply later" into "my bot replied instantly".

{
  "accounts": {
    "default": {
      "enabled": true,
      "dmPolicy": "pairing",
      "groupPolicy": "allowlist",
      "debounceMs": 0
    }
  },
  "dmPolicy": "allowlist",
  "selfChatMode": false,
  "allowFrom": [
    "+8086738055"
  ],
  "groupPolicy": "allowlist",
  "mediaMaxMb": 50,
  "debounceMs": 0
}
bash-3.2$ clawdbot config get channels

🦞 Clawdbot 2026.1.24-3 (885167d)
   I can't fix your code taste, but I can fix your build and your backlog.

{
  "whatsapp": {
    "accounts": {
      "default": {
        "enabled": true,
        "dmPolicy": "pairing",
        "groupPolicy": "allowlist",
        "debounceMs": 0
      }
    },
    "dmPolicy": "allowlist",
    "selfChatMode": false,
    "allowFrom": [
      "+8080123456"
    ],
    "groupPolicy": "allowlist",
    "mediaMaxMb": 50,
    "debounceMs": 0
  }
}
bash-3.2$ 

``` @marsh frost

marsh frostBOT Jan 29, 2026, 6:12 AM

#

wet snow Here is the output: ``` bash-3.2$ clawdbot config get channels.whatsapp 🦞 Claw...

Config looks correct - WhatsApp is enabled. The issue is somewhere else.

Let's check if the gateway is actually loading WhatsApp:

clawdbot gateway status

Check the gateway config specifically:

clawdbot config get web

Also check your full config file for any enabled: false anywhere:

clawdbot config get

#

The config shows WhatsApp should be enabled, but the dashboard says "disabled". This might be:

A gateway config issue (web.enabled)
Something in the full config overriding it
The gateway not picking up the WhatsApp module

Share all three outputs above! 🦐

wet snow Jan 29, 2026, 6:14 AM

#

Here is my logs:

bash-3.2$ clawdbot gateway status

🦞 Clawdbot 2026.1.24-3 (885167d)
   I don't just autocomplete—I auto-commit (emotionally), then ask you to review (logically).

│
◇  
Service: LaunchAgent (loaded)
File logs: /tmp/clawdbot/clawdbot-2026-01-28.log
Command: /usr/local/bin/node /Users/josephcauton/.npm-global/lib/node_modules/clawdbot/dist/entry.js gateway --port 18789
Service file: ~/Library/LaunchAgents/com.clawdbot.gateway.plist
Service env: CLAWDBOT_GATEWAY_PORT=18789

Config (cli): ~/.clawdbot/clawdbot.json
Config (service): ~/.clawdbot/clawdbot.json

Gateway: bind=loopback (127.0.0.1), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.

Runtime: running (pid 4699, state active)
RPC probe: ok

Listening: 127.0.0.1:18789
Troubles: run clawdbot status
Troubleshooting: https://docs.clawd.bot/troubleshooting
bash-3.2$ clawdbot config get web

🦞 Clawdbot 2026.1.24-3 (885167d)
   If you're lost, run doctor; if you're brave, run prod; if you're wise, run tests.

{
  "enabled": false
}
bash-3.2$ clawdbot config get
error: missing required argument 'path'
bash-3.2$

#

@marsh frost

wet snow Jan 29, 2026, 6:29 AM

#

I actually fixed it. I needed to turn enable web

#Whats app not working

Quick Fix Steps

1. Check if Gateway is Running

2. Re-link WhatsApp (if gateway is running but still failing)

3. Check Full Status

4. Check Logs if Still Broken

Common Causes

Fix: Enable WhatsApp

Option 1: Quick CLI fix (if you have config editing enabled)

Option 2: Edit config manually

Then link WhatsApp

Fix Steps: