This guide explains how to import a subscription into Clash, enable it, and troubleshoot why webpages still won’t open in your browser. Follow the steps below to add the subscription, select a node, and turn on the proxy. Then check your IP, DNS, and browser settings to determine whether the subscription has expired, the node is unavailable, or your local settings aren’t taking effect. Interfaces vary across Clash clients, so refer to the menus in your version.
1. Prepare the client and subscription link
Download and install the client from its official release channel, and make sure it supports Clash-format subscriptions. Common menus include “Configuration / Profiles,” “Proxy / Proxies,” and “Settings.” Don’t mistake a webpage introducing the service for a subscription URL: a subscription link usually retrieves a configuration directly, while an individual node link such as vless:// may not work in the subscription import field.
A subscription link may contain a personal access token, so don’t share it publicly. When copying it, make sure you don’t include spaces, line breaks, or punctuation added by a messaging app. If you’re using free nodes from this site, check the format and last-updated date shown on the relevant page first. Different formats can’t be used interchangeably.
2. Import and enable a Clash subscription
- Open the client and go to “Configuration / Profiles.” Look for “New,” “Import,” or “Download from URL.”
- Paste the full subscription link, enter a name you can recognize, and click Download or Save. If you have a local configuration file, choose “Import from file”—don’t paste its file path as if it were a URL.
- Once the download is complete, select the configuration to make it the active one. Importing a subscription doesn’t automatically enable the proxy.
- Go to “Proxy / Proxies” and choose a node in the active policy group. For first-time use, we recommend “Rule” mode; you usually don’t need to route all traffic through the proxy for everyday browsing.
- Turn on “System Proxy” in Settings, keep the client running, and then use your browser to visit the target website. For a basic webpage test, leave TUN disabled at first to reduce the number of variables.
- To refresh the subscription later, click “Update” on the configuration page. If the client supports scheduled updates, you can enable them as needed. If an update fails, keep the old configuration for now so you don’t delete something that still works.
3. After importing, what do IP, DNS, and browser settings do?
The subscription provides nodes and rules; your exit IP depends on which node actually handles the request. In Rule mode, domestic websites may connect directly, so seeing different exit IPs on different websites isn’t necessarily a problem. When testing, check whether the target website matches a proxy rule rather than relying on a single IP lookup page.
DNS resolves domain names to addresses. Focus on the client’s DNS settings if you see domain resolution errors or some websites won’t open. A browser’s “Secure DNS” feature may use a separate resolution path. You can temporarily turn it off and compare results, but that doesn’t mean you need to leave it off permanently.
Browser proxy extensions may override the system proxy. Incognito mode doesn’t automatically change your exit IP; it mainly isolates some browsing history and session data. Disable proxy extensions before testing the system proxy—this makes it easier to pinpoint the issue than changing several settings at once.
4. Troubleshoot connection failures in order
- Subscription download fails: Check that the link is complete and hasn’t expired, and confirm that your current network can reach the subscription URL.
- Configuration parsing fails: Make sure the subscription format is supported. Don’t import webpage content or another client’s configuration directly.
- Node times out: Update the subscription, try another node, and verify by visiting an actual webpage. Latency results are only a guide.
- All webpages are affected: Make sure the correct configuration is selected and the system proxy is on. Close any other proxy software and try again.
- Only one browser is affected: Check extensions, Secure DNS, and the cache, then compare results in another browser.
Change only one setting at a time while troubleshooting, and keep track of the results. If the problem persists, check the client logs for download, parsing, or connection errors. Before asking for help, redact your subscription token, node password, and other personal information.