How to Import Nodes in sing-box: Team Configuration and Stability Troubleshooting

This article explains “how to import nodes into sing-box” and why, when multiple people on a team use it, some have stable connections while others experience frequent dropouts. Follow the steps to import a subscription or individual node, organize nodes into groups, and learn how account environments can affect connection stability.

1. Before you import

sing-box is a proxy core. Most users access it through a graphical client, such as SFI, sing-box for Android, NekoBox, Hiddify, or another client that supports the sing-box core. For team use, it’s best to standardize on the same client version first. This helps prevent the same subscription from being parsed differently across members’ devices.

• Have a working node link or subscription link ready. Common protocols include VLESS, VMess, Trojan, and Shadowsocks.
• Make sure your device’s clock is accurate. A time discrepancy can cause TLS handshakes to fail.
• If you’re using this site’s free nodes, copy the subscription address first, then import it into your client to test.
• Within a team, avoid having multiple people frequently switch between the same account and the same exit strategy, as this may trigger rate limits or security checks on the server.

2. Steps to import a subscription into sing-box

1. Open the sing-box graphical client and go to the “Configuration,” “Subscription,” or “Profiles” page.
2. Click “Add Subscription,” “Import from URL,” or “Import from Link.”
3. Paste the subscription link. Give it a name such as “Team Nodes” or “Backup Subscription” so it’s easy to identify later.
4. Save it, then update the subscription and wait for the client to parse the node list.
5. Go to the proxy or routing page and select a node with low latency in a suitable region.
6. Connect, then open a browser and visit a test website to confirm that you can access the internet.

If you have a link for a single node rather than a subscription, select “Import from Clipboard” or “Import from Clipboard.” Copy the complete node link and import it. Make sure you include the prefix, such as vless:// or trojan://, or the client won’t recognize it.

3. Recommended practices for teams

The biggest differences between team and individual use are the number of people and devices involved and the variety of network environments. To reduce the chances of one person being able to connect while another cannot, administrators should provide everyone with the same subscription address and specify the recommended client and update schedule. Team members should avoid changing routing rules on their own, especially settings for DNS, bypassing mainland China, and global proxy mode.

If you need to organize nodes by purpose, create groups such as “Everyday Browsing,” “Backup Lines,” and “Low Latency First.” Avoid having everyone stay on the same node for long periods, as too many connections concentrated on one node can lead to congestion and unexpected disconnections. For important meetings or remote work, prepare a backup node in advance.

4. How account environment stability affects node imports

Importing a node is only the first step. Stability also depends on the account, device, network, and client configuration. When multiple team members share one account, having too many devices online at once, frequently changing IP regions, or reconnecting repeatedly within a short period may trigger restrictions. Symptoms can include successfully importing a node but being unable to connect, or disconnecting just minutes after connecting.

The key to a stable connection is to keep configurations consistent, avoid unusual switching, and update subscriptions promptly. If team members often switch between office Wi-Fi, home broadband, and mobile hotspots, they should disconnect the proxy before changing networks, then reconnect afterward. Some public networks block proxy traffic. If that happens, try another node, switch protocols, or use a mobile network to troubleshoot.

5. Connection troubleshooting checklist

• Subscription update fails: Check whether the link has expired and whether you can open the subscription address in a browser.
• No nodes appear: Confirm that the client supports the protocol, or try a newer version that supports the sing-box core.
• No internet after connecting: Switch between “Rule Mode” and “Global Mode,” and check the DNS settings.
• Only one person has trouble: Have them match the client version, system time, and configuration used by everyone else.
• Everyone has trouble: The subscription has likely expired, the nodes are unavailable, or the network is restricted.

In short, importing nodes into sing-box is straightforward. The key is to use a reliable subscription source, standardize client versions, and have team members follow the same usage rules. When problems arise, first determine whether they’re specific to one person’s device or affect everyone’s nodes, then work through the checks one by one. This makes troubleshooting much more efficient.