How can you access the internet through a proxy on your phone? Why might websites still fail to load after importing nodes, or still show the same location? This guide walks you through the basics—from installing a client and importing a subscription to checking your IP, DNS, and browser settings. Please understand and comply with the laws and regulations in your location and the rules of any services you use.
1. Get a client and a working subscription
You’ll need a client that supports the relevant protocol, along with node links or a subscription URL from a trusted source. VLESS and VMess are connection protocols, while Clash and sing-box are clients or configuration ecosystems. A link’s name alone doesn’t tell you whether it can be imported. First, make sure the client supports the subscription format; don’t assume a Clash configuration is a universal node link.
Android users should install apps from the project’s official website, official code repository, or a trusted app store. iPhone users can choose a client that supports the relevant protocols in their region’s App Store, and should verify the developer. Don’t install modified app packages shared by strangers, or install an untrusted root certificate just to use a node. The free nodes on this site can be used for testing, but their availability may change.
2. Import nodes and connect on your phone
- Copy a node link or subscription URL. Subscriptions may contain access credentials, so don’t share screenshots or forward them.
- Open the client and, under “Subscription,” “Configuration,” or “Add,” choose to import from the clipboard or paste the subscription URL. Menu names vary by version.
- Update the subscription and select a node. If you see a format error, first check that you copied the full link, then confirm that the protocol and configuration format are compatible.
- Use “Rule” mode as a starting point for everyday use, so traffic is handled according to the rules. To check whether routing rules are the problem, temporarily switch to “Global” mode for testing.
- Turn on the connection and allow the system to create a VPN configuration. On Android, if the client offers VPN/TUN mode, you’ll generally need to enable it for the client to handle traffic from other apps.
- Test the target website in your browser, then check the client logs for timeouts, DNS resolution failures, or authentication errors.
Seeing a VPN icon doesn’t mean the node is working; it usually only indicates that the system tunnel is enabled. You still need to test whether websites load.
3. What IP, DNS, and browser settings affect
Your exit IP is the network address websites see. In Rule mode, domestic websites may connect directly while international websites use the proxy, so different sites may show different locations. When checking your exit IP, make sure the test page itself is routed through the proxy. IP geolocation databases can also be inaccurate.
DNS translates domain names into IP addresses. DNS problems can prevent websites from opening by name even when other connections work. Start with the DNS settings recommended by your client, and avoid using multiple DNS tools at once. Android Private DNS, your browser’s secure DNS, and the client’s DNS settings may interact. Change one setting at a time and test again.
Browser settings also include cookies, sign-in status, language, and location permissions. Websites don’t determine your location from your exit IP alone, and changing nodes won’t automatically clear stored data. Try comparing results in a private window and check the site’s location permissions, but remember that private browsing doesn’t make you anonymous.
4. Troubleshoot connection issues step by step
First, disconnect the client and confirm that your phone can access the internet on its own. Then update the subscription, switch nodes, and test both Wi-Fi and mobile data. If only one app fails, check per-app proxy settings and rules. If all websites fail, review the logs and verify your system clock. Finally, check for conflicts with other VPNs, ad blockers, or firewalls. Change only one setting at a time and record the result—it’s easier to find the cause this way than by changing nodes, DNS, and modes all at once.