This article explains “how to import nodes into sing-box” and why shared use within a team can affect account environment stability. Follow the steps below to import free nodes or a subscription link into sing-box. With consistent configuration, grouped testing, and troubleshooting, you can reduce cases where “it works for some colleagues but not others.”
1. What to prepare before importing nodes
sing-box is a core engine, and many users pair it with a graphical client, such as SFI, sing-box for Windows, Nekoray, or Hiddify. For team use, it’s best to standardize client versions and system environments first to avoid differences in rules, DNS, or TUN mode caused by using different software.
- Check the node format: common formats include VLESS, VMess, Trojan, and Shadowsocks, or a subscription link.
- Decide how you’ll add nodes: import one node manually or import multiple nodes from a subscription.
- Check permissions: in a company or team network environment, you may need administrator privileges to enable TUN/VPN mode.
- Prepare a backup node: this site collects information about free nodes for temporary testing, but actual connection stability may vary.
2. Common ways to import nodes into sing-box
Button names vary slightly between clients, but the process is generally the same: copy a node link or subscription URL, paste it into the client, and update the configuration.
- Open the sing-box graphical client and go to “Configuration,” “Profiles,” or “Subscriptions.”
- If you have a node link, select “Import from Clipboard.”
- If you have a subscription URL, select “Add Subscription,” paste the URL, and enter a recognizable name, such as “Team Backup Subscription.”
- Click to update the subscription, then wait for the node list to refresh.
- Select a node and click Start, Connect, or Set as Current Outbound.
- Open a browser and visit a commonly used website to test the connection. Switch nodes if needed.
If the client supports configuration file imports, you can also import a JSON configuration. However, manual editing of many fields isn’t recommended for most users, especially DNS, routing rules, and outbound tags. Mistakes can make troubleshooting difficult.
3. How importing nodes affects account environment stability for teams
When multiple team members share an internet access setup, stability depends not only on the node itself, but also on the exit IP, switching frequency, DNS, and proxy rules. Frequently switching regions or protocols may cause some platforms to detect changes in the account environment, leading to login verification, risk-control alerts, or access issues.
Teams should follow three principles: First, use the same regional node consistently for each business account. Second, avoid switching back and forth between nodes in multiple countries within a short period. Third, have team members use the same subscription and rules to avoid discrepancies caused by everyone configuring their own client.
If you’re just researching or accessing developer documentation, the impact is usually minor. But for collaboration tools, advertising platforms, social media accounts, or e-commerce accounts, it’s especially important to keep the exit environment relatively consistent. After importing nodes into sing-box, give frequently used nodes clear names, such as “Research—Hong Kong” and “Backup—Singapore,” to avoid connecting to the wrong one.
4. Connection troubleshooting checklist
- Subscription won’t update: Check that the URL is complete and accessible over your network, or try again using a different network.
- Node times out: Test another node; free nodes may stop working at any time.
- Websites won’t load after connecting: Try turning the proxy off and back on, and check whether the system proxy or TUN mode is working.
- Only some websites have issues: Check the rule mode and, if necessary, temporarily switch to Global mode for testing.
- Team members get different results: Compare client versions, system times, DNS settings, and whether IPv6 is enabled.
Finally, we recommend keeping a simple team log with the subscription name, usual region, associated account, time of any issue, and how it was resolved. This makes it easier to diagnose future problems without starting from scratch and to determine whether the cause is a node failure, a client configuration issue, or a change in the account environment.