This guide explains “how to import nodes into sing-box” and why shared use by a team can affect account environment stability. It’s intended for everyday users who need to import subscriptions, distribute nodes to team members, and reduce frequent disconnections and environment anomalies in Windows, Android, iOS, or macOS clients.
I. Two things to check before importing nodes
sing-box itself is a proxy core, and the interface varies slightly between clients such as SFI, sing-box for Android, NekoBox, and GUI.for.SingBox. There are generally two ways to import nodes: paste a subscription link or import a local JSON configuration file. For team use, it’s best to use a subscription link so nodes can be updated centrally and errors from manual copying can be avoided.
- Make sure the subscription comes from a trusted source and is in a format supported by sing-box, or is a configuration converted from Clash/V2Ray.
- Avoid having multiple people frequently switch regions while sharing the same high-risk account environment.
- Keep a record of currently working nodes so members don’t change locations repeatedly while testing.
II. General steps for importing nodes into sing-box
- Open your sing-box client and go to the “Profiles,” “Configuration,” “Subscriptions,” or “Configuration Files” page.
- Click “Add,” “New Profile,” or the plus sign in the upper-right corner.
- Select “Remote/Remote Subscription” and paste in the node subscription link. For a file, select “Local/Local File” and import the JSON.
- Give the configuration an easily identifiable name, such as “Team-Hong Kong Line” or “Backup Subscription.”
- Save it, then update the subscription and wait for the node list to load.
- Select a node, enable system proxy or VPN mode, then test access in a browser.
If you get free nodes from this site, you’ll usually need to copy the relevant VLESS, V2Ray, or subscription address first, then paste it or convert it depending on whether your client supports direct import. Free nodes are suitable for connectivity tests and temporary use. For long-term team use, it’s especially important to follow consistent rules.
III. How importing nodes relates to team account environment stability
Many people assume that as long as they can connect, everything is fine. But when a team is involved, node selection can directly affect the account environment. For example, if the same business account is used in Japan one day, the United States the next, and Europe the day after, a platform may flag the login environment as unusual. A more reliable approach is to have each member or business use nodes in a consistent region and avoid frequent switching.
We recommend establishing a few simple team guidelines: use the same country or region for the same account whenever possible; don’t use the same line for important accounts and test accounts; after updating a shared subscription, have one person test it before notifying the team to switch. This is more stable than having everyone import nodes at random, and makes troubleshooting easier.
IV. Troubleshooting connection failures and subscriptions that don’t appear
- Subscription update fails: Check that the link is complete, that no spaces were copied, and that your network can access the subscription address.
- Nodes appear but won’t connect: Try another node, or check that the client’s time and the system’s VPN permissions are set correctly.
- You can connect but can’t open webpages: Check whether system proxy/VPN mode is enabled and whether another app has taken over DNS settings.
- Some team members can connect while others can’t: Compare client versions, configuration names, rule modes, and the regions of the selected nodes.
To sum up, importing nodes into sing-box is straightforward. What matters most is the subscription source, client compatibility, and team usage habits. Grouping nodes, sticking to a consistent region, and reducing random switching are usually better for account environment stability than simply pursuing “more nodes.”