Connect Telegram Through a Proxy on Android (Full Setup)
Connect Telegram Through a Proxy on Android (Full Setup)
This is the version of the proxy guide I wish someone had handed me the first time a client asked why their Telegram kept disconnecting on a phone in a hotel. The official Android client has proxy support built in, it works, and it is not hard. The hard part is everything Android does around it: battery optimization that quietly kills the connection, dual-SIM routing that sends your traffic out the wrong interface, and ISPs that block the ports your proxy listens on.
I run managed Telegram hosting on dedicated Singapore hardware, so I see the difference between a proxy that technically connects and a proxy that actually holds an account in good standing for months. We will do the setup first, then I will be honest about what a random proxy can and cannot do for you.
what you will end up with
By the end of this you will have a Telegram account on Android routing every connection through a proxy you control or rent. Telegram will show the small shield icon next to the connection status, your traffic to Telegram’s data centers will egress from the proxy’s IP instead of your phone’s carrier IP, and the connection will survive the screen turning off.
That last point is the one most guides skip. A proxy that drops the moment the phone sleeps is worse than no proxy, because Telegram notices the flapping. We will fix it.
If you are still deciding between proxy types before you start, read MTProto vs SOCKS5 vs cloud phone for Telegram first. The short version: MTProto is purpose-built for Telegram and harder for a network to fingerprint and block, SOCKS5 is generic and works for everything, and a cloud phone is a different model entirely where the account never lives on your handset.
before you start
A few things to have ready, because chasing them mid-setup is annoying.
1. The proxy credentials. For MTProto you need a server host or IP, a port, and a secret (a hex string, sometimes prefixed with dd or ee for the newer obfuscated formats). For SOCKS5 you need host, port, and usually a username and password. If you were handed a tg:// link instead, that is even easier and we cover it below.
2. A clear idea of what the proxy IP actually is. This matters more than people think. A datacenter IP, a recycled residential IP, and a clean mobile IP behave very differently from Telegram’s side. If you do not know the difference yet, what is a mobile IP and why Telegram cares explains why carrier-grade IPs get treated more gently than a server in a hosting rack.
3. The current Telegram app, not a fork. Forks like some unofficial clients handle proxy settings differently and a few have shipped bugs that leak DNS outside the tunnel. Stick to the official client from Google Play or the APK from telegram.org for this walkthrough.
4. Your phone off battery saver. Turn it off entirely for the setup so you are not debugging a connection problem that is actually a power problem. We re-enable selective settings at the end.
the step-by-step
Here is the full path through the Android client. Menu labels are stable across recent versions.
1. Open proxy settings. Tap the hamburger menu, then Settings, then Data and Storage. Scroll to the Proxy Settings entry near the bottom and tap it. On some builds it sits under a Connection sub-menu, but Data and Storage is the reliable route.
2. Enable the proxy toggle and add a server. Turn on Use Proxy at the top, then tap Add Proxy. You will be asked to choose a type: MTProto Proxy or SOCKS5.
3. Fill in the fields. For MTProto enter the server, the port, and paste the secret exactly as given, including any ee/dd prefix. For SOCKS5 enter server, port, and the username and password if your provider issued them. Leave username and password blank only if your provider explicitly runs open SOCKS, which is rare and usually a bad sign for IP quality.
4. Save and select it. Tap the checkmark to save. The proxy appears in the list. Tap it so the radio button fills in. Telegram will try to connect immediately.
5. Watch the connection status. At the top of your chat list the status text cycles through Connecting, then Updating, then disappears when connected. A shield icon next to it confirms proxy mode is active. If it sits on Connecting for more than fifteen seconds, the proxy or the port is the problem, not the app.
If you were given a tg:// import link instead of raw fields, you do not touch any of the menus above. The link carries everything. The format looks like this:
tg://proxy?server=proxy.example.sg&port=443&secret=ee1a2b3c4d5e6f00112233445566778899
Tap that link in any app on the phone (a note, a message, a browser address bar) and Android hands it to Telegram, which opens a dialog asking if you want to enable the proxy. Confirm, and you are done. For a SOCKS5 link the scheme is tg://socks with user and pass parameters instead of secret. Note the literal & between parameters; if you copy a link and the ampersands got mangled into something else, the import will fail silently.
6. Verify you are actually routed. Connecting is not the same as routed-and-leak-free. Send a message, load a channel, confirm media downloads. Then check the egress IP from the phone’s side and confirm it matches the proxy, not your carrier. The cleanest way to be sure nothing is leaking around the tunnel is the procedure in how to test if your Telegram proxy is leaking. Do this once per proxy. A proxy that connects but leaks your real IP on voice calls or media fetches is giving you false confidence.
what can go wrong
This is the section that earns its keep. Android has three failure modes that look like proxy problems but are not.
1. Battery optimization kills the connection. This is the big one. Android’s Doze and per-app battery restriction will throttle or suspend Telegram’s network sockets when the screen is off. The symptom is messages that only arrive when you open the app, and a proxy that “drops” overnight. The fix: go to Settings, Apps, Telegram, Battery, and set it to Unrestricted (the label varies by manufacturer; Samsung calls it Unrestricted, others say Don’t optimize or No restrictions). On Xiaomi, Oppo, and Vivo phones you also have to lock the app in the recents tray and grant Autostart, because those skins are far more aggressive than stock Android. Until you do this, no proxy will hold a stable session on that phone.
2. Dual-SIM routes traffic out the wrong interface. If the phone has two SIMs, Android picks one for mobile data. The proxy connection rides whatever the active data SIM is. If you intended to egress through a specific carrier (say you wanted the connection going out over your M1 line, not StarHub), check Settings, Connections, SIM Manager, and set the mobile data SIM explicitly. When the phone hands off between Wi-Fi and mobile data, the proxy reconnects, which is normal; if it reconnects constantly, your Wi-Fi and mobile data are fighting and you should pin one for the session.
3. Blocked ports. Many networks, especially corporate Wi-Fi, hotel Wi-Fi, and some mobile carriers, block outbound traffic on non-standard ports. If your MTProto proxy listens on port 8443 or some random high port and you cannot connect on one network but can on another, the port is being filtered. The fix is a proxy that listens on 443, the HTTPS port, which almost nobody blocks because doing so breaks the entire web. Good MTProto providers run on 443 for exactly this reason. If you control the proxy, move it to 443.
4. A blank or stale secret. If you upgraded a proxy from an old non-obfuscated secret to an ee format, the old saved entry will fail. Delete the proxy from the list and re-add it rather than editing in place; Telegram caches some connection state per entry and editing does not always clear it.
5. The proxy works but the account still gets limited. This one is not Android’s fault and not the app’s fault. It is the IP. If you connect through a flagged or heavily shared proxy IP, Telegram can still rate-limit, ask for re-verification, or shadowban the account regardless of how clean your setup is. If you suspect this, read how to tell if your Telegram is shadowbanned and, separately, why Telegram bans accounts. A proxy hides your IP; it does not launder a bad one.
how this looks on managed hosting
Everything above is the do-it-yourself path, and it is a legitimate one. I run plenty of accounts on phones with a hand-configured proxy. But there is a ceiling to what a phone-plus-proxy setup gives you, and it is worth naming honestly.
The IP is the whole game. A proxy you rent for a few dollars a month is almost always a datacenter IP or a residential IP shared across hundreds of users, and Telegram has seen those ranges abused for years. A real Singapore mobile IP, sitting on SingTel, M1, StarHub, or Vivifi, looks like an ordinary person’s phone because it is the same kind of address ordinary people use. That is why we built our infrastructure on dedicated SG hardware with actual carrier mobile IPs rather than a rack of cloud servers. The difference shows up in survival rate over months, not on day one. If you want the deep comparison, mobile IP vs residential IP for Telegram and the Singapore mobile IP advantage lay out exactly why the carrier matters.
The other thing managed hosting changes is where the account lives. On the DIY path your account lives on your handset, which means battery settings, OS updates, the phone overheating in your pocket, and Android’s device-limit behavior all become your problem. On our setup the account runs on a Samsung cloud-phone in the rack, on a stable mobile IP, online twenty-four hours a day, and you reach it from your own phone whenever you want. You bring your own number; we never sell numbers or accounts, and there is no bulk SMS or referral nonsense involved. It is hosting, the same way a server is hosting. If you run several accounts, the device-limit math gets ugly fast on a single handset, and that is covered in Telegram device limits and cloud-phone hosting. If you are juggling more than one account on one Android phone today, read the technical reality of multi-account Telegram on Android before you assume the built-in account switcher is enough.
Managed hosting is not for everyone. If you have one personal account and you just want a clean IP while traveling, the proxy setup in this guide is the right tool and you do not need us. If you are running accounts that matter, that you cannot afford to lose, on IPs that need to stay clean for the long haul, that is where hosting on dedicated mobile-IP hardware earns its cost. The same logic, by the way, applies to running a bot, which we cover in how to run a Telegram bot on a cloud phone.
For the network protocol itself, Telegram’s own documentation is worth a read if you want to understand what MTProto is doing under the hood: see telegram.org, and our own breakdown in what is an MTProto proxy, explained.
final word
The Android setup is genuinely simple: Settings, Data and Storage, Proxy Settings, add your MTProto or SOCKS5 server, or just tap a tg:// link. The two things that trip people up are battery optimization silently killing the connection and the IP quality being worse than they assumed. Fix the battery setting, verify the connection is not leaking, and understand what your proxy IP actually is before you trust it with an account that matters.
If you would rather skip the IP lottery and run your accounts on dedicated Singapore mobile-IP hardware with the account hosted on a cloud-phone instead of your handset, that is exactly what we do. Mention code TGYT and take a look at what we offer. Bring your own number, keep your IP clean, and stop debugging Doze at midnight. If you are on iPhone instead, the same logic applies and the steps are in connect Telegram through a proxy on iPhone.
Get new guides and videos first — join the Telegram channel.