This article explains how to import nodes into sing-box for teams with multiple users, how to use subscriptions to manage configurations centrally, and why the same set of nodes may have different levels of stability across accounts or device environments. It’s intended for everyday users who already have node links or a subscription URL, or who have copied a configuration from our free nodes page.
1. Check the node format before importing
sing-box supports multiple proxy protocols, but the import process varies slightly between client interfaces. Common sources include individual share links, subscription links, and complete JSON configuration files. For teams, we recommend using a subscription link whenever possible. When the maintainer updates the nodes, team members can simply refresh the subscription instead of manually replacing the configuration on each device.
- Individual node links: Common formats include vless://, vmess://, and trojan://.
- Subscription URLs: Usually an https link that the client can update periodically.
- JSON configurations: Suitable for advanced users; team members should avoid making ad hoc changes.
2. General steps for importing nodes into sing-box
The names of menus may vary by operating system, but the overall process is much the same. The following steps use a common sing-box graphical client as an example:
- Install and open the sing-box client. The first time you use it, allow it to create a VPN or proxy connection.
- Go to the “Profiles / Configuration / Subscription” page and click “Add.”
- For a subscription, select “Remote Profile” and paste the subscription link. For an individual node, select “Import from Clipboard.”
- Save the configuration, then click “Update” or “Download” and make sure no errors appear.
- Return to the home screen, select the configuration you just imported, and start the connection.
- Test access in a browser. If you can’t connect, first try another node from the same subscription.
For team use, we don’t recommend that everyone import and mix nodes from multiple sources. It’s best for an administrator to maintain a single subscription, with each member using that as their only configuration source. This helps prevent rule conflicts.
3. How account and device environments affect connection stability
Many people assume an unstable connection is always caused by the node. In team settings, however, account, device, and network environments can also play a role. For example, the same subscription may perform differently on office Wi-Fi, home broadband, and mobile data. Frequent switching between locations and devices may also trigger security checks or temporary restrictions on some accounts.
To improve stability, we recommend the following practices for your team:
- One configuration per person: Don’t have multiple people share an exported client configuration. This can cause conflicts with device identifiers, caches, and rules.
- Keep usage consistent: Each team member should stick to a regular device and network where possible, and avoid frequently switching between regions.
- Refresh subscriptions regularly: If a node stops working, update the subscription first, then decide whether to switch nodes.
- Choose nodes based on intended use: Office work, research, and video streaming may call for different nodes. Avoid having everyone use the same line.
4. Troubleshoot connection failures in order
If you can’t connect after importing, don’t keep reinstalling the client. Instead, check the following in order: First, make sure there are no extra spaces in the subscription URL and that it updates successfully. Second, check that your system clock is correct; an incorrect time can cause a TLS handshake to fail. Third, try a different network, such as switching from Wi-Fi to a mobile hotspot. Fourth, disable any other VPN or proxy software to avoid port conflicts. Fifth, check the logs for keywords such as DNS, timeout, or certificate.
If you can import free nodes from our site but the connection is unstable, first try refreshing the subscription, switching nodes, or changing networks. Free nodes are suitable for temporary testing and learning how to configure the client, but shouldn’t be your team’s only long-term option. When using sing-box as a team, the key isn’t to “import as many nodes as possible,” but to keep configuration sources clear, establish consistent usage practices, and troubleshoot problems systematically.