Telegram Stuck on Connecting? Set Up a Proxy (SOCKS5/MTProto) 2026
Telegram installs fine, then sits on “Connecting” and messages never leave. That is usually network, not a bad build: servers are overseas, and many networks need an in-app proxy.
Persistent Connecting or clock icons on outbound messages → fix the proxy before reinstalling. Path: Settings → Data and Storage → Proxy Settings. Add a working SOCKS5 or MTProto node and enable it. Dead nodes and typos in host/port/secret explain most “I added a proxy and it still fails” cases.
Connection vs install—then mobile and desktop setup
Endless Connecting means network/proxy. Missing client: use the download page. Site blocked: access guide.
- Settings → Data and Storage → Proxy Settings
- Add Proxy → SOCKS5 or MTProto
- Enter host, port, credentials/Secret
- Save and enable until status shows connected
iOS and Android paths match. Prefer trusted providers over random public proxies. Desktop: Settings → Advanced → Connection type → Use custom proxy—desktop does not inherit the phone’s proxy. More: desktop guide.
SOCKS5 vs MTProto—and when it still fails
| SOCKS5 | MTProto | |
|---|---|---|
| Protocol | Generic | Telegram-specific |
| Obfuscation | Average | Often stronger |
| Availability | Most tools | Needs MTProto nodes |
| Restricted nets | Node-dependent | Often steadier |
Use what you already have; try MTProto first when both are available.
| Check | Verify | Action |
|---|---|---|
| Node alive | Same node opens an overseas site | Replace if dead |
| Host/port/Secret | Character-by-character | Re-enter and enable |
| System clock | Automatic time | Turn auto time on |
| Client age | Official latest | Update |
After you connect—and when to stop
Then finish signup/login: registration, SMS issues. Flaky proxies also delay pushes—see notification fixes.
| Symptom | Check first | Avoid |
|---|---|---|
| Stuck Connecting | In-app proxy vs system VPN clash | Reinstall loops / modded APKs |
| Connected but cannot send | New node or protocol | Assuming a permanent ban |
| Phone works, PC fails | Configure desktop separately | Expecting phone sync of proxies |
| Chat works stably | Stop | Pasting login codes into “free node” pages |
FAQ
Why is Telegram stuck on "Connecting"?
Telegram’s servers are blocked on some networks (notably mainland), so a direct connection just spins on "Connecting" and messages won’t send. The fix is to add a working SOCKS5 or MTProto proxy under Settings → Data and Storage → Proxy Settings and enable it, after confirming the node can reach other overseas sites.
What is the difference between SOCKS5 and MTProto proxies?
SOCKS5 is a general-purpose proxy protocol offered by most proxy tools; MTProto is Telegram’s own protocol with better obfuscation that is harder to detect and block. Both let Telegram reach its servers. On restrictive networks MTProto is usually more stable — use whichever you have, the setup is nearly identical.
I added a proxy but still can’t connect — now what?
First confirm the node itself works by opening an overseas site through it. Then re-check the address, port and password; for MTProto verify the Secret. Dead or blocked nodes are the most common cause, so try another. An incorrect system clock can also break the handshake — enable automatic time.
Is it safe to use random free MTProto proxies from the web?
Not recommended. Unknown public proxies may log traffic, inject ads, or be used for phishing. Prefer a provider you control or a trusted private node. A proxy only solves connectivity — it does not replace two-step verification and the rest of your account security checklist.
I already run a system VPN — do I still need an in-app proxy?
Not always. If a global VPN already opens overseas sites, Telegram can often connect without an in-app proxy. If the VPN only routes some apps, or Telegram still spins, add SOCKS5/MTProto inside the app. When both are on, avoid conflicts — keep whichever layer actually delivers stable send/receive and turn the other off to test.
The proxy shows Connected but messages still won’t send — what next?
“Connected” only means the handshake worked, not that the node can reach Telegram reliably. Try one layer at a time (turn off an extra system VPN), switch nodes or try SOCKS5 vs MTProto, then check for rate limits or account restrictions. Follow the same order as “still not connecting” in the article — don’t jump straight to reinstalling.
Does the proxy I set on my phone automatically apply to Telegram Desktop?
No. Phone and desktop are separate sessions; you configure the proxy in each app (or at the system level on that device). If Desktop stays on Connecting, set Connection type / VPN on the computer instead of only watching the phone proxy.
SOCKS5 vs MTProto — which should I use, and can I enable both?
Use whichever node is stable; MTProto is often tuned for Telegram, SOCKS5 is more generic. Usually enable one working proxy — juggling many makes debugging harder. Trust the source first, then pick a protocol.
I already have a system VPN — do I still need an in-app proxy?
Often the system VPN is enough; if you still see Connecting, add an in-app proxy as a supplement. If they conflict, try one at a time. Don’t install a modded client that bundles “double proxy” for this.
Need the installer or platform notes?
The download page lists versions, requirements, and install entry points.
Open download page