How to Import Nodes into sing-box: Team Setup & Stability Troubleshooting Guide

This article explains how to “import nodes into sing-box” and why, when used by a shared team, some people can connect while others have unstable connections. You can follow the steps below to import a subscription or a single node into the sing-box client on Windows, macOS, Android, or iOS, and understand how account environment, node allocation, and configuration updates affect stability.

1. Confirm the node type before importing

sing-box supports common protocols such as VLESS, VMess, Trojan, and Shadowsocks, but the interface varies slightly between clients. For team use, it is recommended to standardize on one import method first: prioritize using a subscription link, and only use individual nodes as a secondary option. The advantage of a subscription is that when nodes change later, you only need to refresh it instead of having everyone repeatedly replace nodes manually.

• If what you received is a long address starting with https, it is usually a subscription link.
• If it starts with vless://, vmess://, trojan://, or ss://, it is usually a single node.
• If it is a JSON configuration file, you need to confirm whether the client supports importing the configuration directly.

This site organizes some free node information suitable for testing connectivity; if it is for team office use, it is recommended to prepare multiple backup nodes as well, to avoid everyone crowding onto the same route.

2. General steps for importing a subscription into sing-box

1. Open the sing-box client and go to the “Profiles,” “Configuration,” or “Subscription” page.
2. Click Add and choose “Import from URL” or a similar option.
3. Paste the subscription link. For the name, you can use something like “Team Backup” or “Office Route” to make it easier to distinguish.
4. After saving, click Update Subscription and wait for the client to fetch the configuration.
5. Return to the home page, select the configuration you just imported, and start the connection.
6. Open a browser and visit commonly used websites to confirm they load normally.

If you are importing a single node, you would usually choose “Import from Clipboard” or “Scan QR Code.” After importing, it is still recommended to give it a clear name, such as “Hong Kong – Backup 1” or “Singapore – Meeting,” so that when team members report problems, it is easier to identify the source.

3. The relationship between team use and account environment stability

Many people assume that as long as a node can be imported, the connection will definitely be stable. In reality, in team scenarios, stability is also related to the usage environment. For example, if multiple people use the same account, the same subscription, and the same exit node at the same time, it may trigger server-side restrictions or cause congestion; different members being on different ISPs can also lead to significant differences in how the same node performs.

It is recommended that teams adopt the following practices: do not have everyone stick to the same node for long periods; group routes by region or purpose, for example using different lines for research, meetings, and development testing; refresh subscriptions regularly to avoid continuing to use invalid nodes in old configurations; if one member disconnects frequently, first have them switch networks or nodes rather than immediately reinstalling the client.

4. How to troubleshoot import failures and unstable connections

• Subscription cannot be updated: check whether the link is complete, whether extra spaces were copied, and whether the subscription address can be opened in a browser.
• Configuration error is displayed: the client version may be too old, so upgrade the sing-box client before importing again.
• It connects but webpages will not open: switch the proxy mode, try global mode or rule mode, and check whether the system proxy is enabled.
• Only one person cannot use it: have them switch networks, for example from company Wi-Fi to a mobile hotspot for testing.
• The whole team disconnects at the same time: first determine whether the node itself has failed, then refresh the subscription or switch to a backup node.

When troubleshooting, do not repeatedly delete all configurations, as this can easily remove working nodes as well. A safer approach is to keep the original configuration and create a new test configuration for comparison. If free nodes are being used, fluctuations are common, so it is recommended to prepare multiple sources and update them promptly.

5. Recommendations for team use

Administrators can put the subscription link, client version, and recommended node names into a one-page internal guide, so members only need to follow the steps. When issues occur, have members report four pieces of information: system, network, node name, and a screenshot of the error. This makes it much easier than just saying “it won’t connect” to determine whether the issue is with importing, the node itself, or the local network. Overall, importing nodes into sing-box is not complicated; the key is standardized configuration, distributed usage, and regular updates so the team environment remains more stable.