Setting up a proxy in Telegram Desktop

Setting Up Proxies in Telegram Desktop

Introduction

Telegram Desktop supports SOCKS5 and MTProto proxies to bypass blocking. In countries where Telegram is blocked, proxies are the primary method of accessing the messenger.

Basic Configuration

Configuration in Telegram Desktop

1. Open Telegram Desktop
2. Settings → Advanced → Connection type
3. Click "Use custom proxy"
4. Select the type:
   • SOCKS5: address, port, username, password
   • MTProto: address, port, secret
5. Click "Save"

SOCKS5

Enter the SOCKS5 proxy details:
- Hostname: ip_address
- Port: port
- Username and Password (if any)

MTProto

MTProto proxies are specialized proxies for Telegram:
- Work only with Telegram (not for web browsing)
- Faster than SOCKS5 for Telegram traffic
- Secret — a hexadecimal string for authentication

Advanced Configuration

Environment Variables

Most tools support standard environment variables for proxies:
- HTTP_PROXY / http_proxy — proxy for HTTP requests
- HTTPS_PROXY / https_proxy — proxy for HTTPS requests
- NO_PROXY / no_proxy — list of exceptions (addresses that bypass the proxy)
- ALL_PROXY / all_proxy — proxy for all protocols

SSL and Self-Signed Certificates

Corporate proxies often use their own SSL certificates. To work through them, you need to:
1. Obtain the proxy's CA certificate from the administrator
2. Add it to the system certificate store
3. Or disable SSL verification (for testing only)

Authentication

Two main authentication methods are supported:

By username and password — standard HTTP Basic authentication. Credentials are sent with each request. URL format: http://user:pass@proxy_ip:port

By IP address (whitelist) — your IP is added to a whitelist. No need to send credentials.

Verification

After configuration, check:
1. Perform a test request through the proxy
2. Ensure that the IP has changed
3. Check the connection speed
4. Ensure there are no DNS leaks

Troubleshooting

Proxy Not Connecting

• Check the correctness of the address and port
• Make sure the firewall is not blocking the connection
• Check the proxy's availability from your network

SSL Errors

• For corporate proxies, add the CA certificate
• For testing, temporarily disable SSL verification
• Update SSL libraries to the latest version

Authentication Errors

• Check the username and password
• Ensure the correct format of credentials
• Try URL encoding special characters in the password

Best Practices

1. Use environment variables — for flexibility and security
2. Do not hardcode credentials — use environment variables or configuration files
3. Configure exceptions — do not proxy localhost and internal addresses
4. Document settings — in the project's README or team wiki
5. Test after changes — any configuration change requires verification

Conclusion

Proper proxy configuration ensures stable tool operation and connection security. Follow the recommendations in this guide and always verify functionality after setup.