This article explains “how to import a subscription into Clash” and how to troubleshoot common issues after importing, such as being unable to access websites, your IP not changing, DNS leaks, or pages not opening in your browser. The step-by-step instructions are suitable for new users of Clash, Clash Verge, Clash for Windows, and similar clients.
1. What to prepare before importing a subscription
A Clash subscription is usually a URL containing multiple proxy nodes and rule configurations. You can use a subscription you purchased or try one of the free subscriptions provided on this site for testing. Before importing, make sure the client is installed, the subscription link is complete, and your network can access the internet—or at least reach the subscription URL.
- Don’t paste your subscription link somewhere public, as this could expose it.
- When copying the link, make sure it doesn’t include extra spaces, line breaks, or Chinese punctuation.
- If the subscription URL won’t open, Clash won’t be able to update the configuration either.
2. General steps for importing a subscription into Clash
- Open your Clash client and look for “Profiles,” “Configuration,” “Subscriptions,” or “Config Files.”
- Click “New,” “Add,” “Import from URL,” or a similar button.
- Paste the subscription link. You can name it “freevpn” or “My Subscription.”
- Click Download, Save, or Update, then wait for the configuration file to load.
- Go to the “Proxies” page, select a node, and start with Rule or Global mode for testing.
- Enable the system proxy or enhanced mode, then open a browser and visit a test website.
If the client reports a YAML error, an empty configuration, or a download failure, the issue is usually not with the nodes themselves. The subscription link may have expired, the network may be blocking it, or the client version may be incompatible. Try a different subscription link or update the client before trying again.
3. Why hasn’t my IP changed after importing successfully?
Successfully importing a Clash subscription only means the node list has loaded; it doesn’t mean your traffic is going through a proxy. The first thing to check is whether the system proxy is enabled. In some clients, selecting a node without enabling the system proxy means your browser still connects directly, so the IP shown in a lookup won’t change.
Also, not all websites use the proxy in Rule mode. For example, domestic sites may connect directly, while overseas sites use a node. To quickly check whether a node is working, temporarily switch to Global mode and refresh your IP lookup page. Once confirmed, switch back to Rule mode to avoid routing all your traffic through the proxy.
4. How DNS and your browser environment can affect things
Many people assume that if Clash connects, everything is fine—but DNS settings can also affect access. A DNS issue may cause pages not to load, unexpected redirects, or a node to work on your phone but not your computer. We recommend enabling the built-in DNS in Clash or using the client’s default recommended settings. Avoid mixing several network tools.
Your browser environment can also lead to misleading results. Browser cache, proxy extensions, WebRTC, and old cookies may all reveal your original environment to a website. When troubleshooting, try these steps in order:
- Test again in a private browsing window.
- Temporarily disable browser proxy extensions.
- Clear the target website’s cookies, then log in again.
- Don’t run multiple VPNs, accelerators, or proxy applications at the same time.
5. Quick checklist for connection failures
If you’ve imported the subscription but can’t connect to a node, start by checking the error in the logs. A timeout usually means the node is unavailable or the network is blocking it. An authentication failure may mean the subscription has expired. A “host not found” error is usually related to DNS or the subscription URL. Try these steps in order: update the subscription, switch nodes, switch networks, restart Clash, and update the client.
Finally, keep in mind that the reliability of free nodes changes over time, so they’re best suited to temporary testing and learning how to configure the client. If you use Clash regularly, get into the habit of updating your subscription regularly, keeping backup nodes, and checking the logs when something goes wrong. This makes most import and connection issues easy to identify.