MTProto

From HAProxy to VLESS+Reality: Overcoming DPI Blocks for MTProto Telegram Proxies

A detailed case study describes the challenges of running an MTProto proxy for Telegram on Russian servers facing ISP-level DPI. Initial attempts using HAProxy TCP relays and SOCKS5 tunnels failed because modern DPI systems detect MTProto and fake-TLS signatures regardless of transparent forwarding. The author eventually succeeded by layering mtg with an Xray VLESS+Reality tunnel that performs genuine TLS 1.3 handshakes to legitimate domains. Key configuration pitfalls included the xtls-rprx-vision flow breaking non-TLS payloads, missing mux causing handshake timeouts on short-lived connections, and provider-specific network policies. Final architecture places mtg and an Xray client on the Russian entry server while the foreign exit server runs Xray in VLESS+Reality inbound mode. The guide supplies complete docker-compose examples, key generation commands, and a checklist of common misconfigurations to avoid.

Over 20 VPN Services Hit by Outages After Russian Regulators Block Hosting Provider Subnets

Users of multiple VPN services reported widespread connection problems throughout the day as IP addresses belonging to several large hosting providers were placed under restrictions. The blocks targeted infrastructure used by VPNs to reroute traffic around content filters, causing entire ranges of servers to become inaccessible when whole subnets were affected. The Telegram channel Exploit reported that more than 20 VPN services of varying sizes experienced disruptions, though Roskomnadzor has not issued an official statement on the scope or origin of the measures. The affected providers indicated they are shifting customers to backup servers, noting that the restrictions appear selective yet still force frequent address changes during the day. The incidents coincide with ongoing discussions of new rules that would require hosting providers to independently detect and report masked VPN IP addresses to regulators. Similar large-scale subnet blocks occurred in late May, impacting numerous MTProto-based proxies and VPNs simultaneously.

TGLock 2.0 Restores Telegram Connectivity with Local MTProto Proxy Over WebSocket

Russian developer babin2002 has released TGLock 2.0, a free open-source application for Windows, macOS and Linux that helps users restore Telegram when the client remains stuck on the Connecting screen due to content filtering systems. The tool launches a local MTProto proxy and routes only Telegram traffic through an encrypted WebSocket tunnel to the messenger’s own web infrastructure, leaving all other network activity untouched. Unlike the first version, TGLock 2.0 now verifies that a working WebSocket tunnel has been established before displaying the “Telegram connected” status and automatically tries alternative routes when a connection drops. The application avoids disabling TLS verification, changing system DNS or importing third-party Cloudflare domain lists, although users may optionally supply their own Cloudflare Worker. A LAN mode allows a smartphone on the same network to use the computer as a proxy, but voice and video calls may fail because UDP traffic is not proxied. No Android version is currently available and the macOS build is not signed with a Developer ID certificate.