Telegram Proxy Link Generator (MTProto / SOCKS5)

Constant spinning usually means the connection has not been established, so troubleshoot in order: 1) switch networks first - toggle between WiFi and 4G/5G, or turn on airplane mode for a few minutes then reconnect. 2) If your location blocks Telegram, set up a SOCKS5 or official MTProto proxy under built-in Use Proxy (it only routes Telegram traffic, so a working browser does not equal Telegram connecting). 3) On desktop the most common cause is an unaligned port: set the Telegram proxy to SOCKS5, the server to 127.0.0.1, and the port to the actual local port of your VPN client (Clash is commonly 7890, the v2rayN SOCKS5 port is commonly 10808). 4) Always restart Telegram after setting up a proxy, and when logged in but stuck, restarting the app or device often restores it.

Not necessarily; it depends on your region. Hong Kong, Taiwan, Singapore, Malaysia, the Philippines, Cambodia and most regions allow a direct connection, and failures are often just local network issues (try switching WiFi/4G or toggling airplane mode), so a VPN is not always required. But in regions that block Telegram at the network layer, such as mainland China (carrier block) and Vietnam (where authorities ordered telecom operators to block it in May 2025), you usually do need a VPN, or a SOCKS5 or official MTProto proxy under Telegram built-in Use Proxy. Judge by region first: if a direct connection works, skip the VPN; if it fails, add a proxy or turn on a VPN, based on local testing.

Essentially no. Mainland carriers block Telegram at the network layer, so a direct connection without a VPN usually fails, and registration, login and messaging all get stuck on Connecting. On top of that, mainland +86 numbers get their international verification SMS blocked by carriers and never arrive no matter how long you wait, so registration usually needs an overseas number or an SMS-code service. A workable approach: first turn on a VPN, or set up a SOCKS5 or official MTProto proxy under Telegram built-in Use Proxy (note it only routes Telegram traffic; on desktop, align the proxy port with your client local port, then restart after setup).

Telegram has no built-in acceleration to bypass blocks, but it does have an official Use Proxy feature supporting two protocols, SOCKS5 and official MTProto. This is not an accelerator; it routes Telegram own traffic through a proxy to get past blocks (it only routes Telegram, not other apps). Whether you need it: Hong Kong, Taiwan and most of Southeast Asia can connect directly with neither a VPN nor a proxy; blocked regions like mainland China and Vietnam need a VPN, or a SOCKS5 or MTProto node under built-in Use Proxy. Note the official app does not provide specific proxy nodes, so node sourcing and safety are on you. Connect directly if you can; add a proxy only if it fails.

Solve it in this order: 1) switch networks first - toggle between WiFi and 4G/5G, or turn on airplane mode for a few minutes then reconnect. 2) On desktop or Mac the most common root cause of Connecting is an unaligned port: go to Settings > Advanced > Connection type / Proxy, set the proxy to SOCKS5, the server to 127.0.0.1, and the port to the actual local port of your VPN client (Clash is commonly 7890, the v2rayN SOCKS5 port is commonly 10808, based on the software). 3) Always restart Telegram after setting up a proxy; if you are logged in but stuck and cannot message, restarting the app or device often restores it. 4) Confirm the built-in proxy only routes Telegram, so a working browser does not mean it can connect.

First, to be clear: the official Telegram app neither provides nor endorses specific proxy nodes, and built-in Use Proxy is just a tool with no free IP list attached. Free MTProto/SOCKS5 nodes out there are mostly distributed by third parties in channels (often given as tg://proxy?server=...&port=...&secret=... or t.me/proxy links; one tap imports and enables them, and a secret starting with dd means fake-TLS disguise is on). But free public nodes are unstable and their safety is on you, as they may be abused or log traffic. A safer choice is to set up MTProxy yourself (the official open-source project on GitHub) or use a reliable VPN client together with built-in SOCKS5.

Telegram built-in Use Proxy is an official feature, and on Android the path is Settings > Data and Storage > Proxy > Add proxy. It supports two protocols: SOCKS5 and official MTProto. The easiest is to tap a t.me/proxy one-tap link someone shared to import MTProto, and when the status shows Connected it has succeeded. If you already have a VPN tool running on your machine: choose SOCKS5, set the server to 127.0.0.1, and set the port to the client actual local port (Clash is commonly 7890). Note the built-in proxy only routes Telegram own traffic and does not affect other apps, and it is best to restart Telegram once after setup. Node stability and safety are on you.

Two paths: one is to turn on a full-device VPN at the phone level to route all traffic, in which case you usually do not need to set a separate proxy inside Telegram; the other is to use the Telegram built-in proxy, with the path Settings > Data and Storage > Proxy, where you can enter SOCKS5 (server 127.0.0.1, port the actual port of your machine client) or just tap a t.me/proxy one-tap link to import the official MTProto. Note the built-in proxy only routes Telegram through the proxy and does not affect other apps, so a working browser does not mean Telegram can connect. After setting up the proxy, it is best to restart Telegram once and then check whether it shows Connected.

It helps; switching networks is the first troubleshooting step. The community-accepted order is: switch networks first (move to 4G/5G mobile data or a different WiFi) > then check the proxy settings (whether SOCKS5 has 127.0.0.1 plus the correct local port) > restart Telegram or the device after setup. Distinguish two cases: if everything fails to connect and you cannot message, it is usually a network or proxy problem; if text messages are fine and only images and videos keep spinning, that is not a connection issue but a download issue, and blindly switching proxy nodes often helps little. Clear the network and proxy hurdles first.

Check in this order: 1) is the port right - on desktop the most common issue is the VPN client local port not matching the port filled in Telegram, so confirm SOCKS5, 127.0.0.1, and a port matching what the client actually listens on (Clash commonly 7890, v2rayN 10808). 2) Do not pick the wrong protocol; the built-in box accepts only SOCKS5, not HTTP. 3) Always restart Telegram after setup; when not logged in, setting a proxy requires a restart to take effect, and when logged in but stuck on Connecting, restart Telegram or the whole device. 4) Switch routes: change networks (move to 4G/5G), or try a different MTProto one-tap link. 5) Still failing, confirm your VPN tool itself is working (the local client should connect to its node first).

