This article explains “how to import nodes into sing-box” and why sharing nodes among team members can lead to unstable connections and unusual account activity. It’s for users who need to distribute the same set of nodes to colleagues using a mix of computers and phones. Follow the steps to import nodes, switch between them, and troubleshoot issues.
1. Check the node format before importing
sing-box supports multiple proxy protocols, but clients generally offer two ways to import nodes: a subscription link or an individual node link or configuration file. For team use, subscriptions are generally preferable. When an administrator updates the nodes, members can simply refresh the subscription to sync the changes, rather than having each link sent to them again.
- For links using protocols such as vless, vmess, trojan, and hysteria2, make sure your client is up to date.
- For JSON configuration files, verify that the source is trustworthy to avoid overwriting local rules.
- If you’re using the free nodes provided on this site, you can copy a subscription or individual node link and import it for testing.
2. General steps for importing nodes into sing-box
The interface may vary slightly between platforms, but the process is much the same. Here’s an example using a typical graphical client:
- Open the sing-box client and go to “Configuration,” “Profiles,” or “Subscriptions.”
- Click “Add,” “New,” or the plus sign in the upper-right corner, then select Import from URL.
- Paste the subscription link and give the configuration a recognizable name, such as “Team Subscription – Office.”
- Save it, then click “Update Subscription” or “Refresh” and wait for the node list to load.
- Return to the home screen, select a clearly labeled node with low latency, and enable the proxy.
- Open a browser and visit a test site to confirm that external webpages load normally.
If you have an individual node link, select “Import from Clipboard” on the add screen. If the client reports a format error, the link was likely copied incompletely. Try copying the entire line again.
3. How import methods affect stability for teams
Many teams assume that as long as a connection works, that’s enough. But when multiple people are using the service, how nodes are imported and the consistency of account environments can directly affect stability. First, if everyone uses the same node and frequently switches regions, platforms may flag logins as coming from unusual environments. Second, different client rules can lead to inconsistent results: one person may use a global proxy, while another proxies only browser traffic.
We recommend that teams standardize three things: first, use the same subscription so members don’t end up on outdated nodes; second, stick to the same regions for regular use instead of frequently switching between countries; and third, keep the egress environment relatively consistent for important accounts. This can’t guarantee that every platform will avoid flagging unusual activity, but it can reduce the chances of something working one day and triggering an issue the next.
4. What to do if you can’t connect after importing
If the connection fails, try these troubleshooting steps in order:
- Refresh the subscription first: The node may no longer be available. Refresh the subscription, then try a different node.
- Check your system time: A significant clock discrepancy can cause handshakes to fail with some protocols.
- Switch networks: Corporate Wi-Fi or campus networks may restrict proxy connections. Try using your phone’s hotspot.
- Close conflicting software: Running multiple VPN or proxy tools at the same time may cause port conflicts.
- Check the proxy mode: If webpages won’t load, switch from rule mode to global mode to test.
If only one app is inaccessible, the node probably hasn’t failed completely; the routing rules may simply not cover that app’s traffic. When team members report an issue, ask them to include their operating system, client version, selected node name, and a screenshot of the error to make troubleshooting easier.
5. Tips for teams
Don’t share subscription links outside your team, and avoid saving configurations on untrusted devices. For frequently used business accounts, we recommend assigning specific team members and devices, and using relatively consistent nodes. Importing nodes into sing-box is straightforward; the key is to keep subscription updates, node selection, and account environments consistent over time. Following the steps in this article should provide a reliable process from import through everyday use.