This article explains how to import a subscription into Clash, enable it after import, and troubleshoot cases where the connection appears successful but webpages won’t load. It also describes how your exit IP, DNS, and browser settings can affect your experience. Menu names may vary between Clash-compatible clients, but the basic steps are the same: add a subscription, download the configuration, activate it, and enable the proxy.
1. Before importing: Check the client and subscription format
First, install a Clash-compatible client for your operating system that is still maintained. Prefer downloads from the project’s official release page, and avoid modified versions from unknown sources. Get the subscription URL from your service provider and confirm that it supports Clash or the configuration format required by your client.
A subscription link is not the same as a link for a single node. Content starting with vless://, vmess://, or ss:// is usually a share link for a single node and may not work in the subscription field. If your provider offers a “Clash subscription” option, copy the URL provided there. Don’t submit links containing tokens to unfamiliar online conversion sites.
2. How to import a subscription into Clash
- Open the client and go to “Config,” “Profiles,” or “Subscription Management.”
- Click “New,” “Add,” or “Import from URL,” then paste the full subscription URL. Remove any leading or trailing spaces, and make sure you haven’t left out any parameters after the question mark.
- Enter a recognizable name, then click “Download,” “Import,” or “Save” and wait for the configuration to finish loading.
- Select the new configuration from the list and set it as the active configuration. Simply downloading the file without activating it usually won’t switch you to the new subscription.
- Go to the “Proxies” page and select an available node or an auto-select group in the relevant policy group. “Rule” mode is a good place to start.
- Enable “System Proxy,” then test your connection in a browser. TUN mode is a separate way to route traffic; you don’t need to enable it just to browse ordinary webpages.
A successful import doesn’t mean the proxy is active: make sure the configuration is active, the policy group has an available node, and the system proxy is enabled. To refresh the nodes, select “Update Subscription” on the configuration page. If the update fails, keep the existing configuration rather than deleting it right away.
3. Troubleshooting import failures and webpages that won’t load
- Download failed: Check whether the subscription URL has expired, whether it was copied in full, and whether your current network can reach it. If your client supports updating through the proxy, try that when you have an existing working connection.
- Parsing error: The subscription format may be incompatible, or the URL may be returning a login or error page. Check the format with your provider; simply changing the file extension won’t help.
- All nodes time out: Check your local network and system clock. Update the subscription, then try a different node. A failed latency test may also be due to the test URL, so check whether webpages actually load as well.
- Other apps work, but the browser doesn’t: Check for browser proxy extensions that may override the system proxy. Then compare results in a private window or another browser.
4. How your IP, DNS, and browser environment are related
The exit IP a website sees depends on whether that request goes through the proxy or connects directly. In Rule mode, different websites may use different routes, so seeing your local IP doesn’t necessarily mean the proxy is completely inactive. Check the client’s connection log to see how a particular request was routed.
DNS resolves domain names to IP addresses. The browser’s Secure DNS, system DNS, and the client’s DNS settings can affect one another. If you encounter a domain resolution error, note your original settings and test them one at a time to make the cause easier to identify.
Changing your exit IP won’t automatically clear cookies or change your browser fingerprint. Your login status, site cache, and permission settings may still affect how a page behaves. Treat your subscription URL as sensitive information, too. If you share a screenshot for help, hide the full URL and any tokens.