This guide addresses the practical question “How do I use Shadowrocket?” It covers installing the app on an iPhone, importing nodes or a subscription, choosing a routing mode, troubleshooting connection failures, and reducing login verification caused by frequent changes to a team’s network egress. It’s suitable for first-time users and team members who need a consistent workflow.
1. What to prepare before installing
Shadowrocket is a proxy client for iOS; it doesn’t come with any usable servers. Search for it in an App Store where it’s available, and verify the app name and developer information against what the store currently displays. Don’t install modified versions from unknown sources or buy or share someone else’s Apple account.
Get a node link, QR code, or subscription URL from a trusted source, and confirm that it’s compatible with the client. Subscription URLs usually contain access credentials. Don’t post them in public groups or share screenshots that show the full URL. The free nodes on this site can be used to learn how to import and test connections, but availability and exit IP addresses may change, so they shouldn’t be relied on as long-term business connections.
2. Import a node and connect for the first time
- Open Shadowrocket. If you have a subscription URL, tap “+” in the top-right corner of the home screen, select Subscription as the type, enter the URL and an identifiable note, then save. Menu names may vary slightly between versions.
- If you have a single node link, copy it, return to the client, and follow the prompts to add it. You can also use the QR code scanner. Before importing, make sure the protocol is supported by your version of the client.
- Return to the home screen and update the subscription. Check that the nodes appear. Teams can use a consistent naming convention, such as “Project – Region – Purpose,” but each person should use an authorized configuration and never forward credentials without permission.
- Select a node and turn on the connection switch. The first time you connect, the app will ask to add a VPN configuration. Allow it after confirming that you initiated the request, then follow the system prompts to verify.
- Open a browser and visit a website that requires the proxy, then test your everyday apps. A successful latency test doesn’t mean every website will work; verify access by visiting the sites you actually need.
3. Which routing mode should you choose?
Options such as Config, Proxy, and Direct are usually available under settings like “Global Routing,” though the exact names depend on the version. For everyday use, start with a trusted configuration that has clear rules so traffic is handled accordingly. To troubleshoot, you can temporarily switch to Proxy mode for comparison, then switch back when you’re done. Direct mode generally bypasses the proxy, so don’t mistake it for a successful proxy connection.
Don’t import unfamiliar configurations that require installing additional certificates or enabling HTTPS decryption. These steps are generally unnecessary for a standard node connection. Teams should not collect members’ passwords or verification codes just to make troubleshooting easier.
4. How does this affect the stability of a team account environment?
Platforms may assess risk based on a combination of factors, including exit IP, device, browser state, and login activity. Frequently switching regions, sharing one account among multiple people, and repeatedly logging in within a short period may all lead to more verification prompts. A successful connection doesn’t mean the account environment is stable or guarantee that you won’t trigger security checks.
Teams should choose a relatively stable connection and region for recurring tasks and avoid switching nodes back and forth mid-task. Use the member permissions provided by the platform instead of sharing the main account. Save your work before changing connections, and note when the change was made if needed for troubleshooting. Don’t use a proxy to bypass a platform’s identity checks or access restrictions.
5. Troubleshoot connection problems in order
First turn off the proxy and make sure your Wi-Fi or cellular connection can access the internet. Then check whether the subscription has been updated, the credentials are still valid, and the system clock is set to sync automatically. If only one node fails, try another node in the same region for comparison. If only certain websites are affected, check the routing rules and DNS settings. Avoid changing multiple settings at once.
Finally, check the client logs for messages such as timeouts, resolution failures, or authentication errors. When asking an administrator for help, share the time, network type, and a redacted screenshot. Hide subscription URLs, passwords, and tokens. If a free connection stops working, update the source or switch to an available connection; repeatedly tapping Connect usually won’t fix the problem.