This article explains how to import a subscription into Clash and why, after importing, you may still run into issues like webpages not opening, your IP not changing, DNS leaks, or abnormal browser behavior. It is suitable for ordinary users using Clash, Clash Verge, or Clash for Windows clients for the first time. Just follow the steps to complete the subscription import and basic troubleshooting.
1. What to prepare before importing a subscription
Clash does not use a single node link, but a “subscription URL.” Subscription URLs are usually provided by proxy services, node providers, or this site’s free node page, and the client pulls the configuration file through this URL. First, make sure what you have is a subscription link starting with http or https, not a webpage address, QR code screenshot, or a single vmess/vless link.
- A Clash-based client is already installed, such as Clash Verge Rev or Clash Meta GUI.
- The subscription link can be copied correctly, with no spaces before or after it.
- Your system time is correct; otherwise, certificate or subscription update failures may occur.
2. General steps to import a subscription into Clash
- Open the Clash client and find the “Profiles / Configuration / Subscription” page.
- Click “New / Add / Import from URL”.
- Paste the subscription URL into it. For the name, you can enter “freevpn” or any custom name.
- Click download, save, or update, and wait for the configuration to finish loading.
- Go to the “Proxies / Proxy” page and select a node or policy group.
- Return to the home page and enable the system proxy. If necessary, also enable TUN mode.
If you do not see any nodes after importing, first click to update the subscription. If it is still empty, the subscription URL may be unavailable, the format may be incompatible, or your network may be unable to access the subscription source. It is also recommended to update the free nodes provided by this site regularly, because the availability of free resources can change.
3. How subscriptions relate to IP, DNS, and the browser environment
A subscription only tells Clash which nodes and rules are available; it does not automatically change the network path for all software. What actually affects access results are node selection, proxy mode, DNS settings, and the browser environment.
IP: Only after enabling the system proxy and selecting an available node will a browser show the proxy exit IP when visiting detection websites. If it still shows your local IP, the usual reasons are that the system proxy is not enabled, the browser is using a direct connection, or certain applications are bypassing the proxy.
DNS: DNS is responsible for resolving domain names into IP addresses. If DNS does not go through the proxy, you may find that webpages will not open, region detection is abnormal, or DNS leaks occur. Ordinary users can give priority to the client’s default DNS settings; if problems arise, then try enabling enhanced mode, Fake-IP, or switching to global mode for testing.
Browser environment: Browser cache, extensions, WebRTC, account region, and cookies can all affect how websites identify you. After switching nodes, it is recommended to open a new incognito window for testing. If detection is still abnormal, clear the site data or disable browser plugins that modify proxy settings.
4. Quick troubleshooting for connection failures
- Subscription download failed: Check whether the link is complete, try switching networks, or copy it into a browser to test whether it can be opened.
- All nodes are red: First update the subscription, then switch to other nodes. Free node failures are a common situation.
- It connects but webpages will not open: Switch the rule mode to global for testing and confirm whether rule-based routing is the cause.
- IP did not change: Make sure the system proxy is enabled and that the browser is not using its own separate proxy settings.
- Some websites behave abnormally: Clear cookies, switch to an incognito window, and disable options or plugins related to WebRTC leaks.
Summary: The core of importing a subscription into Clash is to “add the subscription URL, update the configuration, select a node, and enable the proxy.” If the import succeeds but the browsing result is still wrong, do not focus only on the subscription itself; you should also check the IP, DNS, and browser environment. Troubleshoot in the order above, and you can usually identify most problems.