AgentFixboard

Telegram gateway won't connect: 'do_request' is read-only

After pulling the latest Docker image, the Telegram gateway keeps failing to connect and retries in a loop.

From GitHub

NousResearch/hermes-agent

Difficulty
Easy
Time
~5 min
Steps
2
Fixed in
v2026.7.20
Last checked

Verified fix: PR #64574 merged on . Fixed in v2026.7.20 (first release published after the merge). Last checked .

Symptom

After pulling the latest Docker image, the Telegram gateway keeps failing to connect and retries in a loop.

Evidence what you'll see

  • Failed to connect to Telegram: 'HTTPXRequest' object attribute 'do_request' is read-only
  • Repeats after each DNS-over-HTTPS fallback attempt
  • Started right after an upgrade

Cause

On Python 3.13 the Telegram library's request object no longer has an instance __dict__, so patching do_request on the instance raises an error.

Fix steps

0 of 2 done

Your check marks stay in this browser only.

Verify the fix worked

  • Restart the gateway and confirm the log no longer shows the read-only error and Telegram messages arrive.

Sources and credit

Summarized in our own words from these public reports. Credit goes to their authors.

Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change

Hit an error we don't cover? Submit it