This article addresses the question “how to import nodes into sing-box” and also explains why, after importing, you still need to pay attention to IP, DNS, and the browser environment. It is suitable for ordinary users who have just installed a sing-box client and obtained free nodes or a subscription link but do not know how to use them.
1. Confirm the node format before importing
sing-box itself is the core program, and the interfaces of common clients on different platforms vary slightly. For example, Android, Windows, and macOS may use different graphical clients. Before importing nodes, first confirm what kind of content you have received:
- Subscription link: usually a URL beginning with https, which the client can use to automatically fetch multiple nodes.
- A single node link: such as links beginning with vless, vmess, trojan, hysteria2, and so on.
- JSON configuration: a complete sing-box configuration file, suitable for direct import or replacing the existing configuration.
If you obtained free nodes on this site, it is recommended to prioritize using the subscription link, since later updates will be more convenient; if you only have a single node link, you can also add it manually.
2. Steps to import subscription nodes into sing-box
- Open the sing-box client and go to the “Configuration,” “Profiles,” or “Subscriptions” page; the name may differ depending on the client.
- Click “Add,” “New Configuration,” or “Add Profile.”
- Select “Import from URL,” “Remote Profile,” or “Subscription Link.”
- Paste the subscription address and give it an easily recognizable name, such as “freevpn-x free nodes.”
- After saving, click “Update Subscription” or “Update” and wait for the client to fetch the nodes.
- Return to the main screen, select a node or policy group, and click to start the connection.
If the client says the format is not supported, the subscription content may not be in a format that sing-box can recognize. You can try using a client that supports subscription conversion, or choose a configuration link specifically for sing-box.
3. How to manually import a single node
If what you received is a single vless, trojan, or vmess link, look in the client for the “Import from clipboard” function. The usual process is: first copy the node link, then open the client to import it, and confirm whether fields such as the address, port, UUID, transport method, and TLS are automatically recognized.
When adding manually, do not change parameters casually, especially fields such as UUID, ServerName, Reality Public Key, and Short ID. Entering even one of them incorrectly may cause the connection to fail. If no node appears after importing, the client version is usually too old or the protocol is incompatible; it is recommended to update the client and try again.
4. What IP, DNS, and the browser environment have to do with things after importing
Successfully importing a node does not mean the browsing environment is necessarily normal. After connecting, it is recommended to check three things: first, visit an IP lookup website to see whether the outbound IP has changed to the node’s location; second, check whether DNS is still going through your local ISP—if DNS leakage occurs, you can enable the built-in DNS or proxy DNS in the client; third, the browser environment may retain cache, cookies, and WebRTC information, causing websites to make abnormal judgments.
A simple way to handle this is: enable sing-box’s system proxy or TUN mode; disable WebRTC leakage in the browser or use a private window; after switching nodes, refresh the DNS cache and restart the browser if necessary. For ordinary users, the priority is to ensure the proxy mode is correct, DNS is not direct-connected, and the browser keeps minimal cache, which usually reduces abnormal warnings.
5. Connection failure troubleshooting checklist
- Whether the subscription has been updated, and whether the nodes have expired or been deleted.
- Whether the system time is accurate; TLS/Reality is relatively sensitive to time.
- Whether the correct proxy mode is selected, such as global, rule-based, or TUN.
- Whether the local network restricts relevant ports; you can switch to Wi-Fi or a mobile hotspot for testing.
- Whether the client log shows messages such as timeout, handshake failed, dns error, and so on.
If multiple nodes all fail, first check the client version, network environment, and DNS; if only one specific node fails, it is most likely unavailable, and you can simply switch to another one. The stability of free nodes may fluctuate, so it is recommended to keep multiple available subscriptions as backups.