This article addresses “how to import nodes into sing-box” and why, when used by multiple team members, it can affect the stability of the account environment. It is suitable for users who have already obtained VLESS, VMess, Trojan, or Shadowsocks node links or subscription URLs. Just follow the steps to import them and then test the connection.
1. Confirm the node format before importing
sing-box itself supports multiple protocols, but the import entry points vary slightly between different client wrappers. There are generally two common methods: one is a single node link, such as vless://, vmess://, or trojan://; the other is a subscription URL, usually an https link, which can update multiple nodes at once. For team use, it is recommended to prioritize subscriptions for easier unified updates and to avoid each person manually copying different versions.
- Make sure the node has not expired, and that the link is copied in full without missing any trailing parameters.
- If you are using this site’s free nodes, you can first copy the subscription or single-node link and then import it for testing.
- Try to use configurations from the same source on both mobile and desktop for easier troubleshooting.
2. General steps for importing nodes into sing-box
The interface labels may differ across platforms, but the overall process is basically the same. Below is an example using a common sing-box graphical client:
- Open the sing-box client and go to the “Configuration,” “Profiles,” or “Subscription” page.
- Click “Add,” “+,” or “Import,” and choose to import from the clipboard, a URL, or a file.
- If it is a subscription URL, choose URL import, paste the subscription link, and enter a name such as “Team Subscription.”
- If it is a single node, first copy the full node link, then choose to import from the clipboard.
- After the import is complete, click update subscription and confirm that nodes appear in the list.
- Select a node, switch to “Global,” “Rules,” or “Proxy” mode, and then click Start.
- Open a browser and visit a test website to confirm whether internet access is working properly.
If the client reports a configuration error, it usually does not mean “sing-box doesn’t work,” but rather that the node format, subscription content, or client version is incompatible. In this case, try testing with another node first.
3. The relationship between team use and account environment stability
In team scenarios, the way nodes are imported can affect usage stability. If multiple people casually use different nodes and switch regions frequently, it may cause excessive changes in the IP environment of logged-in accounts and trigger platform risk controls. It is recommended that the team use a unified subscription source and agree on fixed regions or fixed node groups.
For example, when used for work accounts, ad dashboards, or cross-border stores, it is not recommended to switch frequently between the United States, Japan, and Hong Kong. A more reliable approach is to group by business function and assign each member a fixed usage scope. This can reduce issues such as unusual logins, secondary verification, and account lockouts.
4. Connection failure troubleshooting checklist
- Subscription update failed: Check whether the subscription URL can be opened in a browser and whether the network is being blocked.
- No nodes after import: The subscription format may not be recognized by the current client; try updating the client or switching to a different subscription format.
- Connected but webpages won’t open: Switch the proxy mode and check whether the system proxy is enabled.
- Some team members can use it while others cannot: Compare client versions, system time, DNS settings, and node selection.
In summary, importing nodes into sing-box is not complicated: copy the link, add the subscription, update it, select a node, and start the connection. For team use, what matters more is using a unified configuration, reducing random switching, and keeping a reusable troubleshooting process.