This article explains “how to import nodes into sing-box” and why sharing an account across multiple team members can affect the stability of its login environment. It’s intended for users who already have a subscription link, share link, or local configuration file. Follow the steps to import and enable the configuration, then troubleshoot any issues. This guide does not cover setting up your own server.
1. Check the node source before importing
sing-box supports a range of proxy protocols, though the interface may vary between clients. For team use, it’s best to standardize on a single node source so that differences in configuration versions don’t lead to inconsistent rules, exit nodes, or DNS behavior. Common sources include subscription links, individual node links, and JSON configuration files. We also compile free nodes for testing, which are suitable for temporary use. For long-term team use, however, it’s best to keep a backup connection available.
- Subscription link: Best for distributing across a team and easy to update.
- Individual node link: Useful for a temporary addition, but harder to maintain over time.
- Local configuration file: Suitable for administrators to generate and distribute to team members.
2. General steps for importing nodes into sing-box
Labels may vary by system—for example, SFI, sing-box, sing-box GUI, or a third-party client—but the general process is similar:
- Install and open the sing-box client. The first time you use it, allow it to create a VPN configuration.
- Go to the “Profiles / Config / Subscription” page and click “Add” or “+”.
- For a subscription link, choose “Remote / Remote Configuration,” paste the URL, and enter a name such as “Team-Proxy.”
- For a local JSON file, choose “Import / Import from File” and select the configuration file sent by your administrator.
- Save the configuration, then click “Update Subscription” or “Refresh Configuration” and check for errors.
- Return to the home screen, select the configuration you just imported, and start the connection.
After importing, open a browser and test a few commonly used websites, then test the tools your team uses. If some apps can’t connect, the issue is usually not that the node failed to import, but that the routing rules, system proxy, or DNS behavior differs.
3. Why the import method can affect team account stability
The aspect most often overlooked when using a shared team account is “environment consistency.” If team members sign in to the same account from different countries, different carriers, or frequently changing exit IPs, the platform may flag the login environment as unusual. If everyone chooses a different route when importing nodes into sing-box, this can lead to more verification prompts, risk-control warnings, or frequent session expirations.
We recommend that team administrators use a shared subscription and specify recommended nodes in the instructions. For example, use the same region for routine sign-ins and switch to a backup only when there’s an issue. Don’t let team members jump frequently between multiple free nodes, especially when using work accounts, collaboration platforms, or ad dashboards. The priority isn’t “the fastest speed,” but a stable exit IP, a consistent region, and documented switches.
4. Troubleshooting connection failures and import errors
If you can’t connect after importing, check the following in order:
- Make sure there are no extra spaces in the subscription link and that it opens or downloads correctly in a browser.
- Check whether the client is out of date. Older versions may not support certain VLESS, Reality, or newer rule formats.
- Test a different network—for example, switch from Wi-Fi to a mobile hotspot—to rule out local network restrictions.
- Check the log for keywords: “timeout” usually indicates a network issue or an unavailable node; “parse error” usually indicates an invalid configuration format.
- Close other VPN or proxy software to avoid port and routing conflicts.
If only one team member is affected, first check their device permissions, system time, antivirus software, and whether they imported an outdated configuration. If all team members are affected at once, the subscription source, node, or remote configuration update is usually the cause.
5. Recommendations for team use
Administrators can maintain a “Configuration Guide” that includes the subscription address, recommended and backup routes, update schedule, and how to report issues. Team members can then import the configuration by following the guide without modifying the rules themselves. This reduces training overhead and improves account environment stability. If you use free nodes, keep them for backup or testing; avoid frequent switching when using important accounts.