Shadowrocket Connection Timeout: Check Latency Tests, Protocol Settings, and System Time

If a server times out or a connection fails, troubleshoot in order: check the latency test, verify protocol settings and port, then check the system clock.

At a glance

When Shadowrocket times out, first determine whether the failure is in the test, the proxy handshake, or the destination website. Then check the address, port, protocol settings, and system clock. This guide assumes you already have your own service provider and subscription. Its troubleshooting approach applies to iPhone, iPad, Mac, Windows, Android, and Linux. Steps refer to Home, Config, and Settings on iPhone and iPad; on other platforms, check the equivalent options. By the end, you’ll be able to document the issue so it can be reproduced, changing one setting at a time.

1. Identify where the timeout occurs

“Server timeout” doesn’t point to just one cause. A test destination may be unreachable, the server port may not respond, protocol authentication may fail, or the destination website may stop responding after the connection is established. First note whether the failure happens in Home’s Connectivity Test or while browsing. Don’t change DNS, protocol settings, and rules all at once just because you see a timeout.

Local network DNS resolution Server port Protocol handshake Destination access

Latency reflects the time taken for a particular test method to reach a particular target. It doesn’t measure available bandwidth or guarantee that every app will work. A successful TCP connection test only shows that a connection can be made to the relevant TCP port. A test that includes a proxy handshake and destination access covers more of the connection path. Before comparing results, keep the test method, target, and network conditions the same.

2. Keep test conditions consistent and try again

First, turn off the proxy connection and confirm that ordinary websites load. If you’re on public Wi-Fi and haven’t signed in, complete the network sign-in first. Then test one server from your existing configuration to avoid an automatic selection policy switching servers between requests. Record the time, network type, server label, and result. Change only one condition at a time.

  1. Check the network

    Temporarily turn off the connection switch in Home and confirm that the device can access the internet directly. If public Wi-Fi has a sign-in page, complete its authentication before returning to Shadowrocket.

  2. Choose a server

    In Home, select the server to check and note its label and protocol. If you’re using a policy group, confirm the specific server selected in Config—not just the group name.

  3. Run the test

    Run Connectivity Test in Home and note the test method. Test the same server three times to distinguish consistent failures from occasional failures or widely varying results.

  4. Switch networks

    Keep the server and settings unchanged. Switch between Wi-Fi and cellular, then test again. On a computer, you can make the same comparison using another network you’re authorized to access.

  5. Check automatic connection

    If the connection turns back on after you switch it off, check Settings → On Demand. Temporarily disable the relevant automatic connection conditions while troubleshooting, then restore them when you’re done.

For example, three failures after roughly the same wait time point to a different line of investigation than one failure out of three. Consistent failures make a persistent issue—such as an unreachable port or an unresponsive target—more likely. For a one-off failure, keep an eye on network fluctuations. Testing three times is just a way to compare results, not a statistical measure of service quality.

3. Check the protocol, address, and port one by one

Open the server’s edit screen from Home and compare its settings with the original details from your service provider. Start with Type, server address, and port, then check authentication and transport settings. Don’t replace a value just because another port is more common. If the server listens on 8443, changing it to 443 won’t fix the connection. TCP and UDP traffic on the same numbered port also use different paths.

Protocol or setting Check first Common misconception
Shadowsocks Address, port, encryption method, password, and any plugin settings required by the server. A reachable port doesn’t mean the password and encryption method match.
VMess / VLESS UUID, transport method, and any configured TLS, Host, path, or other settings. After copying the UUID, check the transport settings too. Host and the TLS server name serve different purposes.
Trojan Password, port, TLS server name, and server certificate. Using an IP address to connect doesn’t mean the certificate was issued for that IP.
Hysteria2 Authentication details, TLS settings, any obfuscation required by the server, and UDP reachability. A successful TCP 443 test doesn’t prove that a QUIC connection over UDP 443 will work.
WireGuard Local private key, peer public key, Endpoint, tunnel addresses, and routing ranges. Sending UDP packets doesn’t mean a handshake response was received from the peer.

For connections using TLS, the server address identifies the connection destination, while the server name is used to validate the certificate name. With WebSocket, Host and path also determine how the HTTP request is routed. These values may be the same or different; use the original settings from your existing configuration. Don’t replace every domain field with the server’s IP address.

Bottom line: Test the port using the right transport

If your configuration uses Hysteria2 or WireGuard, a successful TCP port test doesn’t mean the connection is working again. Check the relevant UDP path, then confirm recovery with a protocol handshake and a real access test.

4. Narrow down the cause using the exact log text

