Error

[heady plinth]

The error is clear and well-documented! When you set channels.telegram.dmPolicy="open", you're telling the bot to accept DMs from anyone. For security, this requires explicitly adding "*" to the allowFrom list to confirm you want public access.

Fix: Add "*" to your Telegram allowFrom config:

{
  channels: {
    telegram: {
      dmPolicy: "open",
      allowFrom: ["*"],  // ← Add this line (or add "*" to existing array)
      // ... your other settings
    }
  }
}

If you already have specific users in allowFrom, add "*" alongside them:

allowFrom: ["tg:123456789", "*"]

Alternative: If you don't actually want public DMs, change dmPolicy back to "pairing" (the default) or "allowlist" instead of "open".

After updating the config, restart the gateway scheduled task again. 🦐

[terse girder]

how do i restart the gateaway?

[heady plinth]

Option 1: PowerShell (quickest)

Stop-ScheduledTask -TaskName "Clawdbot Gateway" -ErrorAction SilentlyContinue
Start-ScheduledTask -TaskName "Clawdbot Gateway"

Or one-liner:

Get-ScheduledTask -TaskName "Clawdbot Gateway" | Start-ScheduledTask

Option 2: Task Scheduler GUI

1. Open Task Scheduler
2. Find Clawdbot Gateway in the task list
3. Right-click → Disable → wait a sec → Enable (or use Run)

Option 3: Command Prompt

schtasks /end /TN "Clawdbot Gateway" && schtasks /run /TN "Clawdbot Gateway"

After restarting, check if it's running:

Get-ScheduledTask -TaskName "Clawdbot Gateway" | Select-Object State

Should show Running if it started successfully! 🦐