This article explains how to import nodes into sing-box and why, when multiple team members use the same set of nodes, some may have a stable connection while others experience frequent disconnects. From an everyday user’s perspective, we’ll cover how to import a single node or a subscription, how to share it with team members, and which account environment settings can affect connection stability.
1. Check the node type before importing
sing-box supports several proxy protocols, including VLESS, VMess, Trojan, Shadowsocks, and Hysteria2. You don’t need to understand the underlying configuration—just check whether you have a “node link” or a “subscription link.” Node links are typically long addresses starting with vless:// or trojan://. Subscription links usually start with https:// and contain multiple nodes, making them convenient for teams to update centrally.
If you’re using the free nodes provided on this site, we recommend copying the subscription link first. If you’re just testing a particular route, you can import a single node instead. In a team setting, subscriptions are easier to keep consistent than manually copying individual nodes, and they make it simpler to replace routes later.
2. Basic steps for importing nodes into sing-box
- Install a client: For Windows, Android, iOS, or macOS, choose a client that supports the sing-box core, such as the official sing-box client or a tool compatible with sing-box configurations.
- Open the client and look for “Configuration,” “Profiles,” “Subscription,” or “Import.” The exact label varies by client.
- Import a subscription: Select “Import from URL,” paste the subscription address, save it, then click Update.
- Import a single node: Copy a node link such as vless:// or trojan://, then select “Import from clipboard” or “Import manually.”
- Select a node, start the connection, and then open a browser to test a website you regularly use.
If no nodes appear after importing, first check that the link is complete, and make sure you haven’t copied any extra spaces, Chinese punctuation, or line breaks. Some clients also require you to click “Update subscription” manually after importing.
3. Why account environments affect stability when teams use sing-box
Many people assume that a node just needs to connect to be good enough. But when several team members are using it, stability also depends on their account environments. This includes system time, network egress, DNS, client version, subscription update method, and whether multiple people are using the same node at once.
- Incorrect system time: TLS-based nodes may fail certificate validation, leaving the connection stuck or causing a timeout.
- Different client versions: Someone using an older core may not support newer protocol parameters, so the same subscription may behave differently across devices.
- Sharing a single node: This can cause congestion or trigger security controls. Teams should have multiple nodes available to switch between.
- Different network environments: Office Wi-Fi, campus networks, and mobile networks may impose different restrictions on UDP, ports, and DNS, leading to different connection results.
For this reason, teams should avoid having everyone change the configuration as they see fit. A more reliable approach is to have one person manage the subscription and share the link with everyone, while members simply update the subscription and choose an available node.
4. Quick troubleshooting steps for connection failures
If importing succeeds but you can’t connect, troubleshoot in this order: try another node, then switch networks; check that your phone or computer is set to sync its time automatically; close any other VPN or proxy apps; update the client; and, as a last resort, delete the configuration and import the subscription again. If only one person is having trouble, the cause is more likely to be device permissions, network restrictions, or an outdated client.
Your team can establish a simple rule: whenever the subscription changes, test it on two or three devices using different networks before asking everyone to update. This reduces the communication overhead of figuring out why it works for some people but not others. Overall, importing nodes into sing-box is straightforward. The key is to standardize the subscription, client version, and troubleshooting steps to make connection stability much more predictable.