This article explains how to import nodes into sing-box and how import methods, account environments, and connection stability are related when a team shares a configuration. It’s intended for users who already have a node link or subscription URL, or who have copied a configuration from our free nodes page.
1. First, identify the type of node you have
sing-box supports multiple proxy protocols, but import options vary between clients. Common sources include individual node links, subscription links, JSON configuration files, and rule configurations converted from Clash. For team use, we recommend using a subscription link or a shared configuration file. Avoid having everyone copy different nodes manually, as this can make troubleshooting much more difficult later.
- Individual nodes: such as VLESS, VMess, Trojan, or Shadowsocks links.
- Subscription URLs: a single URL that the client can use to update nodes periodically.
- JSON configurations: native sing-box configurations, usually containing nodes, routing, DNS, and other settings.
- Converted configurations: configurations converted from other formats; check that the rules are compatible.
2. General steps for importing nodes into sing-box
The names of sing-box clients may vary across systems, but the general process is the same. Here’s an example using a typical graphical client:
- Install the sing-box client. The first time you open it, allow it to create a VPN or network proxy.
- Go to “Configuration,” “Profiles,” or a similar menu.
- If you have a subscription URL, choose “Import from URL,” paste the link, and save it.
- If you have an individual node link, choose “Import from Clipboard” or “Add Node.”
- If you have a JSON file, choose “Import from Local File,” then check that the configuration is enabled.
- Return to the home screen, select the configuration you just imported, and tap Start or Connect.
- Open a browser and visit a test website to confirm that the proxy is working.
If you’re using free nodes from our site, first copy the link for the relevant protocol or the subscription URL, then import it using the steps above. Free nodes may fluctuate due to high usage, so we recommend keeping several backup nodes available.
3. For teams, the import method can affect stability
Teams often report that “the same node works for some people but not others.” This doesn’t necessarily mean there’s a problem with sing-box itself. In a team environment, stability usually depends on the following factors:
- Whether configurations match: If some people import an old subscription while others import a new one, differences in routing and DNS can lead to different results.
- System proxy permissions: Windows, macOS, Android, and iOS handle VPN permissions and background activity differently.
- Network egress: Company Wi-Fi, home broadband, and mobile hotspots can affect proxy connections differently.
- Frequent refreshes by multiple users: If the server limits the number of connections, some team members may get disconnected.
- Inconsistent node selection: If the whole team uses the same node, congestion can degrade performance.
For team use, it’s best for an administrator to maintain a shared subscription or configuration file. Members only need to import and update it, rather than changing core settings themselves.
4. Quick checks for connection failures
If you can’t connect after importing, check the following in order:
- Confirm that the subscription URL is accessible. If it isn’t, switch networks and try updating again.
- Check that your system clock is correct. An incorrect time can cause TLS handshake failures.
- Try another node to determine whether the issue is with a single node or the client.
- Close other VPNs, accelerators, and proxy extensions to avoid port conflicts.
- Check the logs for messages such as DNS, timeout, or handshake failed.
- On mobile devices, make sure VPN access is allowed and disable battery-saving restrictions on background activity.
If multiple team members fail at the same time, first check whether the subscription has expired, the configuration was changed by mistake, or the network is blocking it. If only one person is affected, focus on local permissions, DNS, system proxy settings, and security software.
5. Tips for team use
To reduce support requests and back-and-forth, assign one person to maintain the configuration and share the subscription URL, update schedule, and backup node instructions. Other members should avoid changing DNS, routing rules, or outbound policies. When an issue comes up, take a screenshot of the client logs and note the current network environment before reporting it to the administrator. This makes sing-box node imports easier to manage and helps determine whether instability is caused by the node, account restrictions, or the local environment.