How to set up a SOCKS5 proxy in Telegram
In short: Telegram proxy settings take SOCKS5 with a username and password. On mobile open Settings, Data and Storage, Proxy Settings. On desktop open Settings, Advanced, Connection type. Add the host and port, then the login and password. Our proxies are ordinary ISP proxies, not MTProto, so switch the order to SOCKS5 first and expect nothing Telegram-specific.
Telegram has its own proxy screen, so it does not depend on the phone’s or computer’s system settings. It accepts SOCKS5 with a username and password, which suits a ProxyJam order set to that protocol.
What you are adding
Our proxies are general ISP proxies: static addresses for any client that can use HTTP or SOCKS5. They are not MTProto proxies and we make no promise about how Telegram behaves over them. Use them only as the Acceptable Use Policy allows; section 5 does not permit getting around regional or platform access limits.
Prepare the order
If the order is on HTTP, switch it. In your dashboard, use Change protocol to switch the order to SOCKS5, then copy the host, port, login and password from My Proxies again, because the port and the credentials to use are the ones the row shows after the change.
Mobile
- Open Settings, then Data and Storage, then Proxy Settings.
- Turn Use Proxy on and choose Add Proxy.
- Select SOCKS5.
- Enter the host as Server, the port, the Username and the Password.
- Save, then tap the proxy to select it.
Desktop
- Open Settings, then Advanced.
- Under Connection type, choose Use custom proxy.
- Choose Add proxy, select SOCKS5 and fill in host, port, login and password.
- Save.
The menus move a little between Telegram versions and platforms; look for the Proxy screen under data or connection settings if yours differs.
Check that it is used
Telegram marks the proxy you selected as connected, or shows an error if the connection failed. It does not show your public address. To confirm the exit address, set the same proxy in a browser and open What Is My IP. Our proxy checker shows it too: paste the proxy, pick SOCKS5, and no browser setting has to change.
If it does not connect
A proxy that stays on “connecting” usually has a protocol mismatch: the order is still on HTTP while Telegram is set to SOCKS5, or the other way round. Check the row, then see proxy not working.
