How do you use Shadowrocket? This guide for iPhone and iPad users covers installing the app, importing nodes or subscriptions, connecting, and checking your IP, DNS, and browser environment. It focuses on issues such as “connected but can’t open websites” and “outbound IP hasn’t changed,” and does not cover setting up your own server.
1. What to prepare before installation
Shadowrocket is a proxy client and does not provide working proxy routes automatically. First, obtain a node link, subscription URL, or QR code from a trusted source. You can search for the app in the App Store and verify its name and developer details. Availability and purchase requirements depend on your local App Store; avoid installing modified versions from unknown sources.
A subscription URL usually acts as an access credential, so don’t post screenshots or share it with strangers. If you use free nodes, check their source and expiration date. The free nodes on this site can be used to test connectivity, but availability may vary and is not guaranteed to remain stable.
2. Import nodes and connect
- Copy the complete node link or subscription URL provided by the service. Make sure it doesn’t include spaces, line breaks, or explanatory text.
- Open Shadowrocket and tap the add button in the upper-right corner of the home screen. For a single-node link, try importing it from the clipboard. For a QR code, use the scanner; the exact label may vary by version.
- To import a subscription, choose the subscription type on the add screen, enter the URL, and save it. Then update the subscription. If the list is empty, first check whether the URL has expired and whether it was copied in full.
- Return to the home screen and select a node. You can run a connectivity test first, but treat the result as a reference only—it doesn’t guarantee access to every website.
- For your first setup, choose “Config” or rule-based routing, then turn on the connection switch at the top. When iOS first prompts you to add a VPN configuration, grant permission after confirming the app is from a trusted source.
- Open a browser and visit your target website. Once connected, check your outbound IP rather than relying only on the VPN icon in the status bar.
Rule-based mode doesn’t mean all traffic goes through the proxy: domestic websites may connect directly, while only specified sites use a node. For troubleshooting, temporarily switch to global proxy mode for comparison, then return to your usual routing mode.
3. How IP, DNS, and your browser environment are related
Your IP is the network exit point a website sees. After enabling the proxy, use an IP lookup page to check whether the outbound IP matches your expectations. If the lookup page itself is set to connect directly by your rules, it may still show your local ISP’s IP, so take your routing mode into account.
DNS translates domain names into addresses. If some websites won’t open, the cause may be a failed lookup, cached data, or routing settings. Start with the default DNS settings in a trusted configuration; don’t copy unfamiliar parameters without checking them. Also, a region shown by your browser is not, by itself, evidence of a DNS leak.
Your browser may also retain cookies, login sessions, language settings, and location permissions. Changing your outbound IP does not automatically clear your browser identity information. If a website’s region hasn’t changed, compare results in a private browsing window and check your account’s region and location permissions. Private browsing does not make you anonymous.
4. Troubleshooting connection issues
- Turn off the proxy and confirm that Wi-Fi or mobile data works, then test using a different network.
- Update the subscription and try a different node. If authentication fails, check your credentials and expiration date.
- Temporarily disable other VPNs or network-filtering tools to avoid conflicts.
- If only some websites fail, compare rule-based and global proxy modes and check whether traffic is incorrectly going direct.
- If the issue persists, review the connection logs and share only redacted error details with a trusted support provider.
Don’t install unfamiliar root certificates or share your subscription key while troubleshooting. A proxy connection does not provide complete privacy protection. For sensitive activities, confirm that HTTPS is in use and follow local laws and service terms.