This guide explains how to import nodes into sing-box and why shared use across a team can affect account environment stability. You’ll learn how to import nodes using a subscription link or local configuration file, and how to troubleshoot common issues such as connection failures, frequent disconnections, and problems caused by multiple people sharing an account.
1. Confirm how your team will use it before importing
sing-box is just a client core. Node stability also depends on the subscription content, network environment, and usage habits. For team use, first clarify whether each person uses a separate device, whether everyone shares the same subscription, and whether users often switch node regions. If multiple people use the same account at once or frequently change their exit location, some websites may flag the account environment as unusual.
- On personal devices, stick to familiar nodes as much as possible and avoid frequently switching regions.
- Avoid having too many team members share the same subscription across multiple devices at once.
- Prefer node subscriptions from reputable sources. This site also curates free nodes for testing.
- Before signing in to an important account, make sure your current exit IP is consistent with your usual usage.
2. Common ways to import nodes into sing-box
The interface varies slightly between sing-box clients on different platforms, but the basic process is the same: get a subscription or configuration file, import it into the client, and then start the proxy. For most users, a subscription link is the easiest option because it can be updated later.
- Open your sing-box GUI client, such as the Android, Windows, or macOS version.
- Go to “Configuration,” “Profiles,” or “Subscriptions,” then select Add.
- Select “Import from URL” and paste the subscription link provided by your VPN service, a free-node page, or your team administrator.
- Give the configuration an easy-to-recognize name, such as “Team Nodes” or “Test Subscription.”
- Save it, then update the subscription and wait for the node list to load.
- Select a node, turn on the proxy, and test the connection in your browser.
If you have a JSON configuration file, choose “Import from File” or paste the configuration content into the client. After importing, avoid changing rule fields unless you know what they do. Most users only need to select a node and turn on the proxy.
3. Improve account environment stability for team use
For team use, the key question isn’t just “Can we connect?” but “Is the connection environment consistent?” For example, if multiple people manage the same overseas account, using a US node today, a Japanese node tomorrow, and a European node the day after could trigger a security check. We recommend setting a default team node and avoiding frequent switches unless the connection fails.
You can also group nodes by purpose: use regular nodes for research and a fixed node for account sign-ins. When testing free nodes, don’t sign in to important accounts right away; first check the IP, latency, and availability. If the client supports rule mode, stick with either the default rules or global proxy mode. Avoid switching between them frequently if you’re unfamiliar with how the rules work.
4. Troubleshooting connection failures and import issues
If no nodes appear after importing, first check whether the subscription link is complete and whether any special characters were cut off. If nodes appear but won’t connect, try switching networks, updating the subscription, or restarting the client. A configuration error usually means the client is outdated or the subscription format is incompatible.
- Subscription update fails: Check whether the link has expired or whether your current network can access the subscription address.
- You can select a node, but webpages won’t load: Try another node, or check that system proxy/VPN permissions are enabled.
- Some team members can connect, but others can’t: Check whether client versions, system times, or network providers differ.
- Accounts repeatedly require verification: Reduce shared use, stick to a fixed sign-in node, and avoid switching countries within a short period.
In short, importing nodes into sing-box is straightforward. The key is to import via subscription, update regularly, and stick to familiar exit locations. For team use, account environment consistency matters more than simply getting a temporary connection.