This article explains “how to import nodes into sing-box” and why shared use within a team can lead to unstable connections, frequent disconnections, and account issues. Follow the steps below to import nodes, then use a few simple guidelines to improve reliability for your team.
1. What to prepare before importing nodes
sing-box is a core tool. Most users access it through a client with a graphical interface, such as a sing-box GUI client for Android, Windows, or macOS. Before importing nodes, make sure you have one of the following:
- Subscription link: Usually an HTTPS URL, suitable for keeping your nodes up to date.
- Individual node link: A share link beginning with vless, vmess, trojan, hysteria2, or a similar protocol name.
- Configuration file: Usually a JSON file, suitable for importing a complete set of rules directly.
If you’re using the free nodes provided by this site, we recommend using a subscription so you can refresh the list later. For internal team distribution, it’s also best to have an administrator maintain a shared subscription link, rather than having team members manually copy different versions.
2. General steps for importing nodes into sing-box
- Open the sing-box client and go to “Configuration,” “Profiles,” or “Subscriptions.” The name varies slightly between clients.
- Click “Add,” “Import,” or the plus icon in the top-right corner.
- For a subscription link, select “Import from URL,” paste the link, and enter a name, such as “Team Subscription.”
- For an individual node, select “Import from Clipboard” or “Add Manually,” paste the node link, and save it.
- For a JSON file, select “Import from File,” locate the configuration file, and confirm.
- After importing, return to the home screen, select the configuration you added, and tap Start or Connect.
Once connected, open a browser and visit a few commonly used websites to test the connection. If your client supports latency testing, test the nodes first and choose one that’s available. Keep in mind that low latency doesn’t necessarily mean a connection will remain stable. For team use, it’s especially important to watch for frequent disconnections.
3. How team use affects account environment stability
Many people assume that importing nodes only determines whether they can connect. In practice, team use can also affect account environment stability. For example, if the same account is accessed from multiple regions or exit IPs within a short period, some platforms may trigger security checks. If team members switch nodes at random, this may also cause unusual activity to appear in business account logs.
For team use, follow these three guidelines: First, assign fixed routes to different types of work—for example, use separate configurations for research, social media management, and development testing. Second, avoid having all team members perform frequent, sustained activity through the same node. Third, try to use a route in the same region before and after signing in to important accounts. Avoid signing in from one country and switching to another region just a few minutes later.
If your team has several members, the administrator can distribute a shared subscription and label the routes as “Daily,” “Backup,” or “Temporary—Not Recommended for Account Logins.” This is easier to control than having everyone find nodes on their own, and makes troubleshooting simpler too.
4. Troubleshooting connection failures after importing
- Refresh the subscription first: If it has expired or a node is offline, the client may still show outdated nodes.
- Check the system time: A significant clock discrepancy may cause the TLS handshake to fail.
- Switch networks: Try switching from Wi-Fi to a mobile hotspot to see whether your local network is imposing restrictions.
- Check the proxy mode: Selecting Global, Rule, or Direct mode incorrectly may result in a connection that appears active but can’t open websites.
- Update the client: Older sing-box clients may not support newer protocols or configuration fields.
If only one node fails, the node itself is probably unavailable. If all nodes fail, check the client’s permissions, firewall, DNS, and system proxy settings. For team use, have one team member test the subscription first, then ask everyone else to update. This helps avoid confusion from multiple people making changes at once.
In short, importing nodes into sing-box is straightforward: prepare a link, import the configuration, select a node, and connect. What matters most for the long-term experience is maintaining the subscription, organizing routes, and using accounts consistently. For teams, a shared configuration and fewer frequent switches are usually more important than simply having more nodes.