This article answers common questions about “how to use Shadowrocket”: from installing it on an iPhone and importing nodes to enabling a connection. It also explains why your exit IP, DNS, and browser environment can affect what you can access. If you’re new to the app, follow the steps in order: first confirm that a node connects, then troubleshoot any website issues.
1. What to prepare before installation
Shadowrocket is a proxy client for iOS. The client itself does not provide usable nodes. Check the app name and developer information in the App Store. Availability and purchase requirements are determined by the store listing. Avoid installing configuration profiles from unknown sources or so-called cracked versions.
Prepare a node link supported by the client or a subscription URL from a trusted source. They are different: a node link usually corresponds to a single configuration, while a subscription URL retrieves and updates a set of configurations. If you use free nodes from this site or another source, be aware of expiration dates and privacy risks. Don’t share subscription links publicly.
2. Import a node and connect
- Copy the complete node link provided to you and open Shadowrocket. If prompted to import from the clipboard, check the contents before confirming. If no prompt appears, use the add option on the home screen to import it manually.
- To use a subscription, open the configuration screen, select the subscription type, paste the address into the URL field, and save it. Then update the subscription. Button names may vary slightly by version.
- Return to the home screen, select a node, and run a connectivity test. Treat the result as an initial indication only; it doesn’t mean every website will be accessible.
- If you’re new to the app, start with the rule mode provided by a trusted configuration. If you haven’t set up any rules yet, you can temporarily switch to global proxy mode to test the node, then adjust the settings as needed.
- Turn on the connection switch on the home screen. The first time you connect, you’ll need to allow Shadowrocket to add a VPN configuration. Follow the system prompts to verify it, then open a browser and test the website you want to visit.
Seeing the VPN icon doesn’t guarantee that the node is working; it only means the system has enabled the corresponding network tunnel. Check the actual access results and the client’s connection logs to confirm.
3. How IP, DNS, and your browser are related
Your exit IP is the network address that websites see. In rule mode, different websites may connect directly or through the proxy, so seeing your local IP in a lookup doesn’t necessarily mean the client has failed. When checking, make sure the IP lookup page is routed through the proxy. Don’t rely on the status bar icon alone.
DNS translates domain names into IP addresses. Failed lookups, cache issues, or mismatched settings can all cause a “connected but won’t load” problem. Don’t change DNS settings at random when you’re getting started: keep the settings from a trusted configuration, confirm that the node and routing are working, and then check the error logs for DNS issues.
Your browser also retains cookies, sign-in status, and location permissions. Even if your exit IP changes, a website may still show content for your original region based on your account region, browsing history, or location permissions. Try again in a private window and check your location permissions. Private browsing doesn’t guarantee anonymity or automatically change your exit IP.
4. Troubleshoot connection failures in this order
- Turn off the proxy and confirm that your Wi-Fi or cellular connection can access the internet.
- Update the subscription, check whether it has expired or imported incompletely, then try a different node.
- Temporarily close other VPN apps to avoid network configuration conflicts.
- Temporarily switch to global proxy mode and test again. If access is restored, focus on the original routing rules.
- If the issue only affects one browser, try another browser or a private window. If it still fails, check the connection logs for timeouts or DNS errors.
Change only one setting at a time while troubleshooting so you can identify the cause. If you ask someone for help, you can share your system and client versions along with a screenshot of the error with sensitive details hidden. Don’t reveal your subscription URL, node password, or full configuration.