b4 Files

[1.62.0] - 2026-05-11

• ADDED: MTProto proxy works in censored networks - the built-in Telegram proxy can now reach Telegram over WebSocket, in addition to direct TCP. New "Upstream Transport" section in Settings → MTProto Proxy with three modes: Auto (WebSocket → TCP, the new default), WebSocket only, and Direct TCP. Existing installs are switched to Auto on upgrade, so networks without filtering see no change.
• ADDED: Cloudflare fallback for the MTProto proxy - optional "Cloudflare custom domain" field. If Telegram's own WebSocket endpoint is ever blocked too, pointing a Cloudflare zone at the Telegram data center IPs lets the proxy tunnel through Cloudflare instead.
• FIXED: MTProto proxy was incompatible with some Telegram clients - clients using transport variants other than padded-intermediate were silently dropped during the handshake. All three Telegram transport variants are now accepted, and the client's choice is forwarded to the data center.
• FIXED: Upstream SOCKS5 proxy routing did not work on some OpenWrt setups — traffic skipped the proxy and went straight to the internet on installs missing two required kernel modules. The modules are now installed and loaded automatically, and a clear error is shown if they are still missing. #221

What's Changed

• fix: improve single-instance check to prevent false "another b4 insta… by @DanielLavrushin in https://github.com/DanielLavrushin/b4/pull/220

Full Changelog: https://github.com/DanielLavrushin/b4/compare/v1.61.3...v1.62.0rc1