This article explains how to import a subscription into Clash and troubleshoot common issues after importing, such as websites still not loading, your IP address not changing, DNS leaks, or an unexpected browser environment. It’s intended for everyday users who have just received a subscription URL, a free node link, or a VPN provider’s subscription address. Follow the steps below to import it and perform basic troubleshooting.
1. What to prepare before importing a subscription
Clash clients come in several versions, such as Clash Verge, the older Clash for Windows, and Clash Meta GUI. Their interface labels may differ slightly, but the basic process is the same: copy the subscription URL, add a configuration, update the subscription, select a node, and enable the proxy.
- Make sure the subscription URL is complete. It usually starts with http or https.
- Don’t paste a single vmess, vless, or trojan node as a subscription unless your client supports parsing it.
- If you’re using a free node from this site, we recommend copying the “subscription link” rather than adding nodes one by one.
- Make sure your computer or phone has the correct system time; otherwise, TLS connections may fail.
2. General steps for importing a subscription into Clash
- Open the Clash client and go to Profiles, Configuration, Subscriptions, or the configuration files page.
- Click New, Add, Import from URL, or “Import from URL.”
- Paste your subscription URL and give it a name, such as freevpn-x or daily-sub.
- Click Download, Update, or Save, then wait for the client to fetch the configuration.
- Return to Proxies or the proxy page and select a node. You can also start with an automatic selection group.
- Go to General or Settings and turn on System Proxy. Choose Global for global proxying or Rule for rule-based routing.
Successfully importing a subscription doesn’t necessarily mean your connection is working. Make sure System Proxy is enabled and that no other proxy extension in your browser is overriding the settings.
3. What IP, DNS, and your browser environment affect
Many users assume that successfully importing a subscription means their network environment has changed, but Clash mainly handles “proxy traffic.” If your browser, DNS, or system settings aren’t aligned, the results of network checks may be inconsistent.
Your IP address tells websites where your outgoing connection appears to be coming from. If an IP lookup site still shows your local ISP’s IP address, System Proxy may be disabled, the wrong mode may be selected, or your browser may not be routing traffic through Clash.
DNS translates domain names into IP addresses. If your local ISP is still handling DNS, you may encounter DNS poisoning, slow resolution, or websites that won’t load. We recommend enabling the built-in DNS in Clash or using the client’s default enhanced mode. If you’re unsure about the settings, don’t change advanced options at random.
Your browser environment includes language, time zone, WebRTC, cache, and extensions. Even if the proxy is working, WebRTC may expose local network information, or old cached data may cause websites to keep showing content for your original region. Try testing in a private window and, if needed, disable proxy-related extensions.
4. Troubleshooting import and connection failures
- Download failed: Check whether the subscription has expired and whether the URL was copied in full. Try opening the link in a browser to see whether it downloads text.
- All nodes are red: Update the subscription first, then switch networks. Public free nodes may be temporarily unavailable, so try another node.
- Connected, but websites won’t load: Switch between Rule and Global mode, check that System Proxy is enabled, and restart your browser.
- Only some websites won’t load: This is often related to rules, DNS, or node compatibility. Try another node or update the client’s core.
- Not working on mobile: Make sure VPN permissions have been granted and that no other VPN app is running at the same time.
If you’re new to Clash, start with “import subscription + Rule mode + automatic node selection.” Once that works, you can explore routing rules and DNS settings. When problems arise, check these four things: whether the subscription updates, whether the node is available, whether System Proxy is enabled, and whether your browser is using the proxy. This is usually enough to identify the cause.