How to Import Nodes in sing-box: Subscriptions, Manual Setup, and the Role of IP, DNS, and Browser Environment

This article answers the question of “how to import nodes into sing-box“: including importing subscription links, manually adding nodes, updating subscriptions, and why you should still pay attention to IP, DNS, and the browser environment after connecting. It is suitable for ordinary users using sing-box for the first time to follow step by step.

1. What you need before importing nodes

sing-box itself is a proxy core, and many users access it through graphical clients, such as sing-box for Android, SFI, NekoBox, Hiddify Next, and so on. Button names may vary slightly between clients, but the overall process is basically the same: install the client, import the configuration, select a node, and start the proxy.

• Prepare a working node link or subscription link. Common formats include vless, vmess, trojan, hysteria2, and others.
• Make sure the time on your phone or computer is accurate, as an incorrect system time may cause TLS connection failures.
• If you are using this site’s free node page, you can copy the subscription address or an individual node link and then import it.

It is recommended to use a subscription link first, because you can update it with one click later; if you only have a single node link, you can also import it manually.

2. Common ways to import nodes into sing-box

The following uses common graphical clients as examples. Menu names may be “Configuration,” “Profile,” “Subscription,” “Import,” and so on.

1. Open the sing-box client and go to the “Configuration” or “Profiles” page.
2. Tap the “+” in the upper-right corner and choose “Import from Clipboard” or “Import Subscription.”
3. If it is a single node, first copy a link such as vless://, vmess://, or trojan://, then choose import from the clipboard.
4. If it is a subscription link, choose “Add Subscription,” paste the URL, and enter an easy-to-recognize name, such as “Free Nodes.”
5. After saving, tap “Update” or “Download Configuration” and wait for the node list to appear.
6. Return to the home page, select a node, and tap start or connect.

If the client supports scanning QR codes, you can also open the QR code on the node page and use “Scan to Import.” If you do not see any nodes after importing, first check whether the link was copied in full, and in particular make sure the trailing parameters were not omitted.

3. How to confirm it is working after import

A successful connection does not necessarily mean all traffic is being proxied as expected. You can open a browser and visit an IP lookup website to check whether the outbound IP has changed, then visit commonly used websites to test whether they open properly. If the IP is still your local ISP’s, the client may not have taken over the system proxy, or your current browser may not be using the system proxy.

DNS also affects the experience. Some connection failures, pages not loading, or unexpected redirects may not mean the node is broken, but rather that DNS resolution is abnormal. Ordinary users can first use the default DNS settings in the client; if problems persist, then try switching to the remote DNS recommended by the client or enabling options related to “prevent DNS leaks.”

The browser environment is equally important. Browser cache, proxy extensions, WebRTC, and old cookies may all cause websites to detect a different environment. When testing, it is recommended to use an incognito window and disable other proxy plugins to avoid running multiple proxy tools at the same time.

4. Troubleshooting checklist for connection failures

• Subscription update failed: check whether your network can access the subscription address; if necessary, switch networks and update again.
• All nodes unavailable: make sure the client version is relatively up to date, as older versions may not support certain new protocol parameters.
• Only the browser does not work: check whether a browser proxy extension is overriding the system proxy.
• It connects but is very slow: switch nodes or networks, and avoid downloading at the same time or letting background activity consume all bandwidth.
• Certificate or handshake error: sync the system time, re-import the node, and confirm the link was not truncated.

Finally, a reminder: free nodes are suitable for temporary testing and learning configuration, and their stability will be affected by routes, the number of users, and the network environment. When problems occur, do not just keep clicking connect repeatedly. Troubleshoot in this order—whether the subscription is normal, whether the node is available, whether the IP has changed, whether DNS is abnormal, and whether the browser is interfering—for better efficiency.