How do you access the internet through a proxy on your phone? This guide explains how to install a mobile client, import nodes or a subscription, and troubleshoot websites that still won’t load after you connect. It also covers the respective roles of IP addresses, DNS, and your browser environment. Before you begin, make sure your use complies with local laws and regulations and the service’s terms. Don’t install packages or configuration profiles from unknown sources.
1. Get a client and node ready
You’ll generally need a mobile client that supports the proxy protocol you plan to use, along with a working node link or subscription URL. On Android, choose a client that supports protocols such as VLESS, VMess, or Trojan. On iPhone, get an app from the App Store that supports the relevant protocol. Subscription formats vary between clients, so check that the protocol and subscription format are compatible before importing—don’t rely on the link’s name alone.
Node details typically include a server address, port, and authentication parameters. A subscription makes it easier to obtain and update multiple nodes. You can refer to the format guidance on this site’s free nodes page, but free nodes may not always be available and aren’t recommended for sensitive activities. Subscription links may contain access credentials, so don’t share screenshots or the full link publicly.
2. Connect your phone
- Install a client from an app store or the project’s official release channel. Open it and check that it supports your node’s protocol.
- Copy the node link and select “Import from clipboard.” If you have a subscription URL, go to “Subscription management,” add the URL, and update the subscription. Menu names may vary slightly.
- Select a node and start with “Rule” or “Split tunneling” mode, so the client routes connections according to its rules.
- Tap Connect and allow the system to create a VPN connection. The VPN indicator means the client is handling traffic; it doesn’t, by itself, confirm that the node is working.
- Open the website you want to visit, then check whether your exit IP is what you expect. A successful latency test alone doesn’t mean every website will load properly.
Use only one VPN or proxy app at a time while testing to avoid multiple tools competing for the system connection. If you’re using Android and the connection drops frequently, check whether battery optimization is restricting background activity. On iPhone, check for interference from other VPN configurations or on-demand connection settings.
3. What IP, DNS, and your browser affect
Your IP is the network exit address that websites see. In rule-based mode, different websites may use different exits, so seeing a local address on an IP-checking website doesn’t necessarily mean the proxy is entirely broken. Check whether the destination website matches a proxy rule.
DNS translates domain names into addresses. Websites may not load if DNS lookups fail, return unexpected results, or aren’t routed as intended. Use the DNS settings recommended by the client where possible. Avoid changing the system’s Private DNS, the browser’s Secure DNS, and the client’s DNS settings all at once, or it will be harder to pinpoint the cause.
Your browser also stores cookies, cache, and site permissions, and may provide information such as your language, time zone, and location. Changing your exit IP doesn’t make you anonymous or guarantee that a website will show a different region. Your account region, location permissions, and previous login activity may also affect what you see.
4. Troubleshoot connection issues step by step
- Disconnect the proxy and confirm that your phone can access the internet. Then compare results over Wi-Fi and mobile data.
- Update your subscription and try a different node. If importing fails, check that the link is complete and the format is supported.
- Check the system date and time, then review the client logs for timeouts, authentication errors, or DNS errors. Avoid changing every setting at random.
- If the problem occurs only in your browser, test in a private window. If needed, clear data for the affected site only; this may sign you out.
Change only one setting at a time and test again. If switching temporarily to global mode restores access, focus on the routing rules. Restore your original settings after testing to avoid routing unnecessary traffic through the proxy.