This guide explains how to import a subscription into Clash and troubleshoot common issues that may remain afterward, such as webpages not loading, your IP address not changing, DNS leaks, or unexpected browser behavior. It’s intended for everyday users who have just received a subscription or free-node link and want to start using Clash on Windows, macOS, or Android.
1. What to prepare before importing a subscription
Clash is a proxy client; the actual connection comes from the node configurations in your subscription. You’ll need a working subscription URL, usually starting with http or https. It may come from your VPN provider, be shared by your team, or be listed on a free-node page on this site. Don’t share your subscription link publicly or with strangers: it may contain credentials that grant access to your nodes.
- Make sure you’ve installed a Clash client, such as Clash Verge, Clash for Windows, or Clash Meta for Android.
- Check that the subscription URL is complete, with no spaces or line breaks, and hasn’t been cut off by a messaging app.
- If your system clock is incorrect, sync it first; otherwise, TLS connections may fail.
2. General steps for importing a subscription into Clash
- Open your Clash client and go to the “Profiles,” “Configuration,” “Subscriptions,” or “Config Files” page. The name varies slightly between clients.
- Click “New,” “Add Subscription,” “Import from URL,” or a similar button.
- Paste the subscription URL into the URL field. For the name, enter “freevpn” or another label you’ll recognize.
- Click Save, Download, or Update, then wait for the client to fetch the configuration file.
- Return to the proxy page and select a node. To test, start with “Rule” or “Global” mode.
- Enable the system proxy or VPN mode, then visit a site such as ipinfo.io or whatismyip to check whether your IP address has changed.
If the subscription imports successfully but the node list is empty, the problem usually isn’t with the steps you followed. The subscription may have expired, require you to log in, use an incompatible format, or be inaccessible from your current network.
3. How subscriptions, IPs, DNS, and browser settings are related
Importing a subscription is just the first step. Whether your connection works properly also depends on your IP address, DNS, and browser environment. Your IP address is the outgoing address websites see when you connect. DNS translates domain names into server addresses. Your browser environment includes information such as cache, cookies, WebRTC, language, and time zone.
For example, if Clash is connected to a US node but your browser still shows local content, the site may be using old cookies or your location permissions. If your IP has changed but DNS is still handled by your local ISP, you may encounter altered DNS results, unexpected redirects, or privacy leaks. We recommend enabling the built-in DNS in Clash settings or using the client’s default enhanced mode. If you’re unsure what a setting does, don’t change it at random.
4. Troubleshooting common connection problems
- Subscription update fails: Try opening the subscription URL in a browser to see whether it can download the content. If it can’t, switch networks or wait for the provider to restore access.
- A node is selectable, but webpages won’t load: Switch to another node and try Global mode to rule out a problem with rule-based routing.
- Your IP address hasn’t changed: Check that system proxy or TUN/VPN mode is enabled, and make sure your browser isn’t using a separate proxy extension.
- Some websites behave unexpectedly: Clear your browser cache and cookies, check for conflicts with WebRTC leak-prevention extensions, and test again in a new private window.
Finally, we recommend keeping 2–3 working configuration sources and updating your subscriptions regularly. Free nodes are suitable for temporary testing and learning, but their reliability depends on the route, number of users, and network conditions. If an import succeeds but the nodes remain unusable, try a different subscription or node before reinstalling the client.