This guide explains how to import a subscription into Clash and troubleshoot common issues afterward, such as no internet access, an unchanged IP address, DNS leaks, or websites still failing to load in your browser. It’s suitable for beginners who have just received a subscription URL, a free node link, or a subscription from a VPN provider. Follow the steps below to set things up and resolve common problems.
1. What to prepare before importing a subscription
Clash is a client. Subscription links typically contain nodes, rules, and proxy groups. First, install a Clash client for your system. Common options include Clash Verge for Windows, a replacement client for the older Clash for Windows, Clash Verge Rev for macOS, and Clash Meta for Android. On iOS, use a proxy tool that supports the Clash subscription format.
- Make sure the subscription link is a complete URL, usually starting with http or https.
- Don’t mistake a link for a single node for a subscription. Links starting with vmess, vless, or ss require a client that supports importing individual nodes.
- If you get free nodes from this site, use the “subscription URL” whenever possible, and don’t edit its contents manually.
2. General steps for importing a subscription into Clash
- Open your Clash client and go to Profiles, Configuration, Subscriptions, or the configuration files page.
- Click New, Add, Import from URL, or a similarly named button.
- Paste the subscription link and enter a name, such as “freevpn-x,” or choose your own.
- Click Download, Update, Save, or OK, then wait for the configuration file to download.
- Return to Proxies and select a node, or start by choosing an automatic selection group.
- Go to General or the home page and enable System Proxy. Enable Tun Mode as well if you want all traffic routed through Clash.
If the download fails, check whether the link has expired, whether you copied any extra spaces, and whether your current network can reach the subscription server. Some subscriptions require browser access to work, so make sure you can open the link in a browser before updating it in the client.
3. How your IP, DNS, and browser settings are related
A successful import doesn’t necessarily mean your traffic is going through the proxy. Visit an IP-checking website in your browser. If it still shows your local ISP’s IP address, System Proxy may be disabled, the browser may have separate proxy settings, or the node may not actually be connected. Check that Clash is running on the home page, the proxy switch is on, and your system’s network proxy settings show 127.0.0.1 with the corresponding port.
DNS can also affect your experience. You might find that chat apps connect but websites don’t load, or that some sites resolve to unexpected addresses. You can enable built-in DNS in Clash settings and choose fake-ip or redir-host, depending on your client. Most users should stick with the client’s recommended defaults and avoid entering unfamiliar DNS servers.
Browser settings matter, too. Proxy extensions in Chrome or Edge may override the system proxy, while Firefox may be configured to use a proxy only within the browser. To troubleshoot, first disable extensions such as SwitchyOmega and set the browser to “Use system proxy.” If you’re using private browsing, an anti-detect browser, or remote desktop, check its network settings separately as well.
4. Quick checklist for connection problems
- Subscription update fails: Try a different network, copy the link again, and check that the subscription is still valid.
- All nodes show red: Update the subscription, run the latency test again, and try nodes in different regions.
- The subscription updates, but websites won’t load: Enable System Proxy and disable browser proxy extensions.
- Your IP hasn’t changed: Check whether the current group is set to DIRECT. Switch it to Proxy or select a node.
- Some websites won’t load: Switch the rule mode to Rule. You can temporarily test with Global, but it’s not recommended for long-term use.
After importing a subscription, get into the habit of updating it first, selecting a node, and then checking your IP and DNS. Free nodes are useful for temporary learning and testing, but their reliability depends on the route, the number of users, and your network environment. If you run into trouble, work through the steps above to quickly pinpoint the cause.