For Telegram downloads, first distinguish: if text messages send and receive fine and only images, videos or files download slowly or keep spinning, that is usually not a connection issue but a download-side bottleneck, and frequently switching proxy nodes helps little. Practical fixes: go to Data and Storage, switch automatic media download to manual, set auto-download video quality to standard or low, clear the cache regularly to free device space, and switch to WiFi when the network is poor. Also do not believe that changing the data center (DC) speeds things up; your account DC is set by your registration phone number and cannot be changed after registering, so that is a myth. The real fix is in the download settings and proxy link quality, not changing the DC.

The sources do not record any nationwide Telegram block in Singapore, so under normal conditions a local network allows a direct connection with no proxy needed. If you hit slow loading, it is usually not throttling but a media download issue: text is fine and only images and videos spin, usually due to the download queue or cache. In Data and Storage, switch automatic media download to manual, clear the cache regularly, lower the auto-download video quality, and switch to WiFi when the network is poor. Whether there is actual throttling depends on local carrier testing, so verify in practice.

The sources do not record a nationwide block in Myanmar, but as long as you genuinely cannot connect locally, the Telegram built-in proxy is designed precisely to counter blocking and connects in most cases. How to use it: go to Telegram Settings > Data and Storage > Proxy, choose SOCKS5 and enter 127.0.0.1 plus the local port of your VPN client; or tap an official MTProto one-tap link someone shared (tg://proxy / t.me/proxy) to import it, and when the MTProto secret starts with dd it disguises traffic as ordinary HTTPS to better resist detection. Restart Telegram after setup, and Connected means success. The specific block situation needs to be verified in practice.

Free public proxy nodes are inherently unstable, and third-party MTProto nodes commonly stop working. To switch: get a new proxy one-tap link (tg://proxy or t.me/proxy) and tap it inside Telegram to import and enable it, and Connected means success. You can also go to Settings > Data > Proxy to delete the old one and add a new SOCKS5. Reminder: node stability and safety are on you; and if your problem is connects but loads slowly, blindly switching nodes helps little, and in that case what you should address is media download and cache.

It is usually not a Telegram problem itself but that these two network environments differ: the mobile data network may have its traffic treated as international and blocked by the carrier, or your proxy only works on WiFi. First try: turn on airplane mode for a few minutes then off, and switch to 4G/5G mobile data to reconnect; if you reach Telegram via a VPN tool or proxy, confirm it also works on mobile data and check that the proxy port in Telegram is aligned. Remember to restart Telegram after setting up the proxy.

Fix it in this order: switch networks first (toggle WiFi and mobile data, switch 4G/5G, or turn on airplane mode for a few minutes then reconnect); then check the proxy - the Telegram built-in proxy only routes Telegram traffic, so confirm SOCKS5 has 127.0.0.1 plus the client actual local port, since an unaligned port is the most common root cause of Connecting, and always restart Telegram after changing it; if your location has a block (such as Vietnam), set up an MTProto one-tap link. When stuck on the login screen, restarting the app or device often restores it.

In most cases it is not a network or proxy problem. The number-one truth is: if you recently logged in on another device, the login code is delivered as an in-app Telegram push rather than by SMS, so look for the code in the already-logged-in Telegram session on your computer or tablet. Other common causes: the iOS spam-SMS filter or the carrier treating the international verification SMS as spam (toggle airplane mode then reconnect, or switch 4G/5G to fix); a wrong number format (use international format and drop the leading 0); or a mainland +86 number being technically blocked by carriers so it almost never arrives. You can also tap Did not receive the code to switch to voice-call verification.

Generally keep the default and do not turn it on specially. Whether the Telegram proxy works depends on choosing the right protocol (SOCKS5 or official MTProto) and entering the right server and port, not on the IPv6 switch. Unless your network is pure IPv6, or the proxy node explicitly requires IPv6, turning it on may instead cause connection failures because the local network does not support IPv6. Recommendation: first set up SOCKS5 = 127.0.0.1 plus the client actual local port by default (without specially turning on IPv6), and once connected leave it alone; if it will not connect, go back and troubleshoot item by item, where IPv6 is usually not the main cause. Verify in practice.

This is common, and the reason is that the Telegram built-in proxy only routes its own message traffic, while voice and video calls go over a separate peer-to-peer (real-time audio/video) link that does not necessarily follow the proxy, so text and messages are all fine while only calls fail to connect. Real fixes to try: switch to routing the whole device or specific apps (such as a system-level VPN or Clash global or rule mode) so call traffic also goes through the proxy, rather than only setting SOCKS5 inside Telegram; also confirm both sides networks are smooth. Verify in practice.

It depends on how your client routes traffic. If the provider client (such as Clash) is in global mode or a rule mode that includes Telegram, it already proxies the whole device or Telegram traffic, so you do not need to set a separate proxy in Telegram and can just use it. Conversely, if you only want Telegram to go through the proxy while other apps do not, or the client does not route Telegram, then set SOCKS5 = 127.0.0.1 plus the client local port in Telegram (Clash commonly 7890). Simple rule of thumb: if Telegram sends and receives fine, do not fiddle with it; if it stays on Connecting, go back and set up the proxy with an aligned port and restart.