This guide explains how to use Shadowrocket (小火箭) and why teams often run into disconnections, subscription confusion, and account security checks. You’ll learn how to install it on an iPhone or iPad, import nodes or subscriptions, and improve connection stability through consistent usage practices.
1. Using Shadowrocket as a team
Often called “小火箭” (Little Rocket), Shadowrocket is a popular iOS proxy client that supports protocols such as V2Ray, VLESS, Trojan, and Shadowsocks. For teams, it’s just the client—the connection’s stability mainly depends on node quality, subscription management, members’ network environments, and usage habits. This site provides free nodes and import guides for testing and temporary use. For ongoing team collaboration, it’s a good idea to have multiple working nodes available so everyone isn’t relying on the same route.
2. Installing Shadowrocket and importing nodes
- Get the Shadowrocket client ready on your iPhone or iPad. The first time you open it, allow it to add a VPN configuration.
- Get a node link or subscription URL. Common formats include vmess://, vless://, trojan://, and ss://, or an https subscription link.
- Open Shadowrocket and tap “+” in the top-right corner. For a single node, select the appropriate type and paste the link. For a subscription, select “Subscribe/订阅,” paste the subscription URL, and save.
- Return to the home screen, pull down or open the subscription page to refresh the node list, then select a node with low latency and a clear name.
- Tap the switch at the top to connect. When prompted for VPN permission, tap Allow. Once connected, open a browser to check that websites load correctly.
If your team shares a subscription, have the administrator share the subscription URL rather than repeatedly posting individual nodes in chat groups. This helps prevent members from importing outdated configurations and ending up with situations where “it works for everyone else but not for me.”
3. How account environment stability relates to Shadowrocket
Many people assume that once Shadowrocket connects, everything is taken care of. In reality, a team’s account environment is also affected by exit IP, region, device, and login frequency. For example, if multiple people share a business account and frequently log in through nodes in different countries, the account may be prompted for a CAPTCHA or two-step verification, or even restricted. A safer approach is to use nodes in a consistent region for the same business use case and avoid switching frequently.
- Use a consistent node for each purpose: For tasks such as research, social media management, or accessing cross-border tools, try not to switch countries every day.
- Avoid having multiple people log in to the same account from different regions at the same time, especially for platforms such as email, social media, and advertising dashboards.
- Notify team members before updating a subscription so no one continues working with an expired node.
- Free nodes are suitable for testing connectivity, but aren’t recommended for long-term logins to important accounts.
4. Troubleshooting connection failures and instability
If Shadowrocket won’t connect, check the following in order: First, confirm the node hasn’t expired and that the subscription updates successfully. Second, switch networks and test both Wi-Fi and cellular data. Third, check that the client recognizes the node’s protocol and that the imported node has a name, address, and port. Fourth, turn the VPN off and back on, and restart your phone if necessary.
If Shadowrocket shows that it’s connected but websites won’t load, try switching the rule mode. Beginners can start with “Global” mode to test the connection, then switch to “Config/Rule” mode. If only some websites won’t load, the issue may be with routing rules or DNS. Updating the configuration file often resolves it. For teams, administrators should specify the recommended mode so members don’t make inconsistent changes to their rules.
5. Tips for team use
The key to using Shadowrocket reliably isn’t complicated settings—it’s consistency: use a shared subscription, organize nodes into clear groups, keep account login regions as consistent as possible, and don’t rely on temporary routes for important business activities. For most users, learning how to import, update, switch, and troubleshoot nodes is enough for the majority of proxy use cases. If you only need temporary access to information, you can test the free nodes provided on this site. For team account management, pay closer attention to environment consistency and clear guidelines for member behavior.