🌱 Welcome to Factnetize — honest, well-researched articles on tech, health and AI. Get the weekly →
Agentic AI

Hermes Telegram not working: every error message and its fix

Find your exact Hermes Telegram error message, see when Hermes shows it, and apply the fix that goes with it.

Hermes Telegram not working: a phone on a desk showing a chat message without a reply, with a desktop PC in the background

⚡ Key takeaways

  • Hermes checks Telegram in a fixed order. The message you get tells you how far it came.
  • A silent bot with no message at all usually means the gateway is not running.
  • Network errors retry on their own. A rejected token and a token that is in use elsewhere need you.

When you search for “Hermes Telegram not working”, you have one of two things in front of you: a bot that stays silent, or a sentence from Hermes that you do not know what to do with. This page lists those sentences word for word, as they stand in the Hermes source code on November 15, 2026, with when Hermes shows each one and the fix. Setting Telegram up for the first time is a separate guide: Hermes Telegram setup.

Hermes Telegram not working: where the message is

  • The Messaging page. Open Messaging → Telegram in Hermes Desktop or the dashboard and click Test. The answer is one of the messages below.
  • The gateway log. Platform errors are written there too. Open a terminal, PowerShell on Windows, and run:
hermes logs gateway

Check in this order

The test asks the same four questions every time and stops at the first one that fails. The sections below follow that order.

  1. Is Telegram switched on?
  2. Is the bot token saved?
  3. Is the gateway running?
  4. Did Telegram accept the connection?

After those four comes one more: who may talk to the bot.

The bot says nothing at all

Start at question 3. The first time I set this up, nothing came back in the chat, because the agent was not running. Run hermes gateway status. If the gateway runs, click Test on the Messaging page and look up the answer below.

1. Is Telegram switched on?

“Telegram is disabled. Enable it, then restart the gateway.”

The platform is switched off, even if the token is still saved. Switch Telegram on with the toggle on the Messaging page, then run hermes gateway restart.

“No messaging platforms enabled.”

This is a line in the gateway log, followed by “Gateway will continue running for cron job execution.” The gateway runs, but no platform is on, so it only runs your scheduled jobs. Switch Telegram on and restart the gateway.

2. Is the bot token saved?

“Missing required setup” or “Platform setup is incomplete.”

A required setting is empty. The first form names it, for example TELEGRAM_BOT_TOKEN. In the log the same problem reads “No bot token configured”. Enter the token on the Messaging page, or run hermes gateway setup in a terminal. Create with QR also works, but it creates a new bot.

3. Is the gateway running?

“Gateway is not running. Restart the gateway to connect this platform.”

The settings are fine, but the process that talks to Telegram is not there.

  1. Run hermes gateway status.
  2. Run hermes gateway start.
  3. Run hermes gateway install once. On Windows the gateway then starts when you log in.

4. Did Telegram accept the connection?

“Telegram bot token rejected”

The full text ends with “The token is invalid or was revoked — generate a new one with @BotFather and update TELEGRAM_BOT_TOKEN.” Hermes does not retry this one.

  1. Send /revoke, then /token, to @BotFather.
  2. Run hermes gateway setup and paste the new token.
  3. Run hermes gateway restart.

“Telegram polling could not recover after 5 retries (200s total wait)”

Telegram lets one process at a time fetch the messages for a bot, and another session is polling with the same token. In Hermes’s words: “The previous gateway session is still held open on Telegram’s servers, or another process is using the same bot token.” Hermes retries in the background, so an old session of your own clears by itself.

“telegram bot token is in use elsewhere”

This follows when the conflict does not clear. Hermes stops trying and says why: “another process (another machine or a leftover gateway) kept polling it through 3 reconnects. Stop that poller, then run ‘hermes gateway restart’.” Look for a second Hermes with the same token, for example on another PC or a server, and give each one its own bot.

“Telegram startup failed” and “Telegram reconnect task wedged”

Hermes marks both as retryable: it reconnects by itself. Check your internet connection.

“Setup looks complete, but the gateway has not reported a connection yet. Restart the gateway.”

This is what is left when all four questions pass on paper: Telegram is on, the token is saved, the gateway runs, yet it has reported neither a live connection nor an error. Run hermes gateway restart, then click Test again.

Connected, but who may talk to the bot?

“Telegram is connected, but no users are authorized yet”

The bot works, but nobody may use it. Hermes shows this when no user ID is saved and nobody is paired. The message goes on: “set TELEGRAM_ALLOWED_USERS, approve a pairing request, or enable pairing for new users.” Pick one:

  • Add your user ID. Message @userinfobot in Telegram; it replies with your number. Run hermes gateway setup and enter it.
  • Approve the pairing code. If the bot answered you with a code, run hermes pairing approve telegram followed by that code. A code expires after one hour.

“Telegram is connected.” and “Connected. 1 user allowlisted via TELEGRAM_ALLOWED_USERS.” mean it works. One message looks fine and is not: “Gateway is open: GATEWAY_ALLOW_ALL_USERS is set.” Anyone who finds your bot can then use your agent. Securing Hermes in local mode covers who may message your bot.

What’s next

When the bot answers but your scheduled jobs do not arrive, the cause is on the scheduler side: see why your Hermes cron jobs fail.

This article is part of the Agentic AI series.

John Lock
Written by

John Lock

The Tested Weekly

One email a week with the guides we tested, sources linked. No spam.

Leave a comment

Your email address will not be published. Required fields are marked *

Weekly · No spam

The Tested Weekly

One email a week with the guides we tested, sources linked.