[1.76.1] - 2026-08-11
- FIXED: Telegram never got past loading, with an empty chat list, in the WebSocket bridge routing mode - the bridge only ever went through a Cloudflare Worker, never Telegram's own route, the one the MTProto proxy had been taking all along.
- FIXED: A Cloudflare Worker that had stopped passing traffic kept being picked for new Telegram connections - a session on a dead one was held for five minutes before it was given up.
- FIXED: The WebSocket bridge sent traffic to a different data center address than the device had asked for - it kept one address per data center, while Telegram hands out many.
- FIXED: Connections b4 opens for itself went out with none of its own bypass applied - a fail-open connection, made when a destination is already in trouble, was the one it left most exposed.
- FIXED: b4 put its routing rules back only once they had disappeared completely - part of a rule set going missing counted as healthy.
- CHANGED: The Cloudflare Worker script b4 pointed at ignored the port it was asked for - Telegram reaches a data center on a second port too, and those connections were answered by nothing. A script that reads the port is in the Telegram documentation; a Worker set up from the older page has to be deployed again.
What's Changed
- feat: implement self-dial mark and relay stall reporting by @DanielLavrushin in #300
Full Changelog: v1.76.0...v1.76.1
Contributors
DanielLavrushin