This article explains how to import a subscription into Clash and why you might still be unable to access the internet afterward. It also covers how exit IPs, DNS, and browser settings can affect your connection. Menu names vary slightly among Clash-compatible clients, so the steps below use common options such as “Configuration,” “Subscription,” and “Proxy.” They do not cover server setup.
I. What to prepare before importing
First, install a Clash-compatible client for your operating system. Prefer downloading it from the project’s official release page, and avoid modified versions from unknown sources. Get the subscription link from your service provider. It usually starts with HTTPS and should return configuration content supported by the client—not a purchase page or regular webpage. A subscription link may contain an access token, so don’t share screenshots of it or post it in a group chat.
If you use free nodes listed on this site, first check whether the link provided is a subscription link or a link for a single node. They are not interchangeable in every client. Import a single node as described on the page; don’t use it as a Clash subscription.
II. How to import a subscription into Clash
- Open the client and go to “Configuration,” “Profiles,” or “Subscription.” Click “New,” “Add,” or “Import from URL.”
- Paste the complete subscription URL. Check for spaces or line breaks at the beginning or end. You can enter a descriptive name to make it easier to identify.
- Click “Download” or “Save,” then wait for the configuration to appear. If parsing fails, first check whether the subscription is compatible with your client. Don’t modify the URL parameters without a clear reason.
- Select and enable the configuration you just imported, then choose a node on the “Proxy” page. If there are proxy groups, make sure the group used to access your target website isn’t set to DIRECT.
- On desktop, enable “System Proxy.” On mobile, allow the client to create a VPN connection when prompted. Then visit a familiar website to check that it loads properly.
A successful import only means the configuration was downloaded; it doesn’t guarantee that a node is working. We recommend testing in rule mode first and adjusting settings as needed. There’s no need to enable TUN or global mode right away. You can update the subscription manually from the configuration page. If an update fails, keep the existing configuration for now.
III. How IP, DNS, and browser settings affect your connection
Your exit IP depends on the route your traffic takes. When browser traffic goes through a proxy, websites you visit will generally see the proxy’s exit IP. If a rule sends traffic directly, they may see your local network’s IP instead. A single IP lookup site can’t tell you whether all your apps are using the proxy.
DNS translates domain names into addresses. If DNS resolution fails, the client may show that it’s connected while the browser reports that the server can’t be found. Keep the client’s default DNS settings to start with, and check the logs for resolution errors. Don’t change multiple DNS options at once.
Your browser may also have its own proxy extension or secure DNS enabled, causing it to behave differently from other apps. Try temporarily disabling proxy extensions and comparing the results in another browser. Incognito mode won’t change your exit IP or fix a faulty node.
IV. How to troubleshoot import or connection failures
- Subscription download fails: Check whether the link has expired and whether your current network can reach it. Contact your provider if necessary.
- Configuration parsing fails: Check the subscription format and client compatibility. Make sure you’re not using a regular webpage URL as the subscription URL.
- All nodes time out: Check your local network and system clock first. Then update the subscription, try another node, and review the logs for connection errors.
- Only the browser won’t load pages: Check your proxy extension, secure DNS, and whether the system proxy is working. After making changes, restart the browser and test again.
Change only one setting at a time while troubleshooting, and record the results. Before sharing logs, hide subscription tokens, account details, and other sensitive information.