Telegram Proxy not working: what to check
If Telegram Proxy is not working, in 9 cases out of 10 one of three things is to blame: the proxy server is dead, its port has been blocked by the operator, or you entered the wrong secret. Telegram has no built-in proxy diagnostics, so the client just silently stays at “Connecting”, and the source of the problem can only be found by checking step by step.
Telegram supports two proxy types: SOCKS5 and MTProto Proxy. These are different protocols. SOCKS5 is standard, has no encryption inside the tunnel, and is easily recognized by TSPU filtering systems. MTProto Proxy is Telegram’s own design, disguises itself as ordinary TLS traffic, and holds up noticeably better against DPI, but for that same reason it regularly becomes a blocking target.
Below is a step-by-step list of what to check before deciding that “the proxy is dead” and looking for a new one.
In short
- Open Settings → Data and Storage → Proxy and make sure the proxy is enabled and marked as Connected.
- Check that the secret was copied in full, without spaces and without an extra “dd” at the beginning.
- Try disabling the proxy: if Telegram connects without it, the issue is with the proxy itself, not the network.
- SOCKS5 proxies in Russia are widely cut off by DPI — switch to MTProto.
- MTProto proxies from public channels last from hours to weeks; keep 2–3 working backups.
- If nothing helps, check whether the required port is open at all on your operator’s network.
Why Telegram Proxy stops working
A proxy in Telegram is not a “bypass button”, but simple rerouting of client traffic through a third-party server. Any link in the chain can break.
The server is dead or overloaded
Public MTProto proxies from Telegram channels are often rented VPS instances serving several thousand users. They last until the first IP block, payment failure, or load spike. The symptom is constant “Connecting” in all chats.
The port was blocked by the operator
If the port is non-standard (for example, 443, 8443, 31337), the operator may not pass outbound traffic to this port over UDP/TCP at all. Then the proxy is unavailable from this network even though the server itself is alive. Check by trying the same proxy over mobile internet from another operator.
Wrong secret
Modern MTProto proxies use a secret format with an ee (fake-TLS) or dd prefix. If you copy only part of the string, lose the prefix, or insert an extra space, the client will not connect. Connecting through a t.me/proxy?... link is safer than entering it manually.
DPI recognized the MTProto signature
Basic MTProto mode without fake-TLS is easy for DPI to detect. That is why a proxy that is really alive today is almost always MTProto with fake-TLS, disguised as an HTTPS connection to the specified domain.
How to understand what exactly broke
| Symptom | Possible cause | What to check |
|---|---|---|
| The proxy is marked red in the list | The server is unavailable or the secret is wrong | Connect using a fresh t.me/proxy link |
| The proxy is Connected, but messages are not sent | There is a channel, but Telegram cannot reach its DCs | Change the proxy, check another operator |
| Telegram connects without the proxy, but not with it | The proxy itself is to blame | Use another MTProto server |
| The proxy works on Wi-Fi but not on LTE | The operator is blocking the proxy port | Switch to a proxy with another port (443/8443) |
| SOCKS5 connects, but everything is slow and often disconnects | DPI is slowing down proxy traffic | Switch to MTProto fake-TLS |
| The proxy worked, then died after a day | The server was blocked or the secret was changed | Take a new one from a trusted channel |
How to check right now
If it seems that Telegram is not working “for everyone”, but you are not sure, compare it with measurements from other operators and regions. Freedom Checker regularly checks the availability of Telegram and related services from different probes, so you can see whether the problem is local or not.
At the same time, check whether any ordinary website opens without a VPN or proxy. If the internet works, but Telegram is silent, the issue is almost certainly with the proxy server. The MTProto Proxy specification and client updates are published in the official Telegram documentation.
Failure or blocking?
A failure of a specific proxy is a one-server story: it went down, became overloaded, or the owner ran out of money. The symptom is that another proxy from another channel immediately works.
Blocking is when proxies from different providers fail in bulk on one operator’s network. Then the issue is already DPI, which has started aggressively cutting the MTProto/SOCKS5 signature. If none of the tested proxies works on this same network, the problem can no longer be solved at the proxy level — you need a full VPN with obfuscation.
What to pay attention to
- Connect using a t.me/proxy link — this eliminates manual input errors.
- Keep 2–3 different proxies in the list — Telegram will switch to a working one by itself.
- MTProto fake-TLS lasts longer than basic MTProto and much longer than SOCKS5.
- Proxies from “free lists of 5000 servers” are usually 90% dead.
- If a proxy requires a username/password, it is SOCKS5, and in Russia it works worst of all.
- On iOS and Android, proxy settings are not synchronized between devices.
- Never enter a proxy from a dubious source in the Telegram account where you chat with your bank: the proxy owner can see your IP and the fact that you connected.
Conclusion
Telegram Proxy breaks for one of three reasons: the server died, the operator blocked the port, or you entered the wrong secret. Before changing the proxy, check whether Telegram works without it and whether the proxy works on a second operator. This immediately filters out half of the scenarios.
If it becomes clear that the problem is not the network, but specifically proxy blocking by your operator, switch to obfuscated MTProto fake-TLS or to a full VPN.