· Troubleshooting · About 8 minutes

Shadowrocket Connected but No Internet: Check the Server, Routing Mode, DNS & Rules

If Shadowrocket is connected but websites won't load, check the server, Global Routing mode, DNS settings, and matching rules in order. Each step includes what to check and how to restore your settings.

At a glance

A connected switch does not guarantee that the selected server can forward requests or that the destination domain resolves correctly. This guide is for iPhone and iPad users who have imported their own configuration but can't access websites. Start by comparing the same URL with the connection off, then check the server, routing mode, DNS, and rules one at a time. Test after each change, then restore the original setting.

1. Server: Check the Selected Entry First

First narrow down the problem: do all websites fail, or just one? Choose a URL that fails and another that normally opens directly on your current network. Note whether you're on Wi-Fi or cellular. Keep the network, browser, and URLs unchanged during each round of testing. If the page may be cached, reload it; don't rely on a page that was already open to confirm the connection is working again.

  1. Note the Original Settings

    In Home, note the selected server and Global Routing mode. In Config, note the active configuration. If the list has multiple entries with the same name, compare their address, port, and protocol before switching; don't rely on the name alone.

  2. Test with the Connection Off

    Turn off the connection switch in Home, then load the comparison URL. If the switch turns itself back on, check whether Settings → On Demand is enabled. If your device allows it and doing so doesn't conflict with management requirements, temporarily disable the feature for testing, then restore its original setting. If the comparison URL also fails while disconnected, first check whether the network requires sign-in and whether it has internet access.

  3. Test the Selected Server

    In Home, check the selected entry, run Connectivity Test, and review its result. A timeout means only that this test didn't finish within the time limit; one timeout alone doesn't prove the configuration is invalid. A latency result doesn't guarantee the failing website is reachable either, since the test may use a different destination.

  4. Retest with an Existing Entry

    If you already have a backup entry known to work, keep the network and routing mode unchanged. Switch only the server, reconnect, and load the same URL. If switching servers resolves the problem, check the original entry's parameters and service status first. If nothing changes, select the original entry again and check the routing mode.

If the problem started right after a subscription update, compare the server that was actually selected before and after the update. Seeing entries still listed doesn't mean the configuration stayed the same. Use only service details you already have; this site does not provide, sell, or recommend nodes or subscriptions.

2. Global Routing: Compare Proxy, Direct & Config

Check the current mode under Home → Global Routing. The comparison below applies to devices where you can temporarily change the routing mode. If the device is managed, or test traffic must not be sent directly, don't switch to Direct. Test only with public pages that don't require sign-in, then restore the original mode.

Proxy
Routes traffic through the selected server as a proxy-path comparison
Direct
Routes traffic without a proxy server; this is not the same as turning off the connection switch
Config
Selects a policy according to the rules in the current configuration

Diagnosis: Separate Direct and Proxy Paths

If a website loads with the switch off but fails with the switch on in Direct, leave the server parameters unchanged and check DNS settings while the connection is on. The failure can't be attributed to the proxy server alone.

3. DNS: Tell Resolution Failures from Connection Timeouts

First note the URL shown in the browser's final error. The URL you entered may redirect, and a homepage, login page, or image may use a different domain. If the active configuration sets dns-server under [General], check the file currently in use in Config and note its original value. The filename in the list alone doesn't confirm that its changes are active.

Error: Could not resolve host

Cause: This common diagnostic message indicates that the tool couldn't resolve the hostname to an address. It is not specific to a message in the Shadowrocket interface.

Fix: Check the failed hostname for typos, then restore the previously working DNS setting in a copy of the configuration and retest the same URL.

Error: Connection timed out

Cause: The connection wasn't established within the time limit. The server, network path, or destination port may be involved; a timeout alone doesn't prove that DNS is the problem.

Fix: If the diagnostic log shows the destination address, leave DNS unchanged. Compare Proxy and Direct using the same URL, then check the failing path.

4. Rules: Check the Actual Hostname and First Match

Return to Config mode and inspect [Rule] in the active configuration. Follow the rule order from top to bottom and find the first applicable rule. Don't search only for the destination domain: a broader rule may match first, even if the configuration contains the domain rule you expected. The reserved example domain below illustrates rule precedence; it isn't a configuration for everyday browsing.

[Rule]
DOMAIN-SUFFIX,example.com,REJECT
DOMAIN,docs.example.com,DIRECT
FINAL,PROXY
Download Shadowrocket