This guide answers common questions about “how to use Shadowrocket”: how to install the client on an iPhone, import nodes or a subscription, connect, and understand why the IP, DNS, and browser location may not match. Follow the steps below to establish a basic connection, then troubleshoot sites that won’t load or an exit IP that hasn’t changed.
1. Get a node or subscription ready before installing
Shadowrocket is a proxy client. It does not provide usable connections on its own and is not a node service. Check the app name and developer information in the App Store before installing. Availability and pricing depend on your store region. Do not install modified versions or configuration profiles from untrusted sources.
Get a node link, QR code, or subscription URL from your service provider, and make sure it uses a format supported by the client. The free nodes on this site can be used for testing, but their availability may change. Subscription links may contain access credentials, so don’t share them publicly or submit them to unfamiliar conversion websites.
2. Import a subscription and connect
- Open Shadowrocket and tap “+” in the top-right corner of the home screen. If you have a subscription URL, choose the corresponding type, such as “Subscribe,” paste the full URL into the URL field, add a note to help identify it, and save. Labels may vary slightly between versions.
- For a single-node link, copy it and return to the client, then follow the import prompt. Import a QR code using the scan option. After importing, check that fields such as the server and port are present; don’t change them unnecessarily.
- Return to the home screen, update the subscription, and select a node. You can run a connectivity test, but a response does not guarantee that every website will be accessible.
- Set “Global Routing” to “Config” or rule mode, and make sure the configuration comes from a trusted source and its rules have loaded. If no usable rules are available, you can briefly switch to “Proxy” mode to test the connection, then restore your usual mode.
- Turn on the connection switch on the home screen. The first time you connect, follow the iOS prompt to allow a VPN configuration to be added, then test by opening the target website.
A VPN indicator in the system status only means the proxy tunnel is enabled; it does not guarantee that the node is working. Test both a regular website and one that requires a proxy rather than drawing conclusions from a single page.
3. How IP, DNS, and the browser environment are related
Your IP is the network exit address that a website sees. In rule mode, sites that connect directly may still show your local carrier’s IP, while sites routed through the proxy show the node’s exit IP. Before checking, confirm which rule applies to the site you’re using.
DNS translates domain names into addresses. DNS queries and web traffic don’t necessarily take the same route, and seeing a particular DNS provider on a test page does not, by itself, prove there is a leak. Start with DNS settings from a trusted configuration. If a domain won’t load while other connections work, check for resolution errors or a rule mismatch.
The browser environment also includes cookies, signed-in accounts, language, time zone, and location permissions. Changing your exit IP does not automatically clear this information or guarantee that a website will show a different region. Compare results in a private browsing window and check location permissions, but don’t treat private browsing as an anonymity tool.
4. Troubleshoot connection failures in order
- First, turn off the proxy and confirm that Wi-Fi or cellular data is working. Then check whether the subscription updated successfully and whether the node is still active.
- Try another node and compare Wi-Fi with cellular data to distinguish a connection issue from a local network restriction.
- Check the connection log for timeouts, authentication failures, or DNS errors. Check the node status, subscription credentials, and DNS settings as appropriate.
- Temporarily disable other VPNs or network tools that may conflict. If only one website is affected, first check the routing rules, browser cache, and the website’s status.
Change only one setting at a time while troubleshooting, and record the result before moving on. Don’t disable certificate verification to fix connection problems, and don’t trust unfamiliar certificates. Follow the laws in your location and the relevant service terms.