This article addresses how to import nodes into sing-box and why, when used by a multi-person team, the same set of nodes may be stable for some users while others experience frequent disconnects. By following the steps below, you can complete client installation, subscription import, node switching, and reduce connection failures through standardized account environment management.
1. What to prepare before importing nodes
sing-box itself is the core program, and ordinary users usually need to use it together with a graphical client, such as SFA on Android or clients on Windows/macOS that support the sing-box core. For team use, it is recommended to standardize the client version, subscription source, and rule mode first, so that troubleshooting is not made difficult by everyone using different configurations.
- Prepare a working subscription link, or an individual VLESS, VMess, Trojan, or Shadowsocks node link.
- Make sure device time is synchronized automatically, as incorrect time can affect TLS-based connections.
- Team members should not mix in configuration files from unknown sources; prioritize using a unified subscription.
- If testing is needed, you can use the free nodes compiled on this site for temporary connectivity verification, but actual stability depends on your real network conditions.
2. Steps to import subscription nodes into sing-box
Different clients may have slightly different interfaces, but the core process is basically the same. The following uses common graphical clients as examples:
- Open the sing-box client and go to the “Configuration,” “Profiles,” or “Subscriptions” page.
- Click Add, then choose “Import from URL” or “Remote Profile.”
- Paste the subscription link. It is recommended to clearly name it by purpose, for example, “Team – Main Subscription.”
- After saving, click Update Subscription and wait for the client to fetch the node list.
- Return to the home page and select a node or an automatic selection policy group.
- Click Start Connection, then open a browser and visit a test website to confirm that it is working.
If you receive an individual node link, you can choose “Import from Clipboard” or “Import from clipboard.” After importing, it is recommended to test latency first, then set it as the current outbound. In team scenarios, using the subscription method is recommended, because later node changes only require the administrator to update the subscription, and members only need to click refresh.
3. How does account environment affect stability in a team
Many people assume that disconnects are only related to node quality, but in team usage, the account environment can also affect the experience. The so-called account environment mainly includes the number of logged-in devices, concurrent use of the same subscription, network switching across different regions, differences in client versions, and whether the configuration has been modified without authorization.
If multiple people share the same subscription and repeatedly connect within a short period across many devices and different carrier networks, this may trigger server-side restrictions or cause frequent switching of policy groups. It is recommended that the team agree internally that each person uses fixed devices and does not casually share the subscription externally; when working on the move, refresh the subscription before connecting whenever possible; and when problems occur, first record the node name, time, and network type to make troubleshooting easier.
Administrators should also distribute unified configuration instructions, such as whether everyone should use “Rule Mode” or “Global Mode.” For normal office work, Rule Mode is recommended, and Global Mode should only be switched on temporarily when testing certain unavailable overseas services. This not only reduces abnormal traffic, but also lowers the chance of misjudging issues as node failures.
4. Troubleshooting import failures and connection failures
- Subscription cannot be updated: Check whether the link is complete and whether extra spaces were copied; try opening the subscription address in a browser to see whether it is accessible.
- No nodes after import: The client may not support that subscription format; try updating the client or switching to one that supports the sing-box core.
- Connection succeeds but webpages will not open: Switch DNS settings, or change from Rule Mode to Global Mode for testing.
- Only one team member cannot use it: Check local system time, proxy permissions, antivirus blocking, and whether the system proxy is enabled.
- Frequent disconnections: Change nodes, switch networks, and avoid having the same account online on too many devices at the same time.
In summary, importing nodes into sing-box is not complicated. The keys are a reliable subscription source, unified client versions, and clear team usage rules. For team users, stability is not just about which node is fast, but also includes how the account is used, device management, and failure logging. By following the process in this article, you can complete the import more quickly and reduce repeated troubleshooting.