This guide answers the beginner’s question, “How do I use Shadowrocket?” It covers installing the app on an iPhone, importing nodes, and enabling the proxy, and explains how IP, DNS, and browser settings can affect access. Even if the app shows that you’re connected, test by visiting a website to make sure it’s working—don’t rely on the switch status alone.
1. What to prepare before installing
Shadowrocket is a proxy client for iOS and does not include any usable servers. You’ll need to obtain a node link, QR code, or subscription URL separately. Before installing, verify the app name and developer details in the App Store. Availability and pricing depend on your local store. Don’t install configuration profiles from unknown sources or so-called cracked versions.
Before importing, make sure the node comes from a trusted source and that the link is complete. Free nodes may be unavailable or congested, and free nodes shared on this site should be treated as unverified until tested. Subscription URLs may contain access credentials, so don’t share screenshots or forward them.
2. Import a node and connect
- Copy the node link or subscription URL provided by your service, then open Shadowrocket. Button locations may vary slightly between versions.
- For a single node, try adding it with the “+” button on the home screen or importing it from the clipboard. For a QR code, use the scan option. Subscription URLs are usually added by selecting “Subscribe” on the add screen, pasting the URL, and saving.
- Update the subscription and wait for the node list to appear. If the list is empty, check that the link is complete, the subscription hasn’t expired, and your current network can access the subscription URL.
- Select a node and run a connectivity or latency test. A successful test only confirms that the node is initially reachable; it doesn’t guarantee that every website will open.
- As a starting point for everyday use, select “Config” or a rule-based mode under “Global Routing” or a similar menu. Make sure the configuration comes from a trusted source, then turn on the connection switch on the home screen.
- The first time you connect, follow the iOS prompts to allow the VPN configuration to be added and complete system verification. Then open a browser and test access.
If you’re unsure about options such as TLS or certificate verification, leave them at their defaults. Don’t disable security checks just to get a connection. If your subscription includes configuration instructions, first check that they match your current app version.
3. How IP, DNS, and your browser affect access
Your IP is the network endpoint that websites see. In rule-based mode, some requests go directly to the internet while others use the proxy, so an IP lookup site may show your local endpoint. To check the proxy’s IP, you can temporarily switch to “Proxy” or global proxy mode, then switch back to your usual rules afterward.
DNS translates domain names into IP addresses. A webpage may fail to load because of a DNS resolution problem, or because of an issue with the node or routing. Start by keeping the default DNS settings. Check whether custom DNS, encrypted DNS, or filtering settings from other tools are enabled, and avoid changing multiple options at once.
Your browser also stores cookies, sign-in status, language settings, and location permissions. Changing your IP address does not change your entire browser environment. If a website still shows the same region, compare the result in a private window and check your account’s region and location permissions. Private browsing does not make your activity completely anonymous.
4. What to check when you’re connected but can’t open websites
- Turn off the proxy first and test your regular connection to confirm that your Wi-Fi or cellular network is working.
- Update the subscription, try another node, and test several websites to tell whether the problem is limited to one site or affects the entire connection.
- Temporarily switch to global proxy mode. If access works again, check whether the rules are sending the target website through a direct connection.
- If only domain-name access is affected, check DNS. If the problem occurs only in one browser, check its cache, extensions, and site permissions.
- Pause other VPNs or network-filtering tools and try again to avoid conflicts between configurations.
If the problem persists, note the error message, client version, network type, and test results, then contact your node provider. Before sharing logs, hide subscription URLs, passwords, and other credentials.