Everything works well before connecting with the telegram bot.
After setting everything up, the bot read the message but didn't reply.
I tried 1. reinstall the agent 2. revoke the bot api 3. create new bot 4. take down the firewall 5. changed privacy
but all ends up the same situation, the bot just don't reply me
#Telegram bot read the message but not replying
woven narwhal
dim cairn
Please send a debug report so we can see where the Telegram message is getting dropped:
hermes debug share
Also paste the output of:
hermes gateway status
And let us know whether you’re messaging the bot in a DM, a group, or a topic/thread.
woven narwhal
version: 0.12.0 (2026.4.30) [5d3be898]
os: Linux 6.6.87.2-microsoft-standard-WSL2 x86_64
python: 3.11.15
openai_sdk: 2.32.0
profile: default
hermes_home: ~/.hermes
model: gemini-2.5-flash-lite
provider: gemini
terminal: local
api_keys:
openrouter not set
openai not set
anthropic not set
anthropic_token not set
nous not set
google/gemini set
gemini not set
glm/zai not set
zai not set
kimi not set
minimax not set
deepseek not set
dashscope not set
huggingface not set
nvidia not set
ai_gateway not set
opencode_zen not set
opencode_go not set
kilocode not set
firecrawl not set
tavily not set
browserbase not set
fal not set
elevenlabs not set
github not set
features:
toolsets: hermes-cli
mcp_servers: 0
memory_provider: built-in
gateway: stopped (systemd (user))
platforms: telegram
cron_jobs: 0
skills: 89
dim cairn
the pastebin links are fine.
woven narwhal
hmmm
dim cairn
Please send the paste links from:
hermes debug share
The status output shows the gateway service is running, but the useful part is ellipsized right where the Telegram connection error is. The debug report includes the full gateway log, which is what we need here.
You can also run this if you want to paste the full service output directly:
systemctl --user status hermes-gateway.service -l --no-pager
But hermes debug share is preferred.
woven narwhal
2026-05-03 17:03:47,497 ERROR gateway.run: Gateway failed to connect any configured messaging platform: telegram: telegram connect timed out after 30s
2026-05-03 17:08:27,586 INFO hermes_cli.plugins: Plugin 'openai' registered image_gen provider: openai
2026-05-03 17:08:27,588 INFO hermes_cli.plugins: Plugin 'openai-codex' registered image_gen provider: openai-codex
2026-05-03 17:08:27,592 INFO hermes_cli.plugins: Plugin 'xai' registered image_gen provider: xai
2026-05-03 17:08:28,394 INFO hermes_cli.plugins: Plugin discovery complete: 9 found, 6 enabled
2026-05-03 17:08:30,508 INFO gateway.run: Starting Hermes Gateway...
2026-05-03 17:08:30,510 INFO gateway.run: Session storage: /home/lunak/.hermes/sessions
2026-05-03 17:08:30,510 INFO gateway.run: Agent budget: max_iterations=90 (agent.max_turns from config.yaml, or HERMES_MAX_ITERATIONS from .env, or default 90)
2026-05-03 17:08:31,040 INFO gateway.run: Connecting to telegram...
2026-05-03 17:08:31,206 INFO gateway.platforms.telegram_network: DoH discovery yielded no new IPs (system DNS: 149.154.166.110); using seed fallback IPs .........
2026-05-03 17:08:31,206 INFO gateway.platforms.telegram: [Telegram] Auto-discovered Telegram fallback IPs: .......
dim cairn
This is failing before Hermes gets to the reply/model step.
The important line is:
Gateway failed to connect any configured messaging platform: telegram: telegram connect timed out after 30s
So right now the Telegram gateway is not successfully connected. That means this is a Telegram network/connectivity path issue from inside your WSL2 environment, not a chat/personality/model issue yet.
Please send the full debug share links from:
hermes debug share
Also run this and paste the full output, without ellipsized lines:
systemctl --user status hermes-gateway.service -l --no-pager
The lines we need are the full Telegram connection errors around:
Primary api.telegram.org connection failed
Fallback IP ... failed
Connect attempt ... failed
If you are using a proxy or VPN, mention that too. There is a known related fallback-IP startup path being worked on, so the full gateway log will tell us whether you are hitting that path or a plain network block from WSL2 to Telegram.
woven narwhal
this is the full out put of "systemctl......"
hermes-gateway.service - Hermes Agent Gateway - Messaging Platform Integration
Loaded: loaded (/home/lunak/.config/systemd/user/hermes-gateway.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Sun 2026-05-03 17:32:03 EDT; 50s ago
Process: 424 ExecStart=/home/lunak/.hermes/hermes-agent/venv/bin/python -m hermes_cli.main gateway run --replace (code=exited, status=1/FAILURE)
Main PID: 424 (code=exited, status=1/FAILURE)
CPU: 1.880s
May 03 17:32:03 CL systemd[193]: hermes-gateway.service: Consumed 1.880s CPU time.
dim cairn
This is a network connection failure from WSL2 to Telegram, not a Hermes reply/model problem.
Hermes is trying both:
api.telegram.org
and the Telegram fallback IP:
149.154.167.220
Both are failing with httpx.ConnectError, then the gateway times out and systemd restarts it.
Please test basic Telegram connectivity from inside WSL2:
curl -v https://api.telegram.org
Then test the fallback IP path with Telegram’s hostname preserved:
curl -v --resolve api.telegram.org:443:149.154.167.220 https://api.telegram.org
If both fail, WSL2 cannot reach Telegram from that environment. In that case the fix is outside Hermes: VPN/proxy/DNS/network routing, or running the gateway somewhere that can reach Telegram.
If you do use a proxy/VPN, configure Hermes to use it for Telegram and restart the gateway:
TELEGRAM_PROXY=socks5://127.0.0.1:1080
Put that in ~/.hermes/.env with the correct proxy URL for your machine, then run:
systemctl --user restart hermes-gateway.service
There is also an open related fallback-IP startup fix being worked on here:
https://github.com/NousResearch/hermes-agent/pull/18702
But your current logs still show the main issue clearly: the gateway cannot establish any connection to Telegram from WSL2.
woven narwhal
I just checked it, both failed. I didn't use proxy, vpn. Others are also default, So it sounds like there's an issue with fallback-IP?
dim cairn
If both curl tests failed from inside WSL2, this is not primarily a fallback-IP issue.
The fallback-IP path is only Hermes’ second attempt after api.telegram.org fails. In your test, the normal Telegram hostname failed too, so the WSL2 environment itself cannot reach Telegram.
At that point Hermes has nothing to connect to. The gateway can only reply after it successfully connects to Telegram’s API, and your logs show it never gets that far.
First compare Windows vs WSL2:
In WSL2:
curl -v https://api.telegram.org
In Windows PowerShell:
curl.exe -v https://api.telegram.org
If it works from Windows but fails from WSL2, fix the WSL2 networking path. Things to try:
wsl --shutdown
Then reopen WSL and retest. If it still fails, check your WSL DNS/networking config:
cat /etc/resolv.conf
ip route
nslookup api.telegram.org
You may need to adjust WSL networking/DNS settings, especially if Windows can reach Telegram but WSL cannot. After WSL can reach https://api.telegram.org, restart Hermes:
systemctl --user restart hermes-gateway.service
If it fails from both Windows and WSL2, the network itself is blocking Telegram API access, so use a VPN/proxy or run the gateway from a network that can reach Telegram.
dim cairn
Were you able to get this resolved? I'm looking to close out stale threads.