authentication_error | Friends of the Crustacean 🦞🤝 | Page 1

limpid stump Jan 26, 2026, 12:24 PM

#

i'm getting HTTP 401: authentication_error: Invalid bearer token (request_id: req_011CXVyzfWLZS3z1MZBqpHx3), how can i fix this?

#

?

unkempt hollyBOT Jan 26, 2026, 12:25 PM

#

limpid stump ?

Hey! 👋 🦐 I see you're in the #authentication_error channel — looks like you might be running into some trouble with Clawdbot authentication.

What's going on? Feel free to share any error messages or describe what's happening, and I'll help you figure it out!

Just a quick reminder: before troubleshooting, it helps to know your Clawdbot version. If you can run clawdbot --version and share that, it often saves us some back-and-forth. 🦐

limpid stump Jan 26, 2026, 12:27 PM

#

i have clawdbot set up on a vps, and i set up telegram, but when i write anything in telegram i get this error: HTTP 401: authentication_error: Invalid bearer token (request_id: req_011CXVzFqFeAT8EVJ9bHRimz)

version: root@ubuntu-8gb-nbg1-1:~# clawdbot --version
2026.1.24-3

#

?

#

hello?

unkempt hollyBOT Jan 26, 2026, 12:36 PM

#

limpid stump hello?

Hey there! 👋 🦐 Yep, I'm still here!

Just making sure I saw your question — are you still having authentication trouble with Clawdbot? If so, any details you can share would help:

What error message are you seeing?
Clawdbot version (clawdbot --version)
What platform (Discord, WhatsApp, etc.)?

The more context, the faster I can help! 🦐

limpid stump Jan 26, 2026, 12:37 PM

#

i have clawdbot set up on a vps, and i set up telegram, but when i write anything in telegram i get this error: HTTP 401: authentication_error: Invalid bearer token (request_id: req_011CXVzFqFeAT8EVJ9bHRimz)

version: root@ubuntu-8gb-nbg1-1:~# clawdbot --version
2026.1.24-3

unkempt hollyBOT Jan 26, 2026, 12:38 PM

#

limpid stump i have clawdbot set up on a vps, and i set up telegram, but when i write anythin...

Ah, that error! 🔑 HTTP 401 authentication_error means Clawdbot can't authenticate with Telegram's API.

This is almost always one of these issues:

1. Check your Telegram bot token

The token format should be: 123456789:ABCdefGHIjklMNOpqrsTUVwxyz

Run this to verify it's set:

echo $TELEGRAM_BOT_TOKEN

If nothing shows up, the env var isn't set properly.

2. Common fixes:

Restart the gateway after setting the token:

#

  clawdbot gateway restart

Check for extra spaces in the token (copy/paste carefully!)
Verify the bot still exists with @BotFather on Telegram

3. Where to set it:

Environment variable: TELEGRAM_BOT_TOKEN=your_token_here
Or in config file (usually ~/.clawdbot/config.json5 or similar)

