How do you access the internet through a proxy on your phone? Why might web pages still fail to load after importing nodes, or why might a site still show a region warning even after your IP has changed? This guide walks you through installing a client, importing a subscription, checking your IP and DNS, and troubleshooting your browser environment. It applies to Android and iPhone. Before you begin, check your local laws and network-use rules, and learn about the source of your nodes and the provider’s privacy policy.
1. Prepare a client and a valid subscription
Your phone needs a client that supports your node’s protocol, along with a working node link or subscription URL. VLESS, VMess, and Trojan are common proxy protocols, while Clash and sing-box configurations use different formats. A file extension alone doesn’t tell you whether a configuration is compatible. Check which protocols and subscription formats your client supports before importing anything to reduce the risk of parsing errors.
- Android: Install a maintained client from the project’s official website, official release page, or a trusted app store. Avoid modified APKs from unknown sources.
- iPhone: Get a client that supports the relevant protocols from the App Store, and check the system requirements and whether the app is paid.
- Subscription: You can use a subscription from a trusted provider or refer to the instructions on this site’s free nodes page. Free nodes may stop working or become congested, so avoid using them for sensitive activities.
2. Import nodes and connect
- Copy the full subscription URL. In your client, find “Subscription,” “Configuration,” or “Import from URL,” then paste the URL, save it, and update the subscription. Don’t submit your subscription URL to unfamiliar conversion websites.
- If you have a single node link, use “Import from clipboard.” If you have a QR code, scan it with the client. After importing, check that the node list isn’t empty.
- When prompted on first launch, allow the system to add a VPN configuration. This VPN indicator means traffic is routed through the client’s system tunnel; it doesn’t mean every app will necessarily use the proxy.
- Select a node and connect using rule mode first. If you can’t access the site you’re testing, briefly switch to global mode to compare. When you’re done, switch back to rule mode if appropriate.
- Open a site you can normally access, then test the site you’re having trouble with. This can help you tell a local network issue from a proxy connection problem.
3. Understand how IP, DNS, and your browser are related
Exit IP, DNS resolution, and your browser environment are three separate things. Your exit IP is the network address a website sees. DNS translates domain names into addresses; a DNS lookup that fails or returns an unexpected result may prevent a page from loading. Cookies, login status, language, time zone, and location permissions in your browser can also affect how a site determines your region.
After connecting, you can check your public IP, but in rule mode the IP-checking page may connect directly, so the result doesn’t prove that all traffic is routed through the proxy. If you suspect a DNS issue, first check your client’s DNS or leak-protection settings and enable them according to the official instructions. Temporarily rule out conflicts with Android Private DNS or other DNS apps. Don’t assume that “switching to a public DNS” will fix the problem.
4. Troubleshoot connection failures step by step
First switch between Wi-Fi and mobile data, then update your subscription and try a different node. Make sure your phone’s date and time are set to sync automatically. While testing, pause other VPNs, ad blockers, or apps that intercept network traffic to avoid conflicts. If the connection works but a particular site behaves unexpectedly, compare it in a private browsing window and check the site’s location permissions and your login status. Private browsing does not make you anonymous or automatically change your exit IP.
Don’t rely on “Connected” as the only sign that the service is working. If the problem persists, check the client logs for timeouts, resolution failures, or authentication errors, then troubleshoot the specific issue. Before sharing screenshots or logs, be sure to hide your subscription URL, node password, and other credentials.