This article explains “how to import nodes into sing-box” and why using it across a team can affect account environment stability. It’s intended for everyday users who need to import the same subscription across multiple computers and phones and reduce disconnections and accidental switching. It does not cover setting up your own server.
1. Check your node source and how you plan to use it
sing-box is a proxy core used by clients such as SFI, sing-box for Android, NekoBox, and Hiddify. There are two common ways to import nodes: copy a link for a single node or import a subscription link. For team use, the subscription method is recommended, since it makes it easier to update nodes and replace ones that stop working.
- Single node: suitable for temporary testing; simple to configure but harder to maintain.
- Subscription link: suitable for teams that need a shared setup; clients can fetch updates automatically.
- Configuration file: suitable for advanced users; manual JSON editing is not recommended for everyday teams.
If you’re using the free nodes provided on this site, it’s also a good idea to copy the subscription URL first and import it into your client to avoid errors from pasting nodes one by one.
2. General steps for importing nodes into sing-box
- Install a client that supports sing-box. For example, use SFI or NekoBox on Android, or choose a graphical client with a sing-box core on Windows/macOS.
- Open the client and look for “Configuration,” “Subscription,” “Profiles,” or “Import.” The exact labels vary between apps.
- Select “Import from clipboard” or “Add subscription URL,” then paste your node link or subscription link.
- Save it, then tap “Update subscription” and wait for the client to load the node list.
- Choose a node with low latency and a compatible protocol, then connect.
- Open a browser and test a frequently used website. If it doesn’t load, try another node or check your proxy mode.
After importing, avoid changing core settings unnecessarily. Most users only need to check whether the node works, the subscription is up to date, and the system proxy is enabled.
3. How import methods relate to account stability in team settings
For teams sharing a setup, stability depends not only on whether a node connects, but also on the account’s login environment. For example, if the same work account logs in from a Hong Kong IP and then from a US IP a few minutes later, the platform may flag the activity as unusual. Teams should therefore follow consistent rules: use nodes in similar regions for the same business account, and avoid frequent switching between regions.
We recommend setting a few simple team guidelines: assign a fixed group of nodes to each account; don’t have the same team member use different egress locations on multiple devices at the same time; test subscription updates before rolling them out to everyone; and check the current IP region before logging in to important accounts. These steps can help reduce CAPTCHAs, security warnings, and interrupted logins.
4. Troubleshooting connection and import issues
- Empty subscription: Check that you copied the full link, that it contains no spaces, and whether the subscription content opens in a browser.
- Import works, but the connection fails: Try updating the subscription or switching nodes, and check that your device’s clock is correct.
- Web pages won’t load after connecting: Make sure system proxy/TUN mode is enabled and that the browser doesn’t have an incorrect proxy configured separately.
- Some team members can connect while others can’t: Check client versions, network conditions, and whether everyone is using the same configuration.
If a node is only temporarily unavailable, don’t immediately switch through a large number of nodes. First disconnect and reconnect, then update the subscription, and finally try a backup node in the same region. For teams, stability matters more than constantly chasing lower latency.
5. Recommended team practices
Have an administrator manage the subscription URL, while team members handle importing and updating it. Avoid sharing multiple configuration versions in group chats, as this makes troubleshooting harder. Whenever you change the subscription or node rules, record the date, who is affected, and the recommended node names. That way, if an account runs into an issue, you can quickly determine whether it’s caused by the node, the client, or a security check triggered by the account itself.