Can you run echo $TELEGRAM_BOT_TOKEN and let me know what it shows (you can mask the actual token, just tell me if it's empty or has a value)? 🦐

limpid stump Jan 26, 2026, 12:40 PM

#

this is what i see root@ubuntu-8gb-nbg1-1:~# echo $TELEGRAM_BOT_TOKEN

root@ubuntu-8gb-nbg1-1:~# echo $5939864885
939864885
root@ubuntu-8gb-nbg1-1:~# echo 5939864885
5939864885
root@ubuntu-8gb-nbg1-1:~#

#

@unkempt holly ?

unkempt hollyBOT Jan 26, 2026, 12:44 PM

#

limpid stump <@1457407575476801641> ?

Yep, I see you! 🦐 Just waiting on you to run that command:

echo $TELEGRAM_BOT_TOKEN

Just tell me: empty or has a value (you don't need to show the actual token) — that will tell me if the token is even being picked up by Clawdbot!

limpid stump Jan 26, 2026, 12:47 PM

#

Error: No provider plugins found. Install one via clawdbot plugins install.
root@ubuntu-8gb-nbg1-1:~# cat ~/.clawdbot/agents/main/agent/auth-profiles.json
{
"version": 1,
"profiles": {
"anthropic:claude-cli": {
"type": "oauth",
"provider": "anthropic",
"access": "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",
"refresh": "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",
"expires": 1769445311665
},
"anthropic:default": {
"type": "token",
"provider": "anthropic",
"token": "sk-ant-oat01-gJLdYj5Ue9eIGF-bwgWQCp4OfT_I1SmfdHONp5iHaY_maiZeC2ZCrG6fLPG3P7HVzg5"
}
},
"lastGood": {
"anthropic": "anthropic:default"
},
"usageStats": {
"anthropic:default": {
"errorCount": 0,
"lastFailureAt": 1769430432552,
"lastUsed": 1769430432561
}
}
}

#

????

unkempt hollyBOT Jan 26, 2026, 12:48 PM

#

limpid stump Error: No provider plugins found. Install one via `clawdbot plugins install`. ro...

Ah, I see the issue now! 🔍

The auth-profiles.json you showed me is for Anthropic (model provider), not Telegram. Those are two different things:

Anthropic = which AI model to use ✓ (looks fine)
Telegram = messaging platform integration — this needs a plugin!

Fix:

1. Install the Telegram plugin:

clawdbot plugins install telegram

2. Set your Telegram bot token:

#

export TELEGRAM_BOT_TOKEN="your_bot_token_here"

Or add it to your config file. Then:

3. Restart the gateway:

clawdbot gateway restart

The "No provider plugins found" error means Clawdbot doesn't have the Telegram plugin installed yet. That's why it's failing to authenticate — it literally doesn't know how to talk to Telegram!

Let me know once you've installed the plugin and set up the token. 🦐

unkempt hollyBOT Jan 26, 2026, 12:48 PM

#

limpid stump ????

Simpler version:

Run this command:

clawdbot plugins install telegram

Then set your token:

export TELEGRAM_BOT_TOKEN="your_bot_token_here"

Restart:

clawdbot gateway restart

#

That's it! The plugin gives Clawdbot the ability to talk to Telegram. Without it, you get that 401 error. 🦐

limpid stump Jan 26, 2026, 12:48 PM

#

how do i get my bot token?

unkempt hollyBOT Jan 26, 2026, 12:49 PM

#

limpid stump how do i get my bot token?

Easy! 🎯

Open Telegram and search for @BotFather (the official Telegram bot creator)
Start a chat with BotFather
Send this command:
```
/newbot
```
Follow the prompts:
- Give your bot a name
- Give it a username (must end in "bot")
BotFather will give you a token — copy it!

The token looks like:

123456789:ABCdefGHIjklMNOpqrsTUVwxyz

#

Save that token, then set it in Clawdbot as I showed before. 🦐

limpid stump Jan 26, 2026, 12:50 PM

#

Done! Congratulations on your new bot. You will find it at t.me/mark_asd_mark_bot. You can now add a description, about section and profile picture for your bot, see /help for a list of commands. By the way, when you've finished creating your cool bot, ping our Bot Support if you want a better username for it. Just make sure the bot is fully operational before you do this.

Use this token to access the HTTP API:
8477149307:AAG2p1e73Fbsoy1zLr8SvKlzv4PMx95eWxk
Keep your token secure and store it safely, it can be used by anyone to control your bot.

For a description of the Bot API, see this page: https://core.telegram.org/bots/api

#

where do i set my bot id?

#

@unkempt holly ?

unkempt hollyBOT Jan 26, 2026, 12:53 PM

#

limpid stump where do i set my bot id?

You don't set it in a config file usually — just export it as an environment variable before starting Clawdbot:

Quickest way:

export TELEGRAM_BOT_TOKEN="your_token_here"
clawdbot gateway restart

Or add it permanently to your shell profile (~/.bashrc or ~/.zshrc):

echo 'export TELEGRAM_BOT_TOKEN="your_token_here"' >> ~/.bashrc
source ~/.bashrc
clawdbot gateway restart