This article explains how to import nodes into sing-box and why shared use within a team can affect account environment stability. It is intended for users who need to use nodes consistently across computers, phones, or office devices. It covers subscription imports, local configuration imports, traffic routing checks, and troubleshooting common connection failures.
1. Confirm how you plan to use sing-box before importing nodes
sing-box is a general-purpose proxy core, and its interface varies slightly across clients. For example, the menu names in graphical clients for Android, Windows, and macOS may differ, but the import process is essentially the same: either import a subscription link or a local JSON configuration file. For team use, subscription links are recommended, as they make it easier to update nodes centrally and reduce errors from manual copying.
- For temporary personal use: import a single node or a local configuration file.
- For team use: use a subscription, with consistent naming and update schedules.
- Node sources: you can use your own subscription or try the free nodes provided on this site for testing. Keep in mind that free node stability depends on how many people are using them.
2. How to import subscription nodes into sing-box
- Open the sing-box client and go to “Profiles,” “Configuration,” or “Subscription Management.”
- Click “New,” “Add,” or “Import,” then choose “URL/Subscription Link.”
- Paste your subscription URL. Use a descriptive name, such as “Team – Office” or “Test Nodes.”
- Save it, then click “Update Subscription” and wait for the client to fetch the node list.
- Return to the main screen, select the configuration you just imported, and click Start or Connect.
- Open a browser and visit a familiar website to confirm that traffic is going through the proxy. If routing modes are available, use rule mode first.
If you have a JSON file, select “Import from File.” After importing it, check that the configuration is enabled. Avoid making arbitrary changes to the JSON, especially to fields such as ports, protocols, and encryption methods. Incorrect edits can easily prevent a connection.
3. Why team use can affect account environment stability
When multiple team members share nodes, the most common concern is not whether they can connect, but whether the account’s login environment changes frequently. For example, if the same business account logs in through a Hong Kong exit today, a US exit tomorrow, and a different region the day after, the platform may flag the environment as unusual. When using sing-box as a team, try to use a fixed node for each purpose.
Group configurations by use case, such as office communication, research, account logins, and temporary testing. For accounts that require long-term logins, avoid frequently switching countries or routes. Team members should also avoid logging into the same account at the same time through different exits. This can help reduce verification prompts, risk-control alerts, and login issues.
4. Troubleshooting connection issues after importing
- Click “Update Subscription” first to make sure the nodes have not gone stale.
- Check that your system clock is accurate, as an incorrect time can affect TLS connections.
- Try a different network, such as switching from Wi-Fi to a mobile hotspot.
- Check the client logs, especially for messages about DNS, timeouts, or TLS handshakes.
- Try another node in the same subscription to determine whether the issue is with a specific node or the client.
- Close other VPN or proxy software to avoid port conflicts or multiple apps taking over traffic.
If none of the nodes work, check whether the subscription URL has expired, the client version is outdated, or the current network is restricting proxy connections. Team administrators can periodically review available configurations and remove inactive nodes to prevent confusion caused by repeated connection attempts.
5. Practical tips
Importing nodes into sing-box is straightforward. The key to team use is having clear rules: use a shared subscription, choose descriptive names, keep accounts on fixed routes, and update configurations regularly. For most users, importing via subscription and then choosing nodes by use case is the easiest approach. If you run into problems, avoid making frequent, random changes. Check the logs and network environment step by step to quickly identify the cause.