This article explains how to “import nodes into sing-box” and why, when used by a multi-person team, the same nodes may be stable for some people but disconnect frequently for others. By following the steps below, you can complete client installation, subscription import, and connection testing, while also using a unified approach to reduce connection issues caused by differences in account environments.
1. Confirm the team’s usage environment before importing
sing-box itself is a general-purpose proxy core, and different clients may have slightly different interfaces, such as sing-box GUI clients or compatible clients on Windows, macOS, Android, and iOS. For team use, it is recommended to standardize three things first: client version, subscription source, and system proxy mode. If everyone freely copies individual nodes, troubleshooting later will be very difficult.
- Prefer using a subscription link instead of repeatedly forwarding individual nodes in chat software.
- Members of the same team should use the same client version whenever possible to avoid differences in rule parsing.
- Record each person’s network environment: office Wi-Fi, home broadband, and mobile hotspot may behave differently.
If you are only testing temporarily, you can also use the free nodes compiled by this site for import verification, but the stability of free nodes is affected by the number of online users and line status, so they are not recommended as your only office solution.
2. General steps for importing nodes into sing-box
- Open the sing-box client and go to the “Configuration,” “Profiles,” or “Subscriptions” page; the name may vary depending on the client.
- Select “Add Subscription” or “Import from URL,” then paste in your subscription link.
- Click update subscription and wait for the client to fetch the configuration. If a format error appears, the link may not be in a configuration format supported by sing-box, or it may need to be converted into a compatible subscription.
- Return to the node list and select a node with lower latency and a clear name.
- Enable system proxy or VPN mode, then open a browser to test access.
If what you received is a single share link such as vmess, vless, trojan, or hysteria2, some sing-box clients support direct paste import. If the import fails, it is recommended to use a subscription instead or convert it through a compatible tool. In team scenarios, centrally managing subscriptions is more stable than manually copying nodes, and it also makes it easier to replace unavailable lines later.
3. What does account environment stability have to do with the import method?
Many people think whether a node works depends only on the line, but in team use it is also related to the local environment. For example, colleague A can connect while colleague B fails. Common reasons include inaccurate system time, an old client that does not support a new protocol, antivirus software blocking the local proxy port, the browser still using a direct connection, or the company network restricting UDP or specific ports.
It is recommended that the team administrator prepare a simple guide: which client to use, which subscription to import, whether TUN/VPN mode should be enabled, and whether other proxy software needs to be closed. This makes everyone’s post-import environment more consistent and troubleshooting faster. In particular, do not run multiple proxy clients at the same time, otherwise local port conflicts may cause what looks like “node failure.”
4. Troubleshoot in order when the connection fails
- Update the subscription first: the nodes may have changed, and continuing to connect with the old configuration will fail.
- Test on another network: switch from office Wi-Fi to a mobile hotspot to determine whether the current network is restricted.
- Check the system time: excessive time drift may cause TLS-related connection issues.
- Turn off other proxies/VPNs: prevent Clash, browser extensions, or an old VPN from taking over traffic at the same time.
- Check log keywords: for example, timeout usually indicates a network or line problem, while format error usually indicates a configuration format problem.
If multiple team members report that the same node is failing at the same time, first determine whether there is a subscription or line issue. If only a few people fail, focus on checking client version, local proxy settings, and network environment. Do not frequently delete and reinstall; save logs and screenshots first, as that helps identify the issue faster.
5. Tips for team use
To reduce the communication cost of “it works for me but not for you,” it is recommended to keep one primary subscription and one backup subscription, and remind members to update them regularly. After importing nodes, do not casually modify rules, ports, or DNS options. Ordinary users only need to know how to update subscriptions, switch nodes, and view logs. Once you understand these procedures, importing nodes into sing-box is not complicated. The key is ensuring that team members maintain consistent configuration, consistent updates, and a consistent troubleshooting sequence.