Check in this order: public IP first, then app routing

VPN says connected but isn’t working? First, compare your public IP before and after connecting in the same browser, then check whether the app you’re testing matches a proxy rule. A “Connected” status in the client doesn’t mean every new request from every app goes through the tunnel. Likewise, a website showing your old region doesn’t prove the request is going direct. Check your IP, DNS resolution, and app routing separately to confirm what’s happening.

What the results mean and what to do next
What you seeWhat it may meanNext step
Your browser’s public IP has changedThe address shown by the test page has changed, but that doesn’t mean other apps use the same route.Test the app separately.
Your public IP hasn’t changedThe test request may be going direct under a rule, or it may be reusing a connection established before you switched.Restart the browser and check which rule matches the test domain.
DNS still shows the same resolverA resolver can remain in use with a different egress route; its name alone doesn’t prove a leak.Check the browser’s secure DNS settings and the client’s DNS policy.
The target website still shows your old regionThe website may be using your account region, location permissions, or an existing session.Check the request route first, then compare the page before and after signing in.

Public IP: how to compare before and after connecting

  1. Record your IP before connecting. On a network where direct access is allowed, keep the same device and network connection, open the network test page in the same browser, and note the public IP it shows. Don’t use your device’s local network address instead.
  2. Send a new request after switching. Select a route, confirm that the client shows as connected, then fully quit and reopen your browser before visiting the same test page. Don’t rely on a page that was already open before the switch; it may still show an old result. If another proxy or a browser proxy extension is enabled, note that too so you don’t mistake its egress IP for the current route.
  3. Compare the same IP version. If possible, test IPv4 and IPv6 separately. Don’t compare your pre-connection IPv4 address with your post-connection IPv6 address. If IPv4 has changed but IPv6 still shows your original public address, check whether the client handles IPv6 and whether the request matches a direct-connection rule. If the test page doesn’t show IPv6, that alone doesn’t prove IPv6 is handled or blocked.

In rule-based mode, the test website itself may be assigned to a direct-connection group. An unchanged IP doesn’t prevent other apps from using the proxy. First, check the client’s connection log for the test domain. If you need a comparison and your device policy allows it, temporarily switch to the client’s global proxy mode and send a new request. Restore your original settings afterward. Global proxy mode may not capture apps that don’t use the system proxy, so check how the client handles traffic.

DNS troubleshooting: check whether resolution follows your policy

DNS resolves domain names to IP addresses, and DNS requests can take a different route from webpage connections. A browser’s secure DNS may use its own resolver, while your system’s encrypted DNS settings may affect other apps. A change in your webpage’s exit IP doesn’t mean DNS requests follow automatically. And seeing a public resolver listed on a test page doesn’t mean the query went directly through your local network.

  1. Run the same DNS test in the same browser before and after connecting, and note the resolver shown. A test page can generally reveal which recursive resolver queried the test domain, but it can’t reconstruct the full path between your device and that resolver.
  2. Check the browser’s secure DNS, your system DNS settings, and the client’s DNS policy. If the client shows DNS logs, see whether the test domain was handled by the expected resolver. Change one setting at a time and run the test again so you don’t mistake a cached result for a new query.
  3. Check against your intended setup. If your configuration requires DNS queries to be handled by a resolver inside the tunnel, but you confirm the test domain was sent to a resolver on your local network, check DNS handling and rule exceptions. If you intentionally use a separate resolver, check the route to that resolver rather than relying on its name alone.

Some enterprise apps rely on internal DNS. If only internal domains fail to load, ask your administrator whether you need internal DNS and a specific network. Don’t change your corporate network settings just to make a public test page show a particular resolver.

Test each app: browser works, other apps connect directly

System proxy settings affect only apps that follow them. Browser extensions usually affect only requests made in the browser, and tunnel mode may allow direct connections based on app, domain, or IP address. So if your browser uses the expected route but a meeting app or desktop client doesn’t, first check whether the app is covered, then find out which domains it actually connects to.

  • ✅ Check the per-app list. Find out whether the configuration proxies only selected apps or excludes selected apps, then confirm the target app is included or excluded as intended.
  • ✅ Fully quit and reopen the target app, then trigger a new action, such as refreshing an online list. Check the client’s connection log at that time for the process, destination domain, and outbound rule. No log entry doesn’t necessarily mean the app connected directly; the client may not log that type of traffic.
  • ✅ Test each feature separately. Being able to open the sign-in page doesn’t mean calls or file sync use the same route. An app may use different domains or transport methods for different features.
  • ❌ Don’t use a browser’s IP result to draw conclusions about other apps, and don’t assume a request succeeded just because it appears in the log. Check whether the action actually received a response.

Common issues: connection drops after switching networks, or the IP changes but the page doesn't

Problems after switching networks or resuming from sleep

After switching from Wi-Fi to mobile data, first check that the new network can reach ordinary sites that allow direct access, then see whether the client has reconnected. Some public networks require access authentication first. If the connection fails on an Android device only after the screen locks, check the system’s background activity and battery restrictions, then retest with the same page. For help checking client settings, see the Android quick start guide.

Your IP has changed, but the feature you need still fails

First, determine whether the request is timing out or the page loads but still shows the wrong region. For timeouts, check the outbound logs for the target domain and related connections, and confirm that routing matches your expectations. If the content region hasn’t changed, compare the public page in a new browser window while signed out, then check your account region and location permissions. A changed IP on the test page doesn’t guarantee a site will accept that IP or that your account region will change.

If you still can’t pinpoint the issue, note your device platform, connection mode, time of the error, route name, and the action that triggered it. If possible, include the relevant rule match. When contacting support through the support ticket portal, share only the necessary excerpts. Don’t include a full subscription URL or logs containing account credentials.