This article explains how to import a subscription into Clash and why you might still be unable to connect afterward. Follow the steps in order: add the subscription, enable the proxy, and test the connection. It also explains how IP addresses, DNS, and your browser environment each affect connectivity. Button names may vary slightly across Clash-compatible clients; look for entries such as “Configuration” or “Profiles,” and “Proxy” or “Proxies.”
1. Before importing: check your client and subscription format
First, install a Clash-compatible client for your operating system that is still maintained. Get it from the project’s official release page whenever possible, and avoid modified versions from unknown sources. You’ll also need a Clash- or Mihomo-compatible subscription link from your service provider. A regular webpage URL or a single vless:// link may not work as a Clash subscription.
Subscription links often contain access credentials, so don’t share them publicly or include them in screenshots. When copying the link, check for spaces, line breaks, or Chinese punctuation. If this site’s free-node page provides a subscription, first make sure its format is compatible with your client. You’ll still need to test whether the nodes can connect.
2. How to import a subscription into Clash
- Open the client and go to “Configuration,” “Subscriptions,” or “Profiles.” Look for an option such as “New,” “Import,” or “Import from URL.”
- Paste the full subscription link, enter a name you’ll recognize, and click Download or Save. If an error appears, check whether it’s a network timeout or a configuration parsing failure.
- Once the download is complete, select and enable the configuration. A successful download doesn’t mean the configuration is active. Some clients require you to switch to the new configuration manually.
- Go to the proxy page, open the policy group used for external traffic, and select a node. For your first test, choose one manually so you can see which node is in use instead of relying on an automatic group.
- On a computer, enable “System Proxy” and start with “Rule” mode. On a phone, follow the prompts to allow a VPN connection. TUN mode isn’t required for initial setup.
- Open a browser and visit a test website, then check the client’s connection log to confirm that requests are going through the expected policy group. You can set up automatic subscription updates afterward if needed.
3. How do IP, DNS, and your browser environment affect connectivity?
Your exit IP shows which network exit your request is using. Importing a subscription doesn’t change your IP on its own; it may change only when your traffic actually goes through the proxy. In Rule mode, domestic websites usually connect directly as intended, so a single IP lookup page isn’t enough to determine whether the setup has failed.
DNS translates domain names into addresses. If a node works but some domains won’t load, the issue may be related to DNS resolution, caching, or the client’s DNS settings. Keep the default configuration at first and check the logs before making changes. Avoid changing multiple settings at once.
Your browser may also be affected by proxy extensions, Secure DNS, cached data, or your sign-in status. Changing your exit IP won’t automatically clear cookies or change your browser identity. To troubleshoot, temporarily disable other proxy extensions and compare results in a private browsing window. Keep in mind that private browsing doesn’t guarantee anonymity.
4. How to troubleshoot import or connection failures
- Download fails: Check that the link is complete and the subscription hasn’t expired. If the link can’t be fetched directly, follow the provider’s instructions for updating it over an available network.
- Parsing fails: Confirm that the format is Clash-compatible and check the client version. Don’t import a subscription error page as a configuration file.
- Nothing works after import: Check that the configuration is enabled and the system proxy is on. Make sure the policy group isn’t set to DIRECT by mistake, then try another node.
- Only the browser fails: Disable conflicting extensions, check the browser’s own proxy settings, and use the client logs to help pinpoint the issue.
If the issue persists, note the client version, the exact error message, and the steps that failed. Before asking others for help, redact your subscription link, token, and any other sensitive information.