Turning the switch on starts the local tunnel; it does not guarantee that the remote server, DNS, or destination website is reachable. If you have a server configured but webpages won't load, first test the same page with the tunnel disconnected to establish a baseline. Then change one setting at a time and retest to distinguish a local network issue from a proxy egress or routing configuration problem.
1. Server connectivity: narrow down the problem first
Keep the device, network, and test pages consistent. Choose a lightweight page that normally loads directly on your current network, and keep one URL that fails to load. Reload each page in the same browser for every test; don't count a page already in the cache as a successful load. On hotel or public Wi-Fi, make sure you've completed the network sign-in first.
Establish a disconnected baseline
Turn off the connection on Home, then reload the baseline page. If connectivity returns quickly, check Settings → On Demand on your iPhone or iPad. Note the current setting, temporarily turn it off, then disconnect again from Home. If the baseline page and other commonly used sites still won't load while disconnected, troubleshoot the current network before changing Config.
Check the selected server
On Home, confirm that the expected entry is selected. Open its details and compare the protocol, server address, port, and authentication fields with the information from your existing service provider. Use the specified port; don't change the proxy server port to 443 just because the destination website uses HTTPS.
Run a test, then retest
Run Connectivity Test on Home, then open the baseline page. If the test reports latency but the page still won't load, check Global Routing and DNS next. A successful probe only confirms that the probe worked at that moment. If you have a second server already confirmed to work, switch only the server and retest, keeping the network and routing settings unchanged.
Compare with another network
Keep the server and configuration unchanged. Switch from Wi-Fi to an available cellular connection or another trusted network, then repeat the same tests. If the issue occurs on only one network, note what's different about it. If the same server fails on both networks, check its status and connection details with your existing service provider.
2. Global Routing: compare two routing modes
Note the current selection under Home → Global Routing. Keep the selected server unchanged and load the baseline page with Direct, then Proxy, and finally Config. Direct routes traffic directly while the tunnel remains connected; it is not the same as turning off the Home switch. Record the results for each state separately.
- Direct works, but Proxy fails: The issue appears along the proxy path. Check server connectivity, authentication, and egress status. Also consider a domain resolution issue along the proxy path; these results alone do not prove that the credentials are wrong.
- Proxy and Direct work, but Config fails: Focus on DNS in the active configuration, rule order, and the policy actually selected. Comparing these modes is a diagnostic step; it doesn't mean you should leave routing set to Proxy.
- Disconnected works, but both Proxy and Direct fail: First check settings that remain in effect after the tunnel takes over, such as DNS in the configuration. If the network changed during testing, repeat the test on a fixed network as well.
Config applies rules from the active configuration. If you were using Scene, note the active scene and network before temporarily switching away from Scene for troubleshooting. Otherwise, changing networks may also change the routing conditions, making it difficult to tell what caused the result.
3. DNS: identify which domain is failing
DNS can affect the result in two places: a server address entered as a domain name must be resolved first, and the destination website's domain must also be resolved somewhere along the connection path. If the server test and several proxy destinations all fail, first check whether the server address resolves. If the same server can reach other sites, focus on the failing site's domain and the domains used by its related resources.
ERR_NAME_NOT_RESOLVED
Cause: This Chromium-based browser error means the requested hostname could not be resolved. The address may be misspelled, or the current DNS resolution path may be failing. Fix: Check the hostname in the address bar, then compare the same domain with the connection disconnected and connected.
ERR_CONNECTION_TIMED_OUT
Cause: This Chromium-based browser error indicates a connection timeout. By itself, it cannot distinguish a network issue from a proxy egress or destination service problem. Fix: Test the same URL on the same network with Direct and Proxy, then try a second domain to see whether the issue affects only one site.
In Config, find the configuration that's actually enabled and back it up first. Open its editor and check the existing DNS settings under [General], such as dns-server. If the issue started right after a DNS change, restore the last known working settings first. A custom DNS resolver must be reachable from the current network and resolution path. Don't change DNS, the port, and the server all at once; otherwise, even a successful retest won't show which change fixed the issue.
Don't replace an HTTPS URL with a bare IP address to test DNS. The server may rely on the hostname to select a site, and its certificate may not match the IP. Keep the original URL and compare whether the resolution result or browser error changes.
4. Rule matching: check from the first match through FINAL
First, make sure Home → Global Routing is set to Config, then confirm the active configuration in Config. The example below shows how to read rule order; don't replace your entire configuration with it. Rules are evaluated in order, and the first match determines the policy. A request reaches FINAL only if none of the preceding rules match.
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.0.2.0/24,DIRECT
FINAL,DIRECT
- Check the full hostname:
DOMAIN-SUFFIX,example.com,PROXYmatchesexample.comand its subdomains, but not login pages or static resources on a different domain. If the homepage loads but the login button keeps spinning, check the domains for both the main page and the failing resource. - Check broad rules higher up:
IP-CIDRmatches by IP range;192.0.2.0/24in this example is a documentation-only network.GEOIPmatches based on IP geolocation. Check whether an earlier domain or IP rule assigns a different policy than expected; don't look only at the last line. - Check the fallback and egress:
FINAL,DIRECTsends requests that didn't match earlier rules to DIRECT. Even when a rule matches PROXY, the proxy egress still has to work. If the rule points to a policy group, check its currently selected option too; a matching rule does not prove that the connection succeeded.
The diagram shows where to troubleshoot, not a fixed order for DNS processing: domain rules can match by hostname, while IP-based rules may need an address first. After making a change, retest the original URL and then check a commonly used site whose rules you haven't changed. If the issue occurs only in one app while the browser works, test that app separately; don't use it as a reason to route more of the configuration through the proxy.
5. Record retest results and restore settings
If you still haven't found the cause, keep a minimal record that reproduces the issue. A clear account of what changes the result is more useful than simply saying, “It shows connected, but I can't get online.”
- Record the device platform, current network, failing domain, and exact browser error. Note the results for disconnected, Direct, Proxy, and Config.
- Note the most recent change before the issue started, such as switching Wi-Fi, updating your own configuration, or changing DNS. Before sharing details, remove authentication information, complete subscription URLs, and any tokens they contain.
- Revert temporary changes that didn't help. Restore the original Global Routing and On Demand settings, then confirm that sites you could access before still load.