This article addresses two questions: how to import nodes into sing-box, and why import methods, node groups, and update habits can affect connection stability when a team shares the same accounts or subscription. It’s intended for everyday users who have received free nodes, an airport subscription, or a company-provided configuration link.
1. Check the node type before importing
sing-box supports multiple protocols and configuration formats, but the interface may vary slightly between clients. There are three common options: a single node link, a subscription link, or a complete JSON configuration. For most users, a subscription link is the best choice because it makes future node changes and replacements easier. If you’re only testing the free nodes provided on this site, you can also copy and import an individual vless, vmess, trojan, or ss link.
- Single node: Best for temporary testing; you’ll need to replace it manually if it stops working.
- Subscription link: Best for ongoing use, with one-click updates.
- JSON configuration: Best for administrators to distribute centrally; beginners should avoid editing it.
2. Basic steps for importing nodes into sing-box
The steps below use a typical sing-box graphical client as an example. Depending on the client, the relevant section might be called Profiles, Configuration, Subscriptions, or Inbound/Outbound Management, but the process is the same.
- Open the sing-box client and go to “Configuration” or “Profiles.”
- Click “Add,” “Import,” or the plus icon in the top-right corner.
- For a subscription, select “Import from URL” and paste the subscription address. For a single node, select “Import from Clipboard.”
- Name the configuration—for example, “Team Subscription – Office” or “freevpn test node”—so it’s easy to identify.
- Save it, then click “Update Subscription” and wait for the node list to refresh.
- Return to the home screen, select a low-latency, working node, and enable the proxy.
After importing, visit a search engine or an IP lookup site to confirm that the connection is working, then open the apps you need. Avoid enabling multiple VPN or proxy tools at once, as they can conflict over routing.
3. Why import methods affect stability for teams
When several people share a setup, stability depends not only on the nodes themselves but also on each person’s configuration. Common problems include someone copying an expired node, someone else not updating the subscription for a long time, or personal test settings being mixed into the team configuration. As a result, some people can connect while others can’t. To avoid this, teams should use a shared subscription link and agree on an update schedule.
Recommended approach: Have an administrator maintain a standard subscription or configuration file, while members only import and update it. Members should avoid changing rules or deleting groups. If you need separate office, test, and backup connections, label them in the configuration names to prevent selecting the wrong one. Free nodes are best used as backups or for testing, since their availability can change over time.
4. Connection troubleshooting checklist
- Click “Update Subscription” first to make sure the node hasn’t expired.
- Test 2–3 different nodes to rule out a problem with a single node.
- Check that your system clock is accurate; an incorrect time can cause TLS handshake failures.
- Turn off other VPNs, proxy extensions, or accelerators, then reconnect.
- Test both mobile data and Wi-Fi to see whether the current network is restricting the connection.
- If you’re the only person on your team who can’t connect, delete the configuration and import the subscription again.
If the problem persists, send the administrator the relevant error keywords from the client logs, such as timeout, handshake failed, or dns error. Don’t share the full subscription address or account details publicly, as this could affect everyone in the group.
In summary, importing nodes into sing-box is straightforward; the key is choosing the right import method. For temporary personal use, you can import a single node. For team use, a shared subscription, regular updates, and minimal configuration changes are a better fit. This helps reduce connection failures caused by inconsistent setups and makes troubleshooting more efficient.