2026年10月4日
If you've filled in a proxy in Telegram for Windows but it keeps spinning, shows connecting, or fails to connect, the proxy itself is usually not the problem. More often, the proxy type, parameters, or system environment don't match. Work through the steps below in order; each one can be checked on your own.
Don't just stare at Telegram. First use a browser or command line to confirm the proxy is alive: open System Settings → Network & Internet → Proxy and check whether the manual proxy address and port match what you entered in Telegram. Then visit an overseas website in your browser. If it loads, the proxy is working; if not, the problem is on the proxy side and has nothing to do with Telegram.
Note: Telegram for Windows only supports SOCKS5 and MTProto proxies, not HTTP/HTTPS proxies. If you have an HTTP proxy, you'll need to switch to SOCKS5 or MTProto before entering it. A wrong port or entering SOCKS5 as SOCKS4 will both show up as a persistent failure to connect.
In Telegram for Windows, open Settings → Advanced → Connection type, or check directly in the proxy list.
Go through each item: for SOCKS5, enter the host as an IP or domain and the port as a number. Only fill in username and password if your proxy provider requires them; an extra space will cause failure. For MTProto, you need the full server, port, and secret; a missing character in the secret will also prevent connection.
After making changes, click Save and re-enable that proxy. Don't just close the window. If there are multiple proxies in the list, make sure the one currently enabled is the one you just configured, not an old dead node.
If the proxy parameters are correct but it still won't connect, the usual cause is interference from your local environment.
First, having both the system proxy and the in-app proxy enabled at the same time routes traffic through two layers. Turn off the system manual proxy and leave only the in-app proxy, or vice versa. Second, a firewall or security software may be blocking the Telegram process. In Windows Firewall's Allow an app through firewall, make sure Telegram is checked for both Private and Public networks. Third, a company or campus network may block the proxy port. Try a different port or a different network, such as a phone hotspot. Fourth, a large system time offset can cause the MTProto handshake to fail. Turn on Windows time sync.
If everything above is fine, the problem is likely the proxy node itself. Enter a different working node of the same type, confirm it connects, then switch back to the original node to compare. That tells you whether the node is dead or the configuration is wrong.
When testing, don't repeatedly click reconnect. Fully exit Telegram first, including the tray icon in the bottom-right corner, then start it again. If it still fails, temporarily test with Telegram's official connection method: the desktop version downloaded from telegram.org connects directly by default. If direct connection works, your account and client are fine, and the issue is in the proxy chain. When you need an installer, rely on telegram.org, Google Play, or the App Store. The entry provided on this site is not an official Telegram download.
Finally, a reminder: proxy addresses, ports, and secrets are sensitive information. Don't send them to others or paste them on public pages.