[1.73.0] - 2026-07-05
- FIXED: A phone that dropped off mobile data could leave a Telegram proxy connection stuck - when a mobile client backgrounded Telegram or lost signal, its connection frequently died without a clean close, yet b4 held the half-dead session and its link out to Telegram open for many minutes, in some cases until the app was reopened, so returning to Telegram could mean waiting on a dead socket instead of a clean reconnect.
- FIXED: A stalled link out to Telegram over a WebSocket bridge could wedge a proxy session - if that link stalled mid-transfer, tearing the session down could itself block for many minutes on the stuck write, holding the client's slot and both connections until a kernel timeout expired.
- ADDED: Tunable MTProto connection timeouts - Settings → MTProto exposes a TCP user timeout and an idle timeout for the proxy, for unusual carrier networks or router kernels where the built-in defaults (about two minutes and five minutes) need adjusting or turning off.
- ADDED: API to list active MTProto sessions and clients - two HTTP endpoints for integrations: GET /api/mtproto/sessions returns one entry per live client connection (client IP and port, the Telegram destination, and when it connected and was last active), and GET /api/mtproto/active-clients groups those by secret (active connection count and the distinct client IPs using each one). The API exposed only a per-secret connection count, with no way to see the client addresses behind it.
What's Changed
- feat: implement tunable MTProto connection timeouts and improve sessi… by @DanielLavrushin in #269
- fix: update default timeout values for MTProto settings by @DanielLavrushin in #270
Full Changelog: v1.72.0...v1.73.0