This article addresses the common question “how to import nodes into sing-box“: whether you have a subscription link, a share link, or a local configuration file, you can import it into a sing-box client by following the steps below, and understand how it relates to IP, DNS, and the browser environment, making it easier to troubleshoot issues such as connection failures or web pages not loading.
1. Confirm the type of node you have before importing
sing-box itself is a proxy core, and many mobile or desktop clients simply use it as their underlying engine. Before importing, first confirm whether your node source supports sing-box. There are three common forms: subscription links, individual node links, and local JSON configuration files. This site also compiles free nodes that can be used for testing, but the stability of free nodes may fluctuate, so they are best used first for learning and temporary connections.
- Subscription link: usually an https address, suitable for updating nodes in bulk.
- Individual node link: such as those starting with vless, vmess, trojan, shadowsocks, etc.
- Configuration file: usually config.json, which requires the client to support direct import.
2. General steps for importing nodes into sing-box
Different clients may use slightly different interface labels, but the process is basically the same. The following uses a common sing-box graphical client as an example:
- Install and open the client, then go to the “Configuration,” “Profile,” or “Subscription” page.
- Click “Add,” “Import,” or the “+” in the upper-right corner.
- If it is a subscription link, choose “Import from URL,” paste the link, and save it.
- If it is a local JSON file, choose “Import from File” and select the configuration file.
- Return to the home page, select the configuration you just imported, and click Start or Connect.
- Open a browser and visit a test website to confirm whether traffic is already going through the proxy.
If no node list appears after importing, first check whether the link was copied completely, whether it has expired, and whether the client supports that subscription format. Some Clash subscriptions cannot be used directly with sing-box and need to be converted to sing-box format before importing.
3. How IP, DNS, and the browser environment are related
Successfully importing a node does not mean all access will work normally. After connecting, the public IP you see will usually change to the node’s exit IP; but if DNS is not handled properly, websites may fail to load, location detection may be inaccurate, or DNS leaks may occur. It is recommended to enable system proxy or TUN mode in the client and use the client’s default DNS settings, and not run multiple proxy tools at the same time.
The browser environment can also affect your judgment. For example, if Chrome has a proxy extension installed, the browser has cached old DNS records, or the system time is inaccurate, you may see a situation where “the client shows connected but web pages won’t open.” When troubleshooting, it is recommended to first disable browser proxy extensions, test in an incognito window, and then visit IP lookup and DNS check pages.
4. Quick troubleshooting checklist for connection failures
- Has the node expired or been deleted: switch to another node for testing.
- Has the subscription been updated: manually click “Update Subscription.”
- Is the local network restricted: switch between Wi-Fi, mobile hotspot, or carrier network.
- Is the client mode correct: ordinary browsers can use the system proxy, while some applications require TUN.
- Is the time accurate: incorrect system time can cause TLS handshake failures.
- Are there conflicts: close other VPNs, accelerators, and proxy extensions before trying again.
In summary, the key to importing nodes into sing-box is “matching formats, valid links, and the correct proxy mode.” Beginners are advised to start by importing via subscription, and only then learn about individual nodes and JSON configurations. If you run into problems, do not keep reinstalling repeatedly; instead, check IP, DNS, and the browser environment one by one, and you can usually identify the cause quickly.