How do you use Shadowrocket? This guide helps iPhone users install the client, import nodes or subscriptions, and check their IP, DNS, and browser status after connecting. If webpages still won’t load with the proxy enabled, follow the troubleshooting steps at the end to avoid repeatedly reinstalling the app.
1. What to prepare before installing
Shadowrocket is a proxy client and does not include usable servers, so you’ll need to obtain node links, QR codes, or a subscription URL separately. Search for Shadowrocket in the App Store and verify that the developer is Shadow Launch Technology Limited. Availability and purchase requirements depend on your App Store region. Don’t install configuration profiles from unknown sources or purported cracked versions.
Node links typically use formats such as ss://, trojan://, or vless://, while subscriptions commonly use HTTPS URLs. Subscription URLs may contain credentials, so don’t share them publicly or expose them in screenshots. If you use free nodes from sites such as freevpn-x.com, check the publication date and protocol details first. Free resources may not always be available.
2. Import a node and connect
- To import a single node, copy the complete link and open Shadowrocket. Follow the prompt to add it from the clipboard. Alternatively, tap “+” in the top-right corner and enter the provided details, or use the scanner to scan a QR code.
- To import a subscription, tap “+” and choose Subscribe under Type. Paste the subscription URL into the URL field, enter a remark, and save. The wording may vary slightly between versions.
- Return to the home screen, update the subscription, and wait for the node list to appear. If it’s empty, check that the URL is complete and hasn’t expired, and that your current network can reach the subscription server.
- Tap a node. Under “Global Routing,” select “Proxy” first to test the connection, then turn on the connection switch at the top. The first time you connect, follow the iOS prompt to allow adding a VPN configuration and complete system verification.
- Open a browser and visit the site you want to access. Once you’ve confirmed the connection works, you can switch back to “Config” mode for rule-based routing. If you don’t know where the rules came from, don’t assume they’ll handle every website correctly.
The VPN icon only indicates that the system tunnel is enabled; it doesn’t guarantee that the node is working. A latency test is no substitute for testing a webpage, so also check that pages load fully.
3. What IP, DNS, and your browser each affect
Your IP is the network exit address that websites see. The page you use to check your exit IP must also go through the proxy. In rule-based routing mode, different websites may use different exit addresses, so seeing your local IP doesn’t necessarily mean there’s a leak.
DNS resolves domain names to addresses. If a webpage won’t load but other apps work, the cause may be DNS, routing rules, or the node. Start with the default settings, and don’t mix and match DNS configurations you find online. If you need to make a change, adjust just one setting at a time, note the original value, and test again.
Your browser also stores cookies, sign-in status, language preferences, and location permissions. Changing your exit IP won’t automatically clear your browser’s identity information or guarantee that a website shows the same region. You can compare results in a Safari Private Browsing window. If location is involved, check the site’s permissions separately; there’s no need to clear all your data.
4. Troubleshoot connection failures in order
- Turn off the proxy and confirm that Wi-Fi or cellular data can connect to the internet normally, then test using a different network.
- Update the subscription, try another node, and check whether the link has expired. Don’t judge solely by the latency reading.
- Temporarily switch to “Proxy” mode to tell whether the problem is with the node or the routing rules, then restore your usual settings after testing.
- Pause other VPNs or network-filtering tools to avoid conflicts. If the problem persists, check the logs for timeout, DNS resolution, or authentication errors.
When asking someone for help, you can share the client version, network type, and redacted error details. Never send subscription tokens, node passwords, or your full configuration.