Telegram does not connect

1. 1

   Update Telegram

   Old builds fail on current MTProto. It is the cheapest step, so it goes first.

2. 2

   Switch the server and the port

   On the order page pick another Server, press Add to Telegram, and Telegram adds the new address with your secret already in it. Try both ports, 443 and 8443, on each server. Work down the list: a blocked route is usually one server, not all of them.

3. 3

   Leave the secret alone

   The secret on the order page is always the current one and is never the cause. Only the server and the port change.

4. 4

   Compare Wi-Fi and mobile data

   If every server and both ports fail, the block is on your network. In Russia MTProto is actively filtered, especially on mobile data, so it can work on Wi-Fi and drop on the mobile network.

5. 5

   Try a WEB proxy on Telegram Desktop

   It hides Telegram inside ordinary HTTPS, which is what this kind of filtering looks for. It is a better chance, not a guarantee. See WEB proxy.

A free proxy works and mine does not#

Free public proxies run on other servers, and blocks hit addresses one by one. The answer is another server from the list on your order page, not a different product.

Networks with a whitelist mode#

Some mobile networks let through only an approved list of services. Neither MTProto nor WEB passes such a network, and no setting changes that.

Telegram with a SOCKS5 proxy#

If you entered an ISP or datacenter proxy into Telegram as SOCKS5, use the SOCKS5 port, which is the HTTP port plus one. The HTTP port in the SOCKS5 field never connects.