The browser works, but Telegram or Discord desktop still direct-connects or spins forever. Many IM clients use their own stack and ignore the system proxy—the same class of problem as AI CLIs (Tun & AI).
Pick one path: fill 127.0.0.1 + the Clash mixed port inside the IM, or enable Tun. Running system proxy and an in-app proxy together is a double hop that often shows “invalid proxy.” Prove the browser goes through Clash first.
Path A: in-app proxy
In Telegram/Discord network settings, choose SOCKS5 or HTTP, host 127.0.0.1, port = the Clash mixed port (often 7897—use yours). A swapped SOCKS/HTTP type or a stale port after you changed Clash both look like “bad proxy.” Save and reconnect. Disable Telegram’s MTProto or any built-in proxy while testing.
Telegram / Discord → Network / Connection settings
Proxy type: SOCKS5 (or HTTP)
Server: 127.0.0.1
Port: 7897 (your Clash mixed port, not the API port)
Username/Password: leave empty unless you set one
→ Save, then reconnect the app
Path B: Tun
No per-app field, or you don’t want to fill every client: service mode + Tun. Managed PCs that block local proxies or TAP adapters will break both paths—compare on a phone hotspot before you blame the app.
| Path A: in-app proxy | Path B: Tun | |
|---|---|---|
| Setup | One field per app | One system toggle |
| Best when | Few apps, you control settings | Many stubborn apps |
| Risk | App updates wipe the field | More traffic tunneled, higher RTT |
| Must avoid | System proxy ON at the same time | Another VPN stacked on top |
Login works but chat doesn’t; text works but voice doesn’t
Unstable nodes, UDP blocks, or rules sending IM domains DIRECT are common causes. Swap to a stable same-region node and check routing. Voice needs UDP more than text does—fix the node before reinstalling. Clock or DNS weirdness: DNS, fake-ip.
Mobile Telegram and hotspot A/B
The phone can use a LAN proxy (Allow LAN) or its own client. If everything fixes on a hotspot, the office or home Wi‑Fi is likely killing UDP or the proxy port.
Safety and done-when
Install from the download center. Test one app at a time. Success looks like: stable messaging, voice when you need it, the Connections page or Tun showing the traffic, and no double proxy. Ports: port conflicts.