Look in the connection logs or diagnostic records provided by the app for an entry matching the time of your test. Error text can vary by system and may include an address, port, or extra prefix. The examples below are common underlying error snippets, not necessarily the exact titles shown in a dialog. Keeping the original text is more useful than simply noting “can’t connect.”

connection timed out

Cause: The connection or read didn’t complete before the timeout. This line alone can’t tell you whether the network dropped the traffic, the server stopped responding, or the destination request stalled.

Fix: Check the destination address and failure stage in the same log entry. Then keep the settings unchanged, switch networks, and test again to see whether the timeout occurs before connecting to the server or after the proxy handshake.

connection refused

Cause: The connection was explicitly refused. Common causes include a port with no service listening on it or a network device actively rejecting the connection.

Fix: Check the address and port, and ask your service provider to confirm the service is running on that port. Simply increasing the timeout won’t resolve the issue.

no such host

Cause: DNS resolution returned no usable result, so the connection didn’t reach protocol authentication.

Fix: First determine whether the failed lookup was for the server domain or the destination website. Then check the spelling, DNS resolution on the current network, and DNS settings in the configuration.

certificate has expired

Cause: The certificate appears expired based on the current validation time. The server certificate may have expired, or the device clock may be wrong.

Fix: Correct the system clock and try again. If the error persists with the correct time, ask your service provider to check the server certificate. Don’t disable certificate validation as a workaround.

If the log explicitly says authentication failed, check the password, UUID, key, and protocol type instead of continuing to change DNS settings. If it reports a certificate name mismatch, check the server name against the names on the certificate. When contacting your service provider, include the error snippet, time, and network type. Redact passwords, full subscription links, private keys, and authentication tokens.

5. Check the system clock and TLS validation

An incorrect system clock can make a certificate appear not yet valid or expired. It may also affect authentication with time-based checks, as used by VMess. After checking the connection settings, verify the device’s date and clock synchronization—not just its time zone. Changing the displayed time zone alone won’t correct an inaccurate system clock.

After correcting the clock, reconnect and check the new logs; don’t judge the result using an earlier error. If the same configuration reports an expired certificate on another device with the correct time, check the server certificate. Don’t bypass certificate validation just to clear the error, as it’s an important part of verifying the server’s identity.

6. If the test passes, check Global Routing and Config

If the server test succeeds but websites won’t load, confirm that their requests are actually using the server you tested. In Home → Global Routing, Proxy, Direct, Config, and Scene handle traffic differently: Proxy applies a global proxy mode, Direct connects directly, Config routes traffic according to the active configuration, and Scene follows the settings for the selected scene.

For comparison, temporarily switch to Proxy, confirm which server is selected, and try the same destination. Then restore the original mode. If Proxy works but Config doesn’t, check the active file in Config, rule order, and policy selection before considering rebuilding the server. The examples below illustrate rule syntax; don’t replace your configuration with them without accounting for its existing policies:

DOMAIN-SUFFIX,example.com,DIRECT
IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
GEOIP,CN,DIRECT
FINAL,PROXY

A domain may resolve to both IPv4 and IPv6 addresses. If only some requests fail, check which address family the failed connection actually used instead of disabling IPv6 for the whole device. Also distinguish between a server domain that won’t resolve and a destination website that won’t resolve: the first prevents the proxy connection from being established, while the second may affect only certain websites.

7. Common questions and retesting after recovery

Why do websites still time out when latency is low?

First check which method Connectivity Test uses, then test the same website. Low latency doesn’t mean there’s enough bandwidth or that the destination is reachable. In Home → Global Routing, check the current mode and verify which policy Config actually matched.

It works on cellular. Do I still need to change the settings?

Keep the original settings for now. Compare DNS resolution and the protocol handshake on both networks, paying particular attention to UDP. If only one network fails, changing a correct password or UUID could introduce a new problem.

What should I do if everything times out after a subscription update?

In Home, confirm that the selected server is still listed, then compare its updated address, port, and Type. A successful subscription update only means the list was downloaded and parsed; it doesn’t mean every server in it passed a connectivity test. Keep your previously working configuration for comparison.

Should I delete and reinstall the app?

Not yet. Save the current Config and any useful troubleshooting records, then check the network, settings, clock, and rules. Reinstalling won’t fix a server port that isn’t listening or an expired certificate, and you could lose local settings that would help identify the problem.

After the connection works again, restore Global Routing, On Demand, and policy selection to their usual settings. First retest Connectivity Test on the same server, then open the website that previously failed, and finally test again on the original network. Success only in a temporary test mode doesn’t mean your everyday configuration is fixed.

Bottom line: Keep a reproducible record

If the issue persists, record the time, device platform, network, protocol, test method, exact error text, and results on another network. Share these details with your service provider. Change one setting at a time so you can tell what fixed the connection.

Download Shadowrocket