This guide explains how team members can import nodes in sing-box, how to standardize subscription configurations, and why the import method can affect account environment stability. It’s suited to scenarios such as remote work, small-team access to resources, and collaborative testing. It does not cover setting up your own server.
1. Prepare a node or subscription link
sing-box is a proxy core. Many popular clients provide a graphical interface for it, such as sing-box for Windows, SFI, SFA, and NekoBox. Before importing, prepare one of the following:
- A subscription link from a proxy provider or service provider;
- A link for a single node, such as VLESS, VMess, Trojan, or Shadowsocks;
- A JSON configuration file, usually prepared and distributed by an administrator;
- Node details from the available nodes on our free nodes page, which can be used for temporary connection testing.
For team use, a subscription link or shared configuration file is recommended. Members won’t need to copy nodes one by one, and updates are easier to manage.
2. General steps for importing nodes into sing-box
The interface varies slightly between clients, but the process is generally the same. Here’s an example using a typical graphical client:
- Install a client: Windows users should choose one that supports the sing-box core. Android users can use SFA, while iOS users can use a tool that supports sing-box configurations.
- Open the “Configuration,” “Profiles,” or “Subscription” page and select Add.
- For a subscription link, select “Import from URL,” paste the link, save it, and then select Update.
- For a single-node link, copy the entire link and select “Import from clipboard” in the client.
- For a JSON file, select “Import from file” and locate the configuration file provided by the administrator.
- After importing, select a node, enable system proxy or VPN mode, and visit a test website.
After a successful import, first test by visiting a familiar website in your browser, then test the systems your team commonly uses. Don’t rely solely on the client’s “Connected” status.
3. How the import method affects stability for teams
When several team members share a setup, stability depends not only on node quality but also on configuration consistency. If everyone copies nodes from different sources, protocol mismatches, expired nodes, and inconsistent rules can cause problems—some members may be able to connect while others experience frequent drops.
A more reliable approach is for an administrator to maintain a subscription or configuration that members import and update regularly. This keeps routing rules, DNS policies, and backup node lists consistent, and makes it easier to determine whether a problem lies with the node, the client, or the local network.
Also, avoid having every team member use the same egress IP for high-frequency activity over an extended period. On login-related or risk-sensitive websites, frequently switching countries or sharing a single node among multiple people can affect account stability. Consider grouping connections by purpose: one group for work, another for research, and another for testing.
4. Troubleshooting checklist
- Subscription won’t update: Check that the link is complete and hasn’t expired. If needed, try again on a different network.
- Imported node doesn’t work: Confirm that the client supports the protocol and transport method.
- Connected, but websites won’t load: Check that system proxy/VPN mode is enabled, or switch to global mode for testing.
- Works for some team members but not others: Compare client versions, system times, DNS settings, and configuration update times.
- Frequent disconnections: Switch to a backup node and avoid having too many people use a single free node at once.
For occasional research, you can start by testing a free node. For long-term team use, establish a standard import procedure and update schedule.
5. Recommended practices for teams
Administrators can create a one-page guide covering the subscription link, client version, update frequency, and common issues. After importing, members should avoid making ad hoc changes to the underlying JSON. If a problem occurs, they should first share a screenshot of the client log and the name of the current node. This reduces the time spent coordinating and improves account environment stability and overall connection success rates.