#Telegram pairing fails + gateway auth issues on macOS 10.15 (Intel iMac)

1 messages · Page 1 of 1 (latest)

sonic sandal
#

Hi — I’m trying to run ClawdBot locally and pair a Telegram bot, but pairing never completes. I’ve already gone through the docs and logs in detail.

Goal
• Run ClawdBot locally
• Pair Telegram so messages can be sent/received

What happens instead
• Telegram bot responds with a pairing code
• clawdbot pairing approve telegram <CODE> returns:

No pending pairing request found for code

•    clawdbot status --all shows:

Gateway unreachable (unauthorized: gateway token missing)

•    Control UI logs repeatedly show token_missing

Environment
• macOS 10.15.7 (Catalina)
• iMac Late 2013 (Intel i5, HDD)
• Node v22.22.0 (nvm)
• ClawdBot 2026.1.24-3
• Gateway: local, loopback (127.0.0.1:18789)

What I’ve tried
• Manual + LaunchAgent gateway
• Fresh pairing codes, immediate approval
• Verified profile usage
• Checked pairing list before approval
• Reviewed gateway + error logs

Question

Is this a known limitation on macOS 10.15 / older Intel Macs, or am I missing a required gateway auth setup step?
Happy to move to a VPS if local reliability on this OS is not supported — just want to confirm.

Happy to paste logs if helpful. Appreciate any help.

polar cedarBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

thin domeBOT
# sonic sandal Hi — I’m trying to run ClawdBot locally and pair a Telegram bot, but pairing nev...

Based on my research, this is a known gateway auth configuration issue, not a macOS 10.15 limitation. Here's what's happening and how to fix it:

Root Cause

The error "gateway token missing" and "No pending pairing request found" are connected problems:

  • Your CLI can't authenticate with the gateway because it doesn't have the token
  • The gateway needs proper auth config to track pairing requests

The Fix

  1. Set the correct token config key (this is the common mistake):

    # Wrong (deprecated/ignored): gateway.token
# Correct: gateway.auth.token

  2. Force reinstall the gateway to sync configs:

# 
   moltbot gateway install --force --profile ~/your-profile

  1. Get your gateway token:

    moltbot gateway status
# Look for the token in the output, or check ~/.moltbot/your-profile/config.json

  2. Restart the gateway:

    moltbot gateway restart

  3. Try pairing again - now the CLI and gateway share the same auth context

#

Key Docs

If Still Stuck

Run moltbot gateway status --all and check if Config (cli) and Config (service) match - they often don't when you've edited config while the service was running. The --force reinstall fixes this.

Your older Intel iMac can absolutely run this - it's a config issue, not a hardware limitation. 🦐