This guide answers the beginner question “How do I use Shadowrocket?” It covers installing the app on an iPhone, importing a node, and enabling the proxy, and explains how teams can reduce login verification caused by frequent changes to their outbound connection. Shadowrocket is a proxy client and does not include ready-to-use servers. Whether you can connect depends on your nodes, subscription, and local network, and a VPN alone cannot guarantee account stability.
1. What to prepare before installation
Get Shadowrocket from the App Store. Availability and pricing depend on your store region; avoid modified versions from unknown sources. Prepare a node link, subscription URL, or QR code from a trusted provider, and confirm that the service supports Shadowrocket. Subscription URLs often contain access credentials. Don’t post them in public group chats or share screenshots of them. Team members should each use an authorized configuration. Don’t use a shared Apple ID as a deployment method.
2. Import a node and connect
- Open Shadowrocket and tap “+” in the upper-right corner of the home screen. For a single node, choose the appropriate type and enter its details, or use the app’s clipboard import or QR code scanning option. The option names may vary by version.
- If you have a subscription URL, choose a subscription type such as “Subscribe” on the add screen, paste the full link into the URL field, and save it. Return to the home screen and update the subscription to load the node list. Don’t paste the subscription link into the server address field.
- Select a node and run a connectivity test. Treat the results as a guide, and also verify the connection by opening the target website.
- Go to “Global Routing.” For everyday use, select “Config” to route traffic according to the current rules. For troubleshooting, you can briefly switch to “Proxy” to check whether the rules are causing the issue. Routing behavior may differ between configurations.
- Turn on the connection switch on the home screen. When prompted by iOS, allow the VPN configuration to be added, then visit the websites you want to use. When you finish testing, restore your usual routing mode.
Our free nodes can help you learn the import process, but availability and exit locations may change. For team business, first verify that the connection meets your organization’s requirements. Don’t treat a temporary node as a guarantee of a stable long-term environment.
3. How team use affects account environment stability
Platforms may assess risk based on factors such as IP address, device, login location, and activity. A fixed node does not guarantee a fixed exit IP, and it does not guarantee that an account won’t be asked to verify its identity. The exit IP behind the same node may still change, and frequently switching regions may prompt more suspicious-login alerts.
Teams can agree to use fixed devices and a reasonably consistent exit region, and record the time and reason before changing connections. Before important operations, check the current public IP and region. Use the platform’s member invitations, role-based permissions, and two-factor authentication. Whenever possible, give each person their own account instead of sharing passwords. Don’t falsify your environment to evade a platform’s risk controls. If verification is required, follow the official process.
4. Troubleshoot connection issues in order
- Disconnect the proxy first and confirm that Wi-Fi or cellular data can access the internet. Then check whether the subscription has expired and whether it updated successfully.
- Try another node. If all nodes fail, check that the link is complete, make sure your device’s date and time are set automatically, and ask your provider to confirm the service status.
- If you’re connected but websites won’t load, compare routing modes first. If only certain websites fail, check the routing rules and DNS settings. Avoid changing multiple settings at once.
- Temporarily disable other VPNs or network filtering tools and try again. If needed, reconnect to have the system re-establish the tunnel.
When troubleshooting, change one thing at a time and record the result. When submitting feedback, you can include the client version, error message, and network type, but redact sensitive information such as subscription URLs and passwords.