This article explains how to import a subscription into Clash and troubleshoot common issues after importing, such as no internet access, websites not loading, an unchanged IP address, and DNS leaks. It’s intended for everyday users who have just received a Clash subscription link, a free node subscription, or a VPN provider subscription. Follow the steps below to import it and perform basic troubleshooting.
1. Check these things before importing a subscription
A Clash subscription is usually a link starting with http or https that contains multiple nodes and rule configurations. Before importing it, make sure the link has no extra spaces, hasn’t expired, and opens in your browser or returns configuration content. If you’re using free nodes provided by this site, be sure to copy the “subscription link” rather than the text for an individual node.
- On Windows, commonly used clients include Clash Verge, the older Clash for Windows, and compatible clients.
- On macOS, you can use Clash Verge, ClashX Meta, and similar clients.
- On Android, you can use Clash Meta for Android.
- On iOS, you’ll typically need a third-party client that supports Clash subscriptions. Check the client’s documentation for details.
2. Standard steps for importing a subscription into Clash
- Open your Clash client and go to the Profiles, Configuration, Subscription, or Configurations page.
- Click a button such as New, Import, Download from URL, or Add Subscription.
- Paste in the subscription link. You can enter “freevpn-x” or a name of your choice.
- Click Download, Update, Save, or OK, then wait for the client to fetch the configuration.
- Return to the Proxies page and select a node or an automatic latency test group.
- Enable System Proxy. If TUN Mode is available, enable it if needed.
- Open a browser and visit a test site to check whether you can access the internet.
If the subscription imports successfully but the node list is empty, the problem is usually not the client. The subscription link may have expired, your network may be unable to access the subscription URL, or the client may not support that configuration format. Try switching networks or copying the subscription link again.
3. How subscriptions, IP addresses, DNS, and browser settings are related
Many users assume that importing a subscription automatically changes their IP address, but the client also needs to route your traffic correctly. A subscription only provides nodes and rules. Your internet exit point is determined by the node you select, the proxy mode, and whether the system proxy is enabled. If your browser is still connecting directly, the IP address you see may still be that of your local internet provider.
DNS matters, too. DNS translates domain names into IP addresses. If DNS traffic still goes through your local network, you may encounter issues such as websites not loading, DNS pollution, or incorrect location detection. In general, it’s best to use the client’s default DNS settings and avoid running multiple proxy apps at the same time, as this can cause rule conflicts.
Browser settings include cache, cookies, WebRTC, language, and time zone. Even when the proxy is working, some websites may still detect your location based on old cookies or your browser fingerprint. To troubleshoot, try an incognito window or clear the cache for the website in question. If you’re concerned that WebRTC could expose information about your local network, disable the relevant feature in your browser’s extensions or settings.
4. Quick checklist for connection issues
- Subscription won’t update: Check that the link is complete. Try opening it in a browser or switching networks and trying again.
- Node times out: Try another node, update the subscription, and check that your device’s time is correct.
- Some websites load, but others don’t: Switch to Global mode to test. If it works, switch back to Rule mode.
- IP address hasn’t changed: Make sure System Proxy is enabled and that your browser isn’t configured to bypass the proxy.
- DNS issues: Close any other VPNs, accelerators, or proxy apps, leaving only one Clash client running.
Finally, after importing a subscription, first check that it updates successfully, then test the node latency, and finally test access in your browser. If you run into problems, don’t rush to reinstall the client. Start by checking the subscription link, proxy settings, selected node, DNS, and browser cache. These checks are usually enough to identify the cause.