This article explains “how to import nodes into sing-box” and why team use by multiple people can affect account environment stability. You can follow the steps below to import a single node or a subscription link into a sing-box client, and learn how to reduce common issues such as frequent disconnections, invalid nodes, and abnormal logins on the same account.
1. What you need before importing
sing-box itself is a core engine. Common clients such as SFI, sing-box for Android, sing-box GUI, and NekoBox provide graphical interfaces based on it. Before importing nodes, first make sure you have one of the following:
- A single node link: commonly in formats such as vless://, vmess://, trojan://, ss://, etc.
- A subscription link: usually a URL starting with https:// that can update multiple nodes at once.
- A configuration file: generally in JSON format, suitable for directly importing a complete configuration.
If you are using the free nodes provided on this site, it is recommended to copy the subscription or node link directly and not manually modify the parameters, so as to avoid connection failures caused by mismatched protocols, ports, or encryption methods.
2. General steps to import nodes into sing-box
- Open your sing-box client and go to the “Configuration,” “Profiles,” or “Subscriptions” page. The exact name may vary slightly between clients.
- Select “Add,” “Import,” or “New Profile.” If it is a node link, choose to import from the clipboard; if it is a subscription link, choose to add a remote subscription.
- Paste the vless://, trojan://, or https:// subscription address, and give the configuration an easily recognizable name, such as “Team Backup – Hong Kong” or “Daily Subscription.”
- After saving, click update subscription and wait for the client to parse the node list.
- Return to the home page, select a node, and click start or connect. For the first connection, it is recommended to open a browser and visit commonly used websites to test it.
If the client supports “routing mode,” ordinary users are advised to choose system proxy or automatic mode first, and not modify complex rules right away. Team members should ideally use the same instruction document to reduce problems caused by everyone importing in different ways.
3. The relationship between team usage and account environment stability
Many people think importing nodes only affects whether they can connect, but in team scenarios it can also affect the account environment. For example, if multiple people share the same business account and frequently switch between nodes in different countries and from different carriers, the platform may identify this as abnormal login behavior, leading to verification codes, risk controls, or temporary restrictions.
It is recommended that teams follow three rules: first, use fixed regional nodes for fixed purposes, for example recording commonly used routes separately for information lookup, backend management, and social media operations; second, avoid switching back and forth between nodes in multiple countries within a short period of time; third, for important accounts, avoid having multiple people log in simultaneously from completely different regions whenever possible. Stable nodes do not mean a stable account environment; the latter also includes the login device, browser fingerprint, cookies, time zone, and usage habits.
4. How to troubleshoot connection failures after importing
- Make sure no characters were missed when copying the link, especially the parameters at the end of the subscription address.
- Click update subscription. If it shows a parsing failure, the link may be invalid or the network may be unable to access the subscription source.
- Test with another node; do not rely on only one node to determine whether the client is malfunctioning.
- Check whether the system time is accurate, as time discrepancies may cause TLS connection failures.
- Close other proxy software to avoid port conflicts or duplicate proxying.
If none of the nodes can connect, you can try restarting the client, re-importing the subscription, or switching network environments for testing. Team administrators can organize available nodes, recommended regions, and usage precautions into a table, so members can import them according to unified rules, which can significantly reduce the communication cost of “some people can use it while others cannot.”
In summary, importing nodes into sing-box is not complicated. The key is to distinguish between the three sources: single-node links, subscriptions, and configuration files. In team use, it is even more important to focus on standardized import methods and a consistent account environment. This not only makes connection issues easier to troubleshoot, but also reduces the risk of account anomalies.