How do you access the internet through a proxy on your phone, and why does the client say it’s connected when your browser can’t open any pages? This article walks you through installing a client and importing a subscription, then checking your exit IP, DNS, and browser settings. It applies to Android and iPhone. Before you begin, make sure you understand the laws and network-use regulations in your area.
1. Get a client and node subscription ready
You’ll need a client that supports your node’s protocol, plus a node link or subscription URL from a trusted source. VLESS, VMess, and Trojan are common proxy protocols. Clash and sing-box configs are client configuration formats, so a link’s name alone doesn’t tell you whether it’s compatible with your client.
- Android: Choose a client that’s still maintained, such as v2rayNG, or one that supports Clash or sing-box configs.
- iPhone: Get a client that supports the relevant protocol from the App Store. Availability depends on your region’s store.
- Installation sources: Prefer the project’s official release page or a reputable app store. Avoid installing unfamiliar packages that ask you to disable security protections.
First, check that the subscription format is compatible with your client. The free nodes offered on this site can be used for testing, but availability may change. Don’t rely on them as your sole connection for sensitive work.
2. Import the subscription and connect for the first time
- Copy the subscription URL, open the client’s “Subscription,” “Config,” or “Add config” menu, and choose the option to import from a URL. For a single-node link, use the import-from-clipboard or QR code feature.
- Update the subscription and confirm that the node list appears. If it’s empty, check that the URL is complete and hasn’t expired, and that your current network can reach the subscription source.
- Choose a node. For your first connection, you can keep the client’s default routing rules, then tap Connect.
- Allow the system to create a VPN connection. Android typically displays a connection request, while iPhone prompts you to add a VPN configuration. These are normal system authorization steps.
- Open the site you want to visit to test the connection. If you’re already using another VPN, ad blocker, or packet capture tool, pause it first to avoid competing for the system VPN connection.
“Connected” only means the local connection process has started; it doesn’t guarantee that the node is working. A latency test returning a result doesn’t guarantee that every website will be accessible, either.
3. What your IP, DNS, and browser each affect
Your exit IP is the address websites see as the source of your connection. After connecting, visit a trusted IP lookup page and compare the results. In rule mode, domestic sites may connect directly, so an unchanged IP doesn’t necessarily mean something is wrong. Check whether traffic to the site you’re trying to reach is routed through the proxy.
DNS translates domain names into addresses. If only some domains fail to load or you see a “server not found” message, restore the DNS settings recommended by your client and reconnect. Changing DNS is not a substitute for connecting through a proxy. Also, don’t change your system’s Private DNS, the client’s DNS, and the browser’s secure DNS all at once, or it will be difficult to pinpoint the problem.
Your browser also retains cookies, cache, and site permissions. A website’s displayed region may be affected by your account region, location permissions, and browsing history, so it may not match your exit IP. Compare results in a private window and check whether location access is enabled. Private browsing itself does not change your IP.
4. Troubleshoot connection problems in this order
First, disconnect the proxy and confirm that your basic network connection works. Then update the subscription and try a different node. Next, switch between Wi-Fi and mobile data to see whether the issue is related to your current network. If only the browser is affected, test with another browser or a private window. If all apps fail, check the client logs for timeouts, DNS resolution failures, or authentication errors.
If the problem persists, check that your system time is set to sync automatically, and update the client. Change just one setting at a time, recording the result before moving on. If you ask someone for help, you can share your OS version, client version, and error message—but be sure to hide your subscription URL, password, and node credentials.