This guide answers the beginner question “How do I use Shadowrocket?” It covers installing the client on an iPhone, importing nodes, and enabling the connection, and explains how IP, DNS, and browser settings can affect what you see when browsing. Following the steps in order can help avoid confusion when a node appears connected but websites won’t load, or when your apparent location doesn’t match the node’s exit location.
1. What to prepare before installing
Shadowrocket is a proxy client for iOS. It does not include usable nodes, and buying the app does not automatically give you internet access. Check the app name and developer details in the App Store. Availability depends on the store region associated with your account. Do not install configuration profiles from unknown sources or purported cracked versions.
Prepare a compatible node link, QR code, or subscription URL. Node links and subscription URLs may contain access credentials, so do not share them publicly. If you use the free nodes on this site, also check when they were last updated and which clients they support. Free resources may become unavailable.
2. Import nodes and connect
- Open Shadowrocket. After copying a single node link, you can import it using the clipboard prompt, or scan a node QR code using the app’s scanner.
- If you have a subscription URL, tap the add option, select Subscribe, paste the URL, and save. Wording may vary between versions, so follow the app’s interface.
- Update the subscription and confirm that nodes appear in the list. If you see a format error, check that the link is complete and that its source explicitly supports Shadowrocket. Do not use a webpage URL as a subscription URL.
- Select a node. For an initial test, temporarily set “Global Routing” to “Proxy” to reduce interference from split-routing rules. After testing, switch back to a rules-based mode such as “Config” if needed.
- Turn on the connection switch on the home screen. The first time, follow the system prompt to allow adding a VPN configuration. After verifying your device, open a browser and test a website.
The VPN indicator only means that the system tunnel is enabled; it does not guarantee that the node can access the internet. Test two different websites, and don’t judge whether the connection works based on a single latency test.
3. How IP, DNS, and your browser are related
Your IP usually refers to the exit address that a website sees. When traffic passes through a node, websites will generally see the node’s exit address. If your routing mode is set to direct connection, they may see your local network’s exit address instead. When checking your IP, also confirm your routing mode, selected node, and that the test page is actually going through the proxy.
DNS translates domain names into addresses. A failed lookup may prevent a webpage from loading, but seeing a particular DNS provider on a test page does not, by itself, prove that a leak has occurred. Keep the default DNS settings from a trusted configuration, and avoid copying parameters from unknown sources. If only some domains have problems, check the DNS and split-routing rules in your configuration.
Your browser also stores cookies, login sessions, and site permissions. Changing your proxy IP does not automatically clear browser data or change your account’s region. If a webpage still shows your old region, try reopening it in a private tab and check its location permissions. Do not grant precise location access just to change what the page displays.
4. Troubleshoot connection failures in order
- First, turn off the proxy and confirm that you can access the internet over Wi-Fi or cellular data.
- Update your subscription, then try another node. A connection timeout may be caused by an unavailable node or network restrictions.
- Temporarily disable other VPNs or network-filtering tools to avoid conflicts.
- If “Proxy” mode works but rules-based mode does not, check your split-routing configuration. If only one browser is affected, check its cache and site permissions.
If the connection still doesn’t work, note your system version, client version, and error message, then contact your node provider. Before sending a report, redact your subscription URL, password, and UUID. Follow the laws in your location and the rules of the service you use.