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

This article explains “how to import nodes into sing-box” and why sharing an account environment across a team can affect its stability. It’s for users who already have a VLESS, VMess, Trojan, or Shadowsocks link, or a subscription URL, and want to import and connect step by step while minimizing frequent disconnections, account security checks, and location changes.

1. Check the node type before importing

sing-box supports multiple proxy protocols, though the interface varies slightly between clients. Most users don’t need to change the server configuration—just confirm that you have one of the following:

• Single node link: Usually starts with vless://, vmess://, trojan://, or ss://.
• Subscription link: An https URL that can automatically fetch multiple nodes.
• JSON configuration file: A complete sing-box configuration, commonly distributed by an administrator.

For team use, we recommend using a subscription link or a shared configuration file. This prevents team members from manually copying different versions of nodes, and makes it easier to update nodes later. Our free nodes page also provides node details that you can copy, which is useful for temporary connectivity tests.

2. Common steps for importing nodes into sing-box

The following steps use a typical graphical client as an example. The labels may vary by platform, but the general process is the same:

1. Install a sing-box client. On Windows, you can choose a management tool with a GUI; on Android, use a client that supports the sing-box core.
2. Open the client and go to “Configuration,” “Profiles,” or “Subscriptions.”
3. For a subscription URL, click “Add Subscription,” paste the URL, save it, and then click “Update.”
4. For a single node, select “Import from Clipboard” or “Add Node,” then paste the vless:// or similar link.
5. For a JSON file, select “Import Local Configuration” and choose the config.json file provided by your administrator.
6. Return to the home page, select the configuration you just imported, and click “Start” or “Connect.”
7. Open a browser and visit a test website to confirm that your IP, location, and network are working as expected.

If the list is empty after importing, the link may be incomplete, the subscription may require you to log in, the network may be unable to reach the subscription source, or your client version may not support the protocol parameters.

3. How team use relates to account environment stability

When several team members use a proxy, the biggest concern isn’t whether they can connect, but whether the outbound environment is stable. For example, if the same business account is used to log in from Japan and then, just a few minutes later, from the United States, the system may flag it as an unusual login. Multiple team members using the same node at the same time may also trigger security checks.

We recommend grouping configurations by purpose: use separate configurations for everyday browsing, research, and account logins. Keep important accounts on a fixed location and node, and avoid switching frequently. Administrators can maintain a shared subscription, while team members simply update it rather than adding nodes from unknown sources. This makes troubleshooting easier and reduces the risks caused by IP changes.

4. Troubleshooting connection failures and instability

• Update the subscription first: If a node has stopped working, update the subscription and select it again.
• Check the system time: An incorrect time can cause TLS handshake failures.
• Switch networks: Company or campus Wi-Fi may restrict some connections. Try testing with a mobile hotspot.
• Try a different transport protocol or node: Choose a node with lower latency and greater stability from among the options in the same location.
• Close other proxy software: Prevent conflicts between Clash, browser proxy extensions, and sing-box.

If only one team member is having trouble, ask them to export the logs for the administrator to review. If everyone is affected, first check whether the subscription has expired, all nodes are down, or DNS is having issues. For team use, we recommend keeping a record of who changed the configuration and when, so you can roll it back if a problem occurs.

In summary, importing nodes into sing-box is straightforward once you know the difference between a single node, a subscription, and a JSON configuration. For personal use, focus on connectivity. For team use, also pay attention to keeping locations consistent, grouping nodes, and using a shared configuration to make your proxy environment more stable and easier to maintain.