This article explains how to import a subscription into Clash and troubleshoot common issues such as websites not loading, your IP address staying the same, DNS leaks, or your browser still showing your local environment. 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 complete the setup.
1. What to prepare before importing a subscription
Clash is a proxy client and cannot connect to the internet on its own. You’ll first need a working subscription link, which usually begins with http or https. We also compile free node resources on this site. They’re suitable for temporary testing, but their reliability depends on node availability, so try several nodes after importing your subscription.
- Windows users can use Clash Verge Rev or an older alternative client such as Clash for Windows.
- macOS users can use Clash Verge Rev or a similar Clash client.
- Android users can use Clash Meta for Android.
- iOS users generally need a proxy tool that supports Clash subscription conversion or compatible subscriptions.
Note: Don’t share your subscription link publicly. If the link expires, returns a 403 error, or fails to download, contact the subscription provider to get a new one.
2. General steps for importing a subscription into Clash
- Open the Clash client and go to the “Profiles / Configuration / Subscriptions” page.
- Click “New / Add / Import from URL”.
- Paste the subscription link. You can enter a name such as “freevpn” or “Backup Nodes”.
- Click Download, Update, or Save, then wait for the configuration file to load.
- Return to the “Proxies” page and select a node or an automatic latency-testing group.
- Turn on “System Proxy”. If needed, enable “TUN Mode”.
- Visit a search engine or an IP lookup site to confirm that your public IP has changed.
If the subscription imports successfully but no nodes appear, the subscription may use an incompatible format or need to be converted to Clash format. Look for a link labeled “Clash subscription” first.
3. What IP, DNS, and browser environment affect
IP determines the network location that websites see. Once Clash connects, websites you visit in your browser should show the node’s exit IP. If you still see your local IP, the system proxy may be off, your browser may be connecting directly, or the current rules may set that website to DIRECT.
DNS translates domain names into IP addresses. Incorrect DNS settings can cause issues such as being connected to a node but unable to load websites, getting local results, or slow access to some sites. Most users can start with the client’s default DNS settings. If problems persist, try enabling TUN mode or switching to Fake-IP/enhanced mode to avoid interference from your local carrier’s DNS.
Browser environment includes cache, cookies, WebRTC, language, time zone, and extensions. Even after your IP changes, websites may recognize your previous environment based on old cookies or your browser fingerprint. For testing, use a private window or a clean browser.
4. Troubleshooting connection failures after importing a subscription
- Subscription won’t update: Check that the link is complete and that you copied the “raw subscription URL”. Make sure there are no spaces.
- All nodes show as unavailable: Update the subscription, then try a different network. Free nodes may be temporarily unavailable.
- Connected, but websites won’t load: Confirm that the system proxy is enabled and that no browser proxy extension is conflicting with it.
- IP hasn’t changed: Check whether the current mode is Rule. Temporarily switch to Global mode to test.
- DNS issues: Enable TUN mode, restart the client and browser, and clear the DNS cache if necessary.
Finally, we recommend keeping at least two subscription sources and clicking “Update subscription” regularly. For everyday use, choose nodes with low latency that can access your target websites. If you only need temporary access to the open internet, you can import the free nodes updated on this site, but keep in mind that availability can vary and don’t rely on a single node long term.