This article explains “how to import nodes into sing-box” and why using the same account environment across multiple team members can affect connection stability. It’s for everyday users who need to import VLESS, VMess, Trojan, or Shadowsocks nodes, or a subscription link, into a sing-box client. It’s also useful for small teams looking to standardize their configurations, reduce connection failures, and avoid frequent disconnections.
1. What to prepare before importing
sing-box is a general-purpose proxy core. Many users access it through a graphical client, such as a client for Windows, macOS, or Android that supports the sing-box core. Before importing a node, check what you’ve received: a single node link, a subscription link, or a complete JSON configuration.
- Single node: Common formats include vless://, vmess://, trojan://, and ss://.
- Subscription link: An HTTP or HTTPS address that the client can use to fetch multiple nodes automatically.
- Configuration file: Usually named config.json, containing inbound and outbound settings, routing rules, and more.
If you’re using the free nodes provided on this site, we recommend copying the subscription or individual node link rather than splitting out the parameters manually. This helps prevent errors in the port, UUID, or encryption method.
2. General steps for importing nodes into sing-box
The names of options may vary slightly between clients, but the process is generally the same. Here’s the most common method for everyday users:
- Open a client that supports sing-box and go to the “Configuration,” “Profiles,” or “Subscriptions” page.
- Click “New,” “Import,” or “Add,” then choose an import method.
- For a subscription link, select “Import from URL,” paste the link, save it, and click Update.
- For a single node, choose “Import from Clipboard” or “Add Manually,” then paste the vless:// or other link.
- For a JSON file, select “Import Configuration File” and make sure the file is valid before enabling it.
- Return to the home screen, select a node, enable the proxy, and check whether your browser can access the target website.
After importing, start with a node that has low latency and uses a compatible protocol. Avoid switching between too many nodes too frequently. For team use, it’s best for an administrator to prepare a shared subscription and distribute it to team members.
3. Why account environments affect stability for teams
Many people assume that a successful import means the connection will be stable. In practice, when multiple team members share a setup, consistency across account environments can have a significant impact on connection quality. Common issues include multiple people using the same node at once, inconsistent rules across clients, conflicts between system and browser proxy settings, and team members repeatedly updating to different configuration versions.
We recommend that teams adopt a consistent approach: use the same range of client versions, the same subscription URL, and the same rule mode. For example, don’t mix “Rule” and “Global” modes. For collaborative work, it’s best not to have multiple people share a single node link long-term. Assigning different nodes through the subscription can reduce the likelihood of throttling, disconnections, or authentication errors.
4. How to troubleshoot import failures and connection issues
If a node won’t work after you import it into sing-box, check the following in order:
- Make sure the link is complete, especially the UUID, password, port, and host.
- If the subscription won’t update, open its URL in a browser first to see whether it’s accessible.
- Check that your system time is correct. A significant time difference can cause TLS connection failures.
- Try a different network, such as switching from company Wi-Fi to a mobile hotspot, to rule out local network restrictions.
- Close any other VPN or proxy software to avoid port conflicts and routing issues.
- Look for keywords in the logs, such as timeout, tls, dns, or auth failed, and troubleshoot accordingly.
If only one team member is affected, first check their local proxy settings, DNS, antivirus software, and client version. If all team members are affected, the subscription may have expired, the nodes may be unavailable, or there may be an issue with the upstream network.
5. Practical tip: subscriptions work better than manual setup for teams
Copying a single node is convenient for personal use, but for teams, importing a subscription is easier to maintain. The administrator only needs to update the subscription. Team members can then click “Update Subscription” in their clients to sync the changes without having to reconfigure everything individually.
Finally, keep in mind that free nodes are best suited to temporary testing, learning how to configure the client, or emergency access. Their stability depends on the connection route, number of users, and network environment. If your team needs them for long-term work, establish clear usage guidelines: don’t share sensitive account details, don’t change configurations without a good reason, and check the logs and subscription status first when issues arise. This will make sing-box connections more stable and easier to troubleshoot after importing nodes.