This article addresses the question of “how to import nodes into sing-box“: it is suitable for users who have just installed sing-box or a related graphical client, and explains step by step how to import subscriptions and single nodes, as well as why IP, DNS, and the browser environment still need to be checked after connecting.
1. Prepare the client and node information first
sing-box itself is a proxy core. Ordinary users usually use GUI clients, such as sing-box graphical clients on Windows, macOS, Android, and iOS, or tools that support the sing-box core. Before you begin, make sure you already have available nodes. Common formats include VLESS, VMess, Trojan, and Shadowsocks links, or a subscription URL. This site also compiles free nodes for testing, but the stability of free nodes may vary, so it is recommended to test them yourself after importing.
- Subscription URL: usually an https link containing multiple nodes.
- Single node link: starts with vless://, vmess://, trojan://, ss://, etc.
- Configuration file: some clients support importing JSON configuration files.
2. Steps to import a subscription into sing-box
- Open the sing-box client and go to the “Configuration,” “Subscription,” or “Profiles” page.
- Click “Add,” “+,” or “New Profile,” then choose “Import from URL.”
- Paste the subscription URL, and optionally name it “Free Nodes” or “Backup Subscription.”
- After saving, click “Update Subscription” or “Update” and wait for the node list to finish loading.
- Return to the home page and select a node with lower latency in the node/proxy group.
- Enable system proxy or VPN mode, then open a browser to test web pages.
If the client reports a format error, first confirm that the subscription URL is complete and has no leading or trailing spaces. If the update returns empty, the subscription may have expired, the network may be unable to access the subscription source, or the client may not be compatible with the subscription format.
3. Manually import a single node
If you only have a single node link, you can choose “Import from Clipboard” in the client. After copying the node link, click import, and the client will automatically parse information such as the protocol, server, port, UUID, and encryption method. Ordinary users are not advised to manually modify these fields unless the party providing the node explicitly instructs you to do so.
After importing, do not add too many nodes at once. It is recommended to test them one by one. If a node shows a timeout, switch to another node. If they all fail, then check whether the client permissions, network environment, and local system time are correct.
4. What is the relationship between IP, DNS, and the browser environment
A successful node connection does not mean every environment setting is correct. You can open an IP lookup website to confirm whether the outbound IP has changed, then use a DNS leak test page to check whether the DNS resolver is still your local ISP. If the IP has changed but DNS still exposes your local location, you may need to enable options related to FakeIP, remote DNS, or DNS leak prevention in the client. The exact option names vary by client.
The browser environment can also affect the results. For example, browser cache, WebRTC, system proxy not being fully applied, or conflicts with proxy extensions may all cause abnormal location results. When testing, it is recommended to use an incognito window, disable other proxy extensions, and confirm that the client is in global mode, rule mode, or VPN mode, rather than merely having imported nodes without actually enabling the proxy.
5. Quick troubleshooting for connection failures
- Subscription update failed: switch networks and try again, and check whether the link has expired.
- Node latency is -1: the node may be unavailable or blocked by the local network.
- Connected but web pages will not open: check whether system proxy/VPN permissions are enabled.
- Some websites will not open: switch between rule mode and global mode for testing.
- Frequent disconnections: change nodes and avoid running multiple proxy applications at the same time.
Summary: the core of importing nodes into sing-box is to first confirm the source of the nodes, then import them using a subscription URL or the clipboard, and finally check the IP, DNS, and browser environment. Only then can you determine whether the problem lies with the node, the client, or your local network settings.