MTProxy is a proxy protocol for Telegram. Fake-TLS adds a TLS-shaped start to an MTProxy connection. The WEB proxy uses a separate HTTPS transport with t.me/webproxy links. TGProxy Panel manages servers and user secrets; telemt handles the connections.
Practical differences
| Property | MTProxy | Fake-TLS | WEB |
|---|---|---|---|
| Connection start | Obfuscated MTProxy transport | TLS-shaped handshake, then MTProxy | HTTPS and WEB transport |
| Link | t.me/proxy | t.me/proxy with an ee… secret | t.me/webproxy |
| Endpoint | Address and port in the link | Address and port in the link; panel default 8443 | HTTPS domain, usually port 443 |
| Panel use | Underlying protocol; panel-managed tproxy-server nodes expose WEB links only | Links for telemt users | Links for telemt and tproxy-server |
WEB support depends on the Telegram client’s platform and version. The project documents Telegram Desktop as the main supported option and Android as experimental. Test your client and retain Fake-TLS as an alternative. Client support can change over time.
How Fake-TLS works
Telegram uses the proxy address, port and secret from the link. The connection starts by imitating a TLS handshake containing a configured masking domain. That domain can differ from the proxy address: these are separate settings, not a requirement to reuse one hostname everywhere.
The panel also installs a cover website on the node’s HTTPS domain. A normal browser sees the site, while Telegram uses its proxy transport. Masking cannot guarantee availability with every ISP: an IP address, hostname, port or route to Telegram may still be blocked.
How the WEB proxy works
WEB connects to the server’s HTTPS domain. Depending on the engine and configuration, it uses HTTPS, HTTPS lanes, WebSocket or WebSocket lanes. Automatic selection looks for a suitable transport; a fixed configuration may limit the choice.
WEB and Fake-TLS links represent different connection methods. Do not edit secret prefixes by hand: use the link generated by the panel or subscription page. A reachable cover website and valid certificate alone do not prove the proxy can forward a request to Telegram.
Which link to send
Send one subscription link. Its page suggests options for the device and lists all direct links and QR codes. Try Fake-TLS first; if the client supports WEB, compare both in the same network. Testing through another network helps narrow down a connection problem.
Backup masking domains provide extra Fake-TLS links. They may help with restrictions on the main hostname, but do not replace a backup server or repair a hosting provider’s failed route to Telegram.
Why use a panel with telemt?
telemt is the proxy engine. TGProxy Panel provides fleet management: users and secrets, subscriptions, quotas, cover websites, checks, statistics and updates. It sends settings to agents and the engine’s control API; it does not carry user proxy traffic.
The panel is free and open source under AGPL-3.0, for use with your own VPS hosts and domains. Start with the installation guide. Check compatibility and configuration details in the project reference and telemt repository.
Automate users and servers with the management API: personal tokens, permission scopes and working examples.