This article explains how to import nodes into sing-box and why shared use in a team can affect account environment stability. Follow the steps below to install a client and import a subscription or individual node. You’ll also learn the connection practices team members should follow when sharing nodes to reduce frequent disconnections, security checks, and configuration confusion.
1. What to prepare before importing
sing-box is a proxy core. Most users access it through a client with a graphical interface, such as a sing-box client on Android or a client that supports the sing-box core on Windows or macOS. Before importing a node, make sure you have one of the following:
- Subscription link: Usually starts with https:// and is suitable for centrally updating nodes across a team.
- Individual node link: A protocol link such as vless, vmess, trojan, or hysteria2.
- Configuration file: Usually a JSON file, suitable for scenarios where you already have a complete rules configuration.
For a temporary test, you can also copy an available node or subscription from the free nodes page on this site. However, free nodes may vary in stability over time, so teams using them for regular work should have a backup plan.
2. General steps for importing a subscription into sing-box
The interface varies slightly between clients, but the process is generally the same. Here’s an example using a typical graphical client:
- Install a client: Download a client that supports sing-box from a trusted source. After installing it, grant any necessary VPN permissions.
- Open the configuration or subscription page: Look for “Profiles,” “Configuration,” “Subscription Management,” or a similar option.
- Add a subscription: Click “Add,” “Import from URL,” or “Import from Link.”
- Paste the subscription URL: Paste the subscription link provided by your team administrator. You can name it “Team Lines.”
- Update the subscription: After saving, click “Update” or “Refresh” and wait for the node list to appear.
- Select a node and connect: Choose a node with low latency that has been working recently, then enable system proxy or VPN mode.
If you have an individual node link, select “Import from Clipboard” or “Add Node Manually.” For a JSON configuration file, select “Import from File.” After importing, avoid changing rule fields unnecessarily, as this may prevent the configuration from starting.
3. How team usage relates to account environment stability
Many people focus only on whether they can connect, but teams should also consider account environment stability. If multiple people frequently switch between countries and network providers, logging into the same business account may trigger suspicious login alerts, more verification prompts, or dropped sessions.
We recommend that teams follow these guidelines: First, keep the same region and route for each business account where possible. Don’t use the US today, Japan tomorrow, and Singapore the day after. Second, assign different subscriptions or nodes to different groups to avoid crowding a single exit with simultaneous connections. Third, before logging into important accounts, make sure the node is connected and isn’t reconnecting frequently. Fourth, don’t forward subscription links indiscriminately, as misuse can make nodes unavailable.
4. Troubleshooting connection problems after import
- Check whether the link has expired: If the subscription won’t update, first confirm that the link is complete and hasn’t been cut off by a space.
- Test another node: A failure with one node doesn’t necessarily mean there’s a problem with the client. Try other nodes in the same subscription.
- Check the device time: An incorrect device time can cause TLS handshake failures, so enable automatic time settings.
- Close conflicting software: Running other VPN or proxy tools at the same time may cause port or routing conflicts.
- Check the logs: Keywords such as dns, tls, and timeout in the client logs can help identify the issue.
If all nodes fail, try updating the subscription and restarting the client and network. If the problem persists, contact the subscription provider to check the node status. For team use, designate one person to maintain the configuration while everyone else only updates the subscription. This helps prevent inconsistencies caused by everyone making their own changes.
In short, importing nodes into sing-box is straightforward. The key is to choose the right import method, keep the subscription updated, and establish a team habit of using fixed routes, group assignments, and fewer switches. This makes connections easier to manage and helps keep the login environment stable for frequently used accounts.