This article addresses the question of “how to import nodes into sing-box” and explains why, after importing, you still need to pay attention to IP, DNS, and the browser environment. It is suitable for users who have just installed sing-box and have obtained free nodes or a subscription link but do not know how to use them.
1. What to prepare before importing nodes
sing-box itself is a proxy core, and on different platforms it is usually used together with a graphical client, such as a sing-box client on Windows, Android, iOS, or macOS. Before importing, first confirm which type of information you have: a single node link, a subscription link, or a JSON configuration file. The free nodes page on this site generally provides copyable nodes or subscription entries; when using them, refer to the content available on the page that day.
- Single node: commonly links such as vless://, vmess://, trojan://, etc.
- Subscription link: an https address that the client can update regularly.
- Configuration file: usually a complete sing-box JSON, suitable for overwrite import.
2. General steps for importing nodes into sing-box
- Open the sing-box client and go to the “Configuration,” “Profiles,” or “Subscription” page. The exact name varies slightly between clients.
- If it is a subscription link, choose “Add Subscription,” paste the URL, save it, then click update or sync.
- If it is a single node, choose “Import from Clipboard” or “Add Node,” then paste the vless, vmess, trojan, or other link.
- If it is a JSON file, choose “Import Configuration File.” Note that importing it may replace the current configuration, so backing up first is recommended.
- Return to the home page, select the node or policy group you just imported, and click to start the connection.
After connecting, do not just check whether the switch is turned on. It is recommended to open a browser and visit an IP lookup website to confirm whether the exit region has changed. If the IP has not changed, it may mean that only the client started, but the system traffic was not properly taken over.
3. How IP, DNS, and the browser environment are related after importing
IP represents the exit address seen by websites, and it usually changes after the node is connected. If your local ISP IP is still shown, first check whether the system proxy, TUN mode, or routing rules are enabled. On computers, many clients require “system proxy” to be turned on, while on mobile phones traffic is often taken over through VPN mode.
DNS is responsible for domain name resolution. If DNS does not go through the proxy, issues may occur such as websites failing to open, abnormal region detection, or resolution to a local CDN. If there are options in the client related to “remote DNS,” “prevent DNS leaks,” or “fake-ip,” ordinary users can first use the client’s default recommended configuration and should not casually delete DNS rules.
The browser environment can also affect the results. Some websites may refer to information such as language, time zone, cookies, account region, and WebRTC. When testing, it is recommended to use an incognito window or clear the target website’s cookies. If you care greatly about privacy, you can disable settings related to WebRTC leaks in the browser.
4. Quick troubleshooting for connection failures
- Subscription update failed: check whether the link is complete and whether it was cut off by a line break; you can copy it again.
- The node can be imported but cannot connect: try another node for testing; free nodes may become unavailable due to line fluctuations.
- The browser cannot open pages but the software shows connected: check whether system proxy or TUN/VPN mode is enabled.
- Some websites cannot be opened: switch the rule mode to global for testing to confirm whether it is a traffic-splitting rule issue.
- IP is normal but DNS is abnormal: restart the client, refresh the DNS cache, or restore the default DNS settings.
In summary, importing nodes into sing-box is not complicated: first distinguish whether you have a node, a subscription, or a configuration file, then import it through the client entry point and start it. What really affects the experience is often the details of system proxy, DNS, leak prevention, and the browser environment. When problems occur, check one by one whether the IP has changed, whether DNS is working normally, and whether the browser still retains an old environment; this usually helps identify the cause.