Skip to content

v1.76.2

Latest

Choose a tag to compare

@github-actions github-actions released this 12 Aug 20:22

[1.76.2] - 2026-08-12

  • FIXED: Photos, videos and stickers stopped loading in 1.76.0 and 1.76.1 - the data center Telegram serves media from was addressed under another one's name, so every media session was carried somewhere that could not serve it.
  • FIXED: Two of Telegram's addresses were carried to the wrong data center - they answer as data center 4, but sit inside a block b4 read as data center 2.
  • FIXED: Most of Telegram's addresses matched no data center, which left those connections almost no routes to try - b4 knew five address blocks, and nearly half the connections in a capture from a censored network fell outside all of them.
  • CHANGED: The address block b4 reads as data center 4 was narrowed to a quarter of its size - the 768 addresses dropped from it replied to nothing.
  • CHANGED: A Cloudflare Worker of your own is the last WebSocket route tried rather than the first - Cloudflare takes a worker back part-way through a session, well after the connection is made, so it passed every check while video failed on it.
  • FIXED: A route that took a request and returned nothing was handed the next connection anyway - only a route that went quiet mid-session, with a request still outstanding, was ranked down.
  • CHANGED: The Cloudflare Worker script in the documentation holds its relay open longer - Cloudflare could cut off the part carrying data back from Telegram the moment the connection was accepted. Set the worker's compatibility date to 2026-04-07 or later.
  • FIXED: tgprobe never tested the shared Cloudflare pool - it started from a blank configuration, so every on/off setting in it read as off.
  • CHANGED: The Cloudflare Worker is asked for a data center address without a port - data center 203 does not answer on 5222, one of the three ports Telegram serves the same endpoint on, so passing the port on killed media connections. The script in the Telegram documentation is again the tg-ws-proxy script unchanged, and a Worker deployed from either page needs nothing done to it.

What's Changed

  • fixes: address media loading issues in DC 203 and improve Cloudflare … by @DanielLavrushin in #301

Full Changelog: v1.76.1...v1.76.2