This article explains how to “import a subscription into Clash” and why, after importing, you still may not be able to open websites, your IP does not change, DNS leaks occur, or the browser environment appears abnormal. It is suitable for ordinary users who have just obtained a subscription link, a free node link, or an airport subscription. Just follow the steps to complete the setup and troubleshooting.
1. What to prepare before importing a subscription
Clash itself is only a client and cannot connect to the network out of thin air. You need a working subscription address. A subscription is usually an https link containing multiple node configurations. This site also collects some free node resources, which are suitable for temporary testing, but stability will depend on line conditions.
- Make sure Clash Verge, Clash for Windows, or another Clash-core client is already installed.
- Copy the full subscription link, and do not leave out the opening https://.
- Turn off other proxy software on the system to avoid port conflicts.
- Make sure your local network can access ordinary websites normally.
2. Specific steps to import a subscription into Clash
- Open the Clash client and go to the “Profiles / Configuration / Subscription” page.
- Click “New Profile,” “Import from URL,” or “Import from Link.”
- Paste the subscription address. For the name, you can enter “freevpn-x test” or any custom name.
- Click download, save, or update, and wait for the configuration file to finish loading.
- Go back to the proxy page, select a node, then switch to “Rule” mode or “Global” mode for testing.
If it says the download failed, first check whether the subscription link has expired and whether it was copied in full. If it reports a YAML error, the subscription content format is usually incompatible, and it is recommended to switch to a subscription specifically for Clash.
3. How IP, DNS, and browser environment relate after import
Many people think importing a subscription means they have successfully bypassed restrictions, but in fact you still need to check three things: proxy mode, system proxy, and DNS resolution. After Clash connects to a node, only traffic that actually goes through the proxy will show the node’s IP. If the browser is not using the system proxy, the IP will still be that of your local ISP.
It is recommended to first enable “System Proxy / 系统代理” on the Clash home page, then use a browser to visit an IP-check website to confirm whether the exit IP has changed. If you are using Rule mode, domestic websites may still go through a direct connection, which is normal. If you want everything to go through the node, you can temporarily switch to Global mode for testing.
As for DNS, if you can connect but some websites still will not open, the cause may be DNS pollution or abnormal resolution. You can enable DNS in the client settings or use the client’s default configuration. Beginners are not advised to change complex parameters casually. The browser may also have its own secure DNS enabled, causing behavior inconsistent with the system. You can temporarily turn off “Use secure DNS” in Chrome or Edge settings and test again.
4. Common troubleshooting checklist
- Subscription update failed: switch networks and try again, check whether the link is invalid, and make sure there are no extra spaces.
- Node shows timeout: switch to another node or try again later; fluctuations are common with free nodes.
- Browser cannot open sites but Telegram works: check the browser proxy, DNS, and secure DNS settings.
- IP did not change: enable the system proxy and make sure the browser is not using another proxy extension.
- Only some websites work: switch between Rule and Global modes for comparison to determine whether the issue is with the rules or the node.
Summary: the core of importing a subscription into Clash is “a correct subscription link, successful configuration download, a connectable node, and traffic that is actually going through the proxy.” When problems occur, do not keep reinstalling the client repeatedly. First troubleshoot step by step by checking the IP, DNS, and browser environment, and you can usually identify the cause quickly.