This article addresses the question of “how to import nodes into sing-box,” with a focus on scenarios where multiple people or a team share the same account and subscription: how to import nodes correctly, avoid configuration confusion, and improve connection stability through basic checks. Whether you use a sing-box GUI client on Windows, macOS, Android, or iOS, the overall approach is basically the same.
1. Confirm These Things Before Importing Nodes
When a team uses sing-box, the most common problem is not that people do not know how to use the client, but that the node source, subscription link, and account environment are repeatedly modified by multiple people, causing some users to connect successfully while others cannot. Before importing, it is recommended to first confirm the following points:
- Confirm whether what you received is a subscription link or a single node link, such as vless://, vmess://, trojan://, etc.
- Confirm whether the team is consistently using the same subscription address, and do not let everyone casually copy old links.
- Do not post the subscription link publicly in group announcements, forums, or untrusted documents to avoid abuse.
- If you use this site’s free nodes, you can first copy the nodes available that day and then import them for testing, but do not treat free nodes as a long-term stable line for office use.
For a team environment, it is recommended to assign one maintainer to handle subscription updates or the node list, while other members are only responsible for importing and refreshing, to reduce accidental misoperations.
2. Basic Steps for Importing a Subscription into sing-box
The interface labels vary slightly across different clients, but the import logic is usually the same. The following uses common GUI clients as examples:
- Open the sing-box client and go to the “Configuration,” “Profiles,” or “Subscription Management” page.
- Click “Add,” “New Profile,” or “Import.”
- If you received a subscription link, choose “Import from URL” and paste the complete link.
- If you received node text, choose “Import from Clipboard” or “Manual Import.”
- After saving, click “Update Subscription” or “Download Profile.”
- Return to the home page, select the configuration profile you just imported, and click to start the connection.
After importing, it is recommended to first choose “Auto Select” or a lower-latency node to test web access. Team members should not frequently delete configurations and reinstall them; instead, first try refreshing the subscription, switching nodes, and checking the logs.
3. What Does Account Environment Stability Have to Do with the Import Method
“Account environment stability” can be understood as whether the same group of members, the same set of subscriptions, and the same type of client configuration can remain usable over the long term. The way sing-box imports nodes directly affects stability.
If everyone manually copies individual nodes, then when a node becomes invalid, people have to be notified one by one and replacements have to be made one by one, which easily leads to version inconsistencies. It is more strongly recommended to use subscription-based importing. After the maintainer updates it, members only need to click refresh to sync the latest nodes.
In addition, if team members use the same account on too many devices at the same time, or frequently switch between different network environments, this may also trigger server-side restrictions, which can appear as connection timeouts, handshake failures, or some nodes working while others do not. Ordinary users do not need to understand the underlying protocols; they just need to follow the account usage rules and avoid letting the scope of sharing get out of control.
4. How to Troubleshoot Failed Connections After Importing
If sing-box cannot connect after importing nodes, check in the following order:
- First refresh the subscription and confirm that the link has not expired and that no characters were missed when copying it.
- Switch between 2–3 different nodes to test and rule out a temporary issue with a single node.
- Check whether the system time is accurate; incorrect time may cause TLS-related connection failures.
- Turn off other VPN or proxy software to avoid port or routing conflicts.
- Check the client logs, paying special attention to keywords such as timeout, dns, tls, and auth failed.
If the same subscription works normally on other coworkers’ devices, first check the local network, firewall, and client version; if no one can use it, then the subscription or node source most likely needs to be updated.
In summary: in team scenarios, when importing nodes into sing-box, it is recommended to prioritize using subscription links, with unified maintenance, regular refreshing, and minimal manual changes. This not only makes it easier for new members to get started quickly, but also reduces connection failures caused by inconsistent configurations.