This article explains how to import nodes into sing-box and why shared use by a team can affect account environment stability. It’s suited to remote work, small teams accessing shared resources, and scenarios where multiple people use the same subscription. The focus is on importing configurations in the client, organizing nodes into groups, and troubleshooting common issues—not on configuring a self-hosted server.
1. Check the node format before importing
sing-box supports importing configurations from files, subscription links, or configurations generated by third-party panels. Most users receive either a subscription link or a configuration file with a .json extension. For team use, don’t copy individual nodes to each person at random. Use a shared subscription instead so it’s easier to update, replace, and troubleshoot later.
- Subscription link: Usually a URL beginning with https; suitable for keeping everyone’s configuration up to date.
- Local configuration: Usually a JSON file; suitable for use on a specific device.
- Clipboard import: Useful for temporary testing, but not recommended as a long-term solution for a team.
2. Basic steps for importing nodes into sing-box
Interface labels vary slightly between operating systems, but the process is much the same. In a typical graphical client, follow these steps:
- Install the sing-box client or a client that supports the sing-box core, and make sure your system clock is correct.
- Open the client and go to “Configuration,” “Profiles,” or “Subscriptions.”
- Select “Add subscription” or “Import configuration,” then paste the subscription link or select a local JSON file.
- Click Update or Save and wait for the node list to finish loading.
- Choose a node with low latency and a clear name, then enable the proxy.
- Open a browser and visit a test website to confirm that the connection works.
If you’re using the free nodes provided on this site, copy the relevant subscription or configuration first, then import it using the steps above. Free nodes are suitable for testing and temporary use. For formal team collaboration, pay close attention to availability and failover options.
3. Why the import method can affect team account stability
When multiple people use the service, stability depends not only on whether a node connects, but also on the exit IP, region, and how often users switch nodes. For example, if team members frequently switch between nodes in different countries, a business account may flag unusual sign-ins. Likewise, a member who uses a node in one region today and another region tomorrow may be prompted for additional security checks.
Set a few simple rules for your team: keep each business account on a consistent region and node group whenever possible, and don’t let members switch nodes at random. If you need backup nodes, choose one in the same region rather than switching between regions. Admins can name subscriptions by purpose, such as “Work – Hong Kong,” “Research – Japan,” and “Backup – Singapore,” to help prevent mistakes.
4. Recommended settings for team use
- Use a single subscription source: Don’t let everyone save a different configuration version, or some users may keep using expired nodes.
- Enable automatic updates: Set the subscription to update daily or every time the client starts.
- Keep a backup configuration: Switch to it temporarily if the main subscription becomes unavailable.
- Document usage rules: Make it clear within the team which region to use for each account.
- Avoid sharing screenshots of sensitive configuration details: Subscription links may contain account information, so don’t post them in public groups.
5. How to troubleshoot connection failures after importing
If the import succeeds but you can’t access the internet, don’t immediately reinstall the client. Check these items in order: whether the proxy is running, whether the system proxy is enabled, whether the subscription updated successfully, whether latency is shown for the node, and whether your computer’s clock is correct. If only one website won’t open, the issue may be caused by routing rules; temporarily switch to global mode to test.
If only one team member is affected, the cause is likely their local network, firewall, certificate, or client version. If everyone is affected at the same time, the subscription source, node routes, or upstream network is usually at fault. In that case, have the admin handle it centrally. If everyone changes their configuration independently, the issue can become much harder to troubleshoot.
In short, importing nodes into sing-box is straightforward. For team use, the key is to share a consistent subscription, stick to a consistent region, and keep backups clearly organized. This makes connections easier to manage and reduces the risks associated with frequent changes to account environments.