This article explains “how to import nodes into sing-box” and why sharing a subscription across a team can affect account environment stability. It’s intended for users who want to use sing-box consistently across computers and phones. It focuses on importing nodes, updating subscriptions, organizing groups, and troubleshooting connection failures, and does not cover self-hosted server configuration.
1. What to prepare before importing nodes
sing-box is a proxy core. Common clients include graphical sing-box clients for Windows, macOS, Android, and iOS, as well as tools based on sing-box. Before importing nodes, first check what information you have: a single node link, a subscription link, or a complete JSON configuration file. For team use, a subscription link is generally recommended, as it makes updates easier and reduces errors caused by members copying links manually.
- Single node: Usually starts with vless://, vmess://, trojan://, or a similar prefix.
- Subscription link: An HTTPS URL that the client can use to periodically retrieve a list of nodes.
- Configuration file: Usually named config.json and containing the complete configuration, including inbound and outbound settings and rules.
If you’re using the free nodes provided on this site, copy the subscription or node link first, then import it using the steps below. Free node availability may change, so we recommend keeping several backup routes available.
2. General steps for importing nodes into sing-box
- Install a client: Install a client that supports sing-box on your device. When you open it for the first time, grant the required VPN or network permissions.
- Open the configuration page: Look for an option labeled “Profiles,” “Configuration,” “Subscription,” or “Import.” The wording varies slightly between clients.
- Choose an import method: For a subscription link, select “Import from URL”; for config.json, select “Import from file”; for a single node, select “Import from clipboard.”
- Paste the link and save: Give the configuration a clear name, such as “Team – Shared Subscription” or “Backup – Free Nodes.”
- Update the subscription: Click Update or Refresh and confirm that the node list appears correctly.
- Select a node and connect: Start with a node that has low latency and a clear name, then enable system proxy or VPN mode.
After importing, we recommend opening a browser and testing a few commonly used websites. If they load but some apps do not, the cause is often the routing mode, system proxy permissions, or DNS settings—not necessarily an inactive node.
3. How team use relates to account environment stability
For teams using sing-box, stability depends on more than whether the nodes connect. It also depends on who is using them, where they are connecting from, and how often they switch. If the same account is used to log in from different countries and IP addresses within a short period, some platforms may flag the activity, resulting in CAPTCHA challenges, login restrictions, or identity verification requests.
We recommend organizing nodes by purpose: use a relatively stable route for work accounts, and free nodes for temporary lookups or testing. Avoid switching the same business account between multiple regions within a few minutes. For backends, email, and social media accounts that need to stay logged in over time, try to keep the same region, same client, and same rules to reduce unusual changes in the account environment.
4. Troubleshooting connection failures and import issues
- Subscription update fails: Check that the link is complete, whether it needs to be opened in a browser for verification first, and whether your network can access the subscription URL.
- No nodes appear after importing: The client may not support the subscription format. Try another sing-box-compatible client or use a converted configuration.
- It shows as connected, but webpages won’t load: Check whether system proxy/VPN mode is enabled, and try switching to global mode as a test.
- Some team members can connect, but others can’t: Check client versions, system permissions, time settings, and DNS. Where possible, use a consistent configuration template across the team.
- Frequent disconnections: Try another node, and avoid having all team members rely on the same free route at once.
In summary, importing nodes into sing-box is straightforward once you know whether you have a node link, a subscription, or a configuration file. For team use, prioritize shared subscriptions, consistent naming, and stable routes, and avoid frequent cross-region logins to the same account. This makes maintenance easier and reduces the risk of problems caused by unusual account environments.