This guide explains how to import a subscription into Clash, connect after importing it, and troubleshoot cases where your browser IP still hasn’t changed. Follow the steps below to add a subscription, update the configuration, select a node, and enable the proxy. Then, based on what you observe, check your DNS and browser settings. Menu names may vary slightly between Clash-based clients, so refer to the interface you’re using.
1. What to prepare before importing
Install a Clash-compatible client that supports your operating system and is still maintained. Whenever possible, download it from the project’s official release page. You’ll also need a subscription link that explicitly supports the Clash or Mihomo configuration format. A single node link, such as a vless:// link, usually can’t be used directly as a configuration subscription.
A subscription link is an access credential. Don’t share screenshots containing it, post it in a group chat, or submit it to an untrusted online conversion service. If you use a free node from this site, check the format notes and last-updated time on the relevant page first. Availability depends on whether the connection works at the time of use.
2. How to import a subscription into Clash
- Copy the complete subscription URL, making sure it contains no spaces, line breaks, or Chinese punctuation.
- Open the client and go to “Configuration,” “Profiles,” or “Subscriptions.”
- Look for an option such as “Import from URL” or “Add remote profile.” Paste the URL and enter a name that will help you identify it.
- Click Download or Import, then wait for the configuration to appear. If it fails, save the error message and avoid repeatedly overwriting your existing configuration.
- Select and enable the newly imported configuration. Go to “Proxies” and choose a node in the policy group you’ll actually use—don’t just expand the list.
- Turn on “System Proxy,” select “Rule” mode to start, and test by opening a webpage. If you need to route traffic from more applications, enable TUN as directed by your client’s documentation.
A successful import doesn’t mean your traffic is going through the proxy. Make sure the configuration is enabled, a node is selected in the policy group, and traffic is being routed through the proxy. For your first test, pause other proxies or VPNs to avoid conflicts.
3. How to check whether your IP and DNS are working properly
Open a trusted IP lookup page and check whether the reported exit IP is what you expect. In Rule mode, different websites may connect directly or through the proxy, so seeing your local IP on one lookup page doesn’t necessarily mean the subscription is broken. For comparison, temporarily switch to Global mode and select a proxy node. Once you’ve tested it, switch back to Rule mode.
DNS translates domain names into IP addresses, while your exit IP depends on the route your connection takes. They’re not the same thing. If a webpage says it can’t resolve a domain, first check the client logs and DNS status. Don’t start by changing DNS parameters in the configuration at random. Secure DNS in your browser may change the resolution path, but that doesn’t necessarily mean webpage traffic is bypassing the proxy.
4. What to do if the import fails or your browser won’t open pages
- Download times out: Check your network, the subscription link’s expiration, and the service provider’s instructions. If you need a proxy to access the subscription, try an existing working connection.
- Format error: Make sure the link returns a compatible configuration, not a login page, error page, or subscription format intended for a different client.
- Configuration is present but there are no nodes: Manually update the subscription and check for parsing errors or empty content.
- Node times out: Try another node and check your system clock. A latency test doesn’t guarantee that webpages will load.
- Only the browser has problems: Check proxy extensions, the browser’s own proxy settings, and its cache. You can also compare results in a private window.
Troubleshoot in this order: subscription download → configuration enabled → node selected → proxy routing enabled → browser. This makes it easier to find the cause than repeatedly reinstalling the client. You can back up a working configuration before updating, but don’t upload a backup containing credentials to a public location.