How do you access the internet through a proxy on your phone? Why might webpages still fail to load after importing nodes, or why might a website show the same location? This article walks you through installing a client, importing a subscription, and verifying the connection. It explains the roles of IP addresses, DNS, and your browser environment, helping you troubleshoot in order. Follow the laws where you live and the terms of service of your network providers, and prioritize clients and subscriptions from clearly identified sources.
1. Get a client and a working subscription
Phones typically need a client that supports the relevant protocol, as well as a node link or subscription URL. VLESS and VMess are connection protocols, while Clash and sing-box are associated with client ecosystems or configuration formats. Don’t assume you can import a link just because you have it. The subscription format must be compatible with the client; an import error doesn’t necessarily mean the node is no longer working.
- Android users should install a client from the project’s official website, official code repository, or a trusted app store. iPhone users should choose an app in the App Store that supports the relevant protocol and subscription format, and verify the developer’s information.
- Copy the subscription URL from a trusted source, then find “Subscription,” “Configuration,” or “Import from URL” in the client. Paste the URL and update it. The free nodes on this site can be used to test your connection, but availability may change, so don’t rely on them as your only source.
- Select an entry from the node list. The first time you connect, allow the system to add a VPN configuration. You generally don’t need to install an additional root certificate, and you shouldn’t disable system security protections in response to unfamiliar prompts.
- Start the connection in “Rule” or “Auto” mode, then test it in your browser. If you can’t access the site, you can briefly switch to Global mode for comparison, then switch back to Rule mode after testing.
2. What do IP, DNS, and the browser each affect?
Your IP address mainly reflects your network’s point of egress. When a proxy connection is active, websites you access through it will usually see the node’s exit IP. Apps using a direct connection may still show your local carrier’s IP. So, seeing a VPN icon in the status bar doesn’t mean all app traffic is going through the proxy.
DNS translates domain names into addresses. DNS timeouts, unexpected results, or a mismatch between the DNS route and your proxy rules can all cause the “connected, but webpages won’t load” problem. Start with the client’s default or recommended DNS settings, and don’t enter addresses you’ve found online at random. Android’s “Private DNS” and your browser’s “Secure DNS” can also change how lookups are routed. When troubleshooting, note your original settings and compare them one at a time.
Your browser also stores cookies, sign-in status, cached data, and location permissions. A website’s reported region may come from your account details, GPS, or browsing history—not just your IP address. Changing your exit IP doesn’t clear your browser identity or guarantee that a particular service will work.
3. Troubleshoot connection failures in this order
- Turn off the proxy and make sure your phone can access the internet normally. Switch between Wi-Fi and mobile data to rule out basic network problems.
- Check that the subscription updated successfully and that the node hasn’t expired. Make sure your system date and time are set automatically, then try another node. Latency readings can help with diagnosis, but they don’t replace testing actual webpages.
- Make sure no other VPN, ad-blocking, or firewall app is using the connection. On Android, also check whether battery optimization is preventing the client from running in the background.
- If Global mode works but Rule mode doesn’t, focus on the routing rules. If only one browser fails, try an incognito window and check its DNS settings, extensions, and site permissions.
- Check the client logs for timeouts, DNS resolution failures, or authentication errors, and verify the network, DNS, or node details accordingly. Before sharing logs, remove subscription URLs, tokens, and personal information.
Finally, cross-check your results using an IP lookup page and by visiting an actual webpage. Change only one setting at a time and record the results; this makes it easier to find the cause than repeatedly reinstalling the client. Free nodes may stop working temporarily. Don’t share your subscription URL publicly or enter sensitive information on pages from unknown sources.