Confirm the symptom first
A TLS handshake timeout usually means the connection did not finish establishing securely in time. Test the same action once without and once with your trusted proxy to separate routing from account permission errors.
- Record the exact time and error text.
- Do not disable certificate verification.
Save the global proxy
Open App Settings → Global Proxy, enter an address such as http://127.0.0.1:7897 or socks5://127.0.0.1:1080, then choose Save & Enable. The client applies it to external API, account-check and update requests.
- Use the local port shown by your proxy application.
- HTTP and SOCKS addresses must include their scheme.
Use per-account nodes only when needed
The Global Proxy is the client-wide route. Proxy IP nodes under account management are for account-specific region and operational traffic. Test both layers separately when an account has its own node.
- Leave the global field empty to follow the system proxy.
- Avoid stacking unverified proxies because it makes failures harder to identify.
FAQ
Frequently asked questions
Start here for common questions about purchasing, access and system requirements.
Why does TUN mode work while normal proxy mode fails?
TUN captures application traffic at the network layer. A normal system proxy may not be inherited by every desktop process, so setting the proxy explicitly in TKLive provides a stable route.
What should I do if the proxy is enabled but requests still time out?
Verify the local proxy port, protocol and node connectivity, then restart the failed action. If other sites also fail through that node, replace the node rather than changing account credentials.
Content reviewed: October 7, 2026 · TKLive product team