This article addresses how to “import nodes into sing-box” and why shared use by multiple team members can affect account environment stability. It is suitable for scenarios such as corporate foreign trade, remote collaboration, and small team testing, with a focus on client import, subscription updates, grouped usage, and troubleshooting connection failures, without involving self-hosted server configuration.
1. What to Prepare Before Importing
sing-box itself is a general-purpose proxy core. Ordinary users typically use it through graphical clients, such as sing-box GUI, SFI, or clients compatible with sing-box configurations on Windows, macOS, and Android. You first need to prepare a source for your nodes: a single share link, a subscription link, or a JSON configuration file. This site also compiles free nodes, which are suitable for temporary connectivity testing, but for long-term team use, it is recommended to prepare a stable subscription to avoid frequent environment changes.
- Single node: commonly provided as links such as vless, vmess, trojan, hysteria2, and so on.
- Subscription link: imports multiple nodes at once and allows one-click updates later.
- Configuration file: usually a sing-box JSON file, suitable for users who already have organized routing rules.
2. General Steps for Importing Nodes into sing-box
Button names may vary slightly across different clients, but the process is basically the same. Before importing, make sure your system time is correct and that your network is not already occupied by another proxy, otherwise you may encounter a situation where the connection appears normal but webpages cannot be opened.
- Open the sing-box client and go to the “Profiles,” “Configuration,” or “Subscription” page.
- Select “Add,” “Import,” “Import from Clipboard,” or “Import from URL.”
- If it is a node link, first copy the full link, then choose import from clipboard; if it is a subscription, paste the subscription URL.
- After saving, click “Update Subscription” or “Fetch Configuration” and wait for the node list to appear.
- Select an available node in the node, outbound, or policy group section, then click to start the proxy.
- Open a browser and visit a test website to confirm that the IP has changed before logging into your business account.
If the client supports “Rule Mode” and “Global Mode,” it is generally recommended to use Rule Mode for everyday use, so that only websites requiring a proxy go through the node, while domestic websites connect directly for a more stable experience.
3. How Team Usage Relates to Account Stability
When multiple team members use sing-box, the key issue is not just whether it can connect, but also whether the exit IP, region, and device environment change too frequently. Many platforms assess risk based on login region, IP reputation, and switching frequency. If you use a US node today, switch to Europe tomorrow, and then to Asia in the afternoon, the same account may trigger verification or risk controls.
It is recommended that teams assign fixed nodes by purpose. For example, a business account should use nodes from the same region and the same subscription group over the long term; multiple people should not log into the same account simultaneously from different regions; and you should especially avoid frequently switching back and forth between free nodes. Free nodes can be used to test whether sing-box is configured correctly, but the environment for formal accounts should keep the exit region consistent as much as possible.
4. What to Check If It Won’t Connect After Importing
- No nodes in the subscription: check whether the link is complete and whether it needs to be opened in a browser to confirm it is accessible.
- Node shows failure: try another node in the same group, or click update subscription.
- It connects but webpages will not open: check whether the system proxy is enabled and whether browser proxy extensions are conflicting.
- Only some websites will not open: switch between rule mode and global mode for testing, and confirm whether the rules are matching correctly.
- No network on mobile: disable battery-saving restrictions and allow the client to run in the background.
Finally, it is best for the team to standardize the client version, subscription address, and usage rules internally, and to record the node region corresponding to each account. This not only makes troubleshooting easier, but also helps reduce account environment instability caused by frequent node changes.