This article explains how to import a subscription into Clash and why you might still be unable to open websites afterward. Follow these steps in order: get the link, add the configuration, select a node, then check your IP, DNS, and browser settings. Menu names vary slightly across Clash-based clients; common options include “配置,” “Profiles,” and “订阅.” Use the labels shown in your client.
1. Before importing: check the client and subscription format
Install a trustworthy, actively maintained Clash-compatible client, preferably by downloading it from the project’s official release channel. If prompted for network permissions on first launch, grant them as needed. Don’t assume screenshots of an older client show how every version works.
Get the Clash-compatible subscription link provided by your service provider. It is usually an HTTPS URL, not a single vless:// or vmess:// node-sharing link. If the format is reported as unsupported, first check whether the provider offers a dedicated Clash link. Don’t submit a private subscription to an unfamiliar conversion website.
2. How to import a subscription into Clash
- Open the client and go to the “配置 / Profiles” page. Look for “New,” “Add,” or “Import from URL.”
- Paste the complete subscription link. Check that it contains no leading or trailing spaces, line breaks, or Chinese punctuation, then enter a recognizable name.
- Click “Download” or “Import” and wait for the configuration to appear in the list. If the download fails, first check whether the link has expired and whether your current network can reach the subscription URL.
- Click the imported configuration to make it the active one. Downloading it successfully without enabling it usually won’t switch you to the new nodes.
- Go to “代理 / Proxies,” select a node in the proxy group you actually use, and run a latency test. Treat the result as a guide and verify the connection by opening a website.
- Return to the main screen and enable System Proxy. For everyday use, start with “Rule” mode, then visit your target website to confirm it can connect.
If you have a YAML configuration file, use “Import from file.” You can usually update a subscription from the configuration page by clicking “Update.” Locally imported files may not support online updates. Before using free nodes from this site, check their sharing format; not every node link is a subscription.
3. After importing: how do IP, DNS, and your browser interact?
Successfully importing a subscription does not mean your browser traffic is going through the proxy. The subscription provides nodes and rules; the system proxy affects apps that support it; and your exit IP depends on which node your requests actually use. In Rule mode, some websites connect directly, so seeing your local IP doesn’t necessarily mean the configuration has failed. Check the client’s connection logs as well.
DNS resolves domain names to IP addresses. If the logs repeatedly show resolution failures, check the client’s DNS settings and your current network rather than simply switching nodes. Your browser’s “Secure DNS” feature may use a separate resolution path. Temporarily turn it off while troubleshooting, then decide whether to turn it back on once you’ve identified the cause.
A browser proxy extension may override the system proxy. Disable any conflicting extensions, fully quit the browser, and reopen it. If only one website is affected, try an incognito window to rule out cache or login-state issues. A changed IP does not mean your browser environment is anonymous; cookies, accounts, and site permissions may still be linked to your identity.
4. Troubleshoot connection failures step by step
First, check whether the subscription updates. Then confirm that the configuration is enabled, the proxy group has a working node selected, and the system proxy is on. If every latency test fails, check your device’s clock, network status, and subscription validity. If the tests succeed but websites still won’t load, check the connection logs for DNS errors, direct connections caused by rules, or connection timeouts. Avoid changing several settings at once; change one thing at a time and test again to help pinpoint the issue.