If ChatGPT will not load through Clash, the cause may be a bad node, incorrect rules, DNS interference, or the wrong proxy mode. This guide walks through quick tests and safe fixes for Clash Verge Rev and Mihomo before you replace your subscription or change system settings.
If ChatGPT will not load through Clash, the cause may be a bad node, incorrect rules, DNS interference, or the wrong proxy mode. This guide walks through quick tests and safe fixes for Clash Verge Rev and Mihomo before you replace your subscription or change system settings.
When ChatGPT refuses to load while Clash is running, the visible symptom is often just a timeout, a blank page, or an endless loading spinner. Those symptoms do not point to one single cause. A proxy node can be offline, a rule may send ChatGPT directly instead of through the proxy, DNS may return an unusable address, or the browser may be using a different network path from the one you are testing in Clash.
The first useful distinction is whether the problem affects only ChatGPT or affects every destination that should use the proxy. Open another overseas website that normally requires the same proxy path. If several unrelated sites fail, start with the node, the proxy mode, and the local port. If ordinary proxy traffic works but ChatGPT alone fails, inspect domain rules, DNS behavior, and the selected proxy group first.
Also separate a page-loading problem from an account or browser problem. A page that opens but repeatedly logs out, refuses a challenge, or shows an application error is not necessarily suffering from a TCP timeout. Test the same account in a private browser window, and if possible test a second browser. Do not immediately delete cookies, reset the entire profile, or replace the subscription. Those actions can remove useful evidence without repairing the route that is actually broken.
| Observed symptom | Most likely area | First check |
|---|---|---|
| All proxied websites time out | Node, local port, or client mode | Test another node and confirm the system proxy port |
| Only ChatGPT fails | Rules, DNS, or a destination-specific route | Inspect matching rules for ChatGPT domains |
| The page opens but the app keeps loading | WebSocket, browser cache, or unstable route | Try a private window and a stable node |
| ChatGPT works in the browser but not in an app | Different proxy support or DNS path | Check whether that application honors the system proxy |
| It works briefly, then stops | Node overload, connection reuse, or subscription policy | Compare two nodes and review the Clash log |
A working Clash interface does not guarantee that the selected proxy is usable. The core can be running normally while the chosen node is overloaded, expired, blocked, or unable to reach the destination. In Clash Verge Rev, open the proxies or groups view and select a node that has recently passed a latency test. A low latency result is not a complete quality measurement, but a node that consistently times out is a poor candidate for troubleshooting.
Test at least two or three nodes from different regions or server entries. If one node fails while the others load ChatGPT, the problem is probably node-side and the safest fix is simply to select a healthy node. If every node fails in the same way, continue with the client and rule checks instead of repeatedly clicking random entries. Repeated tests can also consume provider resources or make a congested service look even less stable.
Next, verify the current operating mode. Rule mode is normally the best starting point because it sends traffic according to the configuration's rules. Global mode sends nearly all supported traffic through the selected proxy and is useful as a diagnostic control. If ChatGPT works in Global mode but not in Rule mode, the node is probably fine and a rule or rule-provider decision needs attention.
Direct mode intentionally bypasses the proxy. It is useful for confirming that the local internet connection works, but it cannot prove that the proxy route is healthy. On some clients, the mode switch is separate from the system-proxy toggle. Make sure the client is both running and exposing the expected local proxy port. A browser configured for 127.0.0.1:7890 will fail if the current mixed port is actually 7897, even when Clash itself is fully operational.
For a quick isolation test, use this order:
In Rule mode, Clash does not decide based on the page title shown in the browser. It evaluates hostnames and other rule conditions. ChatGPT is not limited to one hostname: the main web application, authentication flow, API requests, static resources, and real-time connections may use several related domains. A rule that covers only one visible address can therefore leave another required request on the direct route.
Inspect the Clash log while opening ChatGPT. In Clash Verge Rev, the log view usually shows the requested host and the rule or policy that selected it. Look for entries containing domains such as chatgpt.com, openai.com, and their related service hosts. The exact set can change as the service evolves, so avoid copying a random, outdated list from an unrelated configuration. The important question is whether the relevant requests are being sent to a proxy group rather than DIRECT or a rejecting policy.
A broad temporary rule can help confirm the diagnosis, but it should be used carefully. For example, a provider's configuration may support a domain suffix rule similar to this:
rules:
- DOMAIN-SUFFIX,chatgpt.com,ChatGPT
- DOMAIN-SUFFIX,openai.com,ChatGPT
- MATCH,PROXYThe group name ChatGPT must already exist in the configuration. If it does not, replace it with the actual proxy group name used by your profile. Do not paste this snippet blindly at the bottom of a large rule list. Clash evaluates rules from top to bottom, so an earlier rule can match first and make the new entry ineffective. Place destination-specific rules before broad regional rules and before the final MATCH fallback.
For diagnosis, switching to Global mode is often safer than editing a remote subscription. If Global mode works, inspect the local override or use the profile editor's rule-provider settings. Many subscribed profiles are regenerated whenever they update, which means a manual edit to the downloaded YAML may disappear later. A local override, if supported by the client, is more durable. Keep the override narrow: route only the required domains through the selected group and leave unrelated traffic governed by the provider's existing rules.
ChatGPT may also use long-lived connections for interactive features. A page can load while messages fail if the route becomes unstable after the initial request. Watch for repeated connection errors or rapid reconnects in the log. In that situation, choose a more stable node and test again before adding increasingly broad domain rules. A routing rule cannot repair a node that drops persistent connections.
This is the practical middle-of-the-process test. The goal is to determine whether the browser and the Clash core are using the same path. Perform each step separately and note the result.
Open the client's dashboard and check that the Mihomo core is running without repeated startup errors. Confirm the mixed port or HTTP port shown in the client. If another application has occupied that port, the system proxy may point to a dead listener. A normal-looking tray icon is not enough; the log should show that the controller and proxy listeners started successfully.
Enable the system proxy in Clash Verge Rev, then open a private browser window. Private mode reduces interference from cached service workers and extensions, but it does not bypass the system proxy by itself. If the browser has a manual proxy extension or its own network setting, disable that temporary override so that only one proxy path is active.
Now test a normal proxied destination and ChatGPT. If the normal destination works but ChatGPT does not, return to the rules section. If both fail, test another node and verify the local port. If the browser works only when manually configured, the operating system proxy integration is not being applied to that browser or desktop session.
TUN mode captures traffic at the network interface level and can proxy applications that do not understand HTTP or SOCKS settings. It is useful when an application ignores the system proxy, but it also introduces more variables: routing, DNS handling, permissions, and conflicts with another VPN or network filter. Do not enable TUN merely because a browser page times out.
If ChatGPT works through the browser's normal system proxy but fails in a desktop application, check whether that application supports HTTP or SOCKS proxies. If it does not, TUN may be appropriate. Enable it temporarily, keep only one VPN-like service active, and verify that the TUN DNS and route settings are consistent with the profile. When the test is complete, disable TUN if you do not need system-wide capture. Two traffic interception layers can produce loops, duplicate DNS requests, or connections that appear to vanish.
DNS problems often look like proxy problems because the browser cannot establish a connection to the address it received. Mihomo configurations may use normal DNS, fake-IP mode, or redirection settings. The correct choice depends on the client and operating system, so avoid switching enhanced modes without a reason.
Look in the Clash log for DNS errors, failed lookups, or a hostname resolving to an obviously unusable address. If fake-IP mode is enabled, verify that the configuration's fake-IP range is not colliding with another local network or VPN route. If you recently enabled a third-party DNS application, browser secure DNS, or another VPN, temporarily disable that competing resolver and retest. The cleanest diagnostic result comes from one DNS controller, one proxy client, and one active VPN path.
The Mihomo log is more useful when read as a sequence rather than as a wall of red text. First find the hostname requested by the browser. Then check which rule matched it, which policy group received it, and whether the connection ended with a timeout, reset, DNS failure, or successful response. These details separate routing mistakes from node instability.
| Log clue | Likely meaning | Action |
|---|---|---|
Matched DIRECT | The request bypassed the proxy | Move or correct the ChatGPT domain rule |
| Connection timeout to one node | The selected node or route is unhealthy | Switch nodes and compare results |
| DNS lookup failed | The resolver path is unavailable or conflicting | Check DNS ownership and resolver reachability |
| Repeated connection resets | The route is unstable or the destination path is being interrupted | Try a different region or transport |
| Successful connection but page hangs | Browser state, persistent connection, or partial domain routing | Use a private window and inspect additional hosts |
Use the smallest fix that matches the evidence. A single bad node calls for a node change. A request matched to DIRECT calls for a rule correction. A port mismatch calls for aligning the browser and Clash settings. A DNS conflict calls for removing the competing resolver, not for adding ten more fallback servers. Large configuration changes make later maintenance harder and can break unrelated services.
After a successful test, return settings to their intended state. If Global mode was only used for diagnosis, switch back to Rule mode. If TUN was enabled temporarily, turn it off unless system-wide capture is required. Clear only the browser data relevant to the failed session, and allow the page to establish a fresh connection. Finally, test ChatGPT on a second node and at a later time so that a single transient recovery is not mistaken for a permanent fix.
Replacing a subscription should be the last major step, not the first reaction to one timeout. A subscription becomes a reasonable suspect when every node fails across multiple devices, the profile downloads correctly but all proxy connections time out, the provider reports an outage, or the account has expired or exceeded its traffic limit. Before replacing it, verify the same profile with a clean client state and compare at least two nodes.
If only ChatGPT fails while other destinations work, a new subscription may reproduce the same rule or DNS problem. If ChatGPT works through Global mode but not Rule mode, changing providers does not address the local rule order. If it works in a browser but not in one application, the application's proxy support is the more relevant issue. These comparisons prevent unnecessary profile changes and preserve a known-good baseline.
The reliable sequence is simple: choose a healthy node, confirm the local proxy port, test Global mode, inspect Rule mode logs, check DNS ownership, and only then investigate TUN or provider-side limits. Most ChatGPT timeouts with Clash can be narrowed down through that sequence without resetting the operating system network stack or rebuilding the entire configuration.