This article addresses the most common questions ordinary users have: how to import nodes into sing-box, how to connect after importing, and why the same node can be affected by IP, DNS, and browser environment. It is suitable for users who have just installed a sing-box client and want to import this site’s free nodes or their own subscription links.
1. What to prepare before importing nodes
sing-box itself is a core engine, and many users actually use clients with graphical interfaces, such as sing-box GUI, SFI, NekoBox, and others on Windows, Android, or iOS. Different clients have slightly different interfaces, but the import logic is basically the same: either import a subscription link or import a single node sharing link.
- Make sure the client is installed and allowed to create VPN or proxy connections.
- Prepare the node link: common formats include vless://, vmess://, trojan://, or it may be a subscription URL.
- If you are using this site’s free nodes, copy the full link and do not miss the trailing parameters.
- On mobile, it is recommended to disable battery-saving restrictions first to avoid background disconnections.
2. General steps for importing nodes into sing-box
- Open the sing-box client and go to the “Configuration,” “Profiles,” “Subscriptions,” or “Nodes” page.
- Select “Import from Clipboard,” “Add Subscription,” or “Import from URL.” If it is a single node, usually choose import from clipboard; if it is a group of nodes, choose a subscription link.
- Paste the node link or subscription address, and give it an easy-to-recognize name, such as “freevpn-x today’s node.”
- Click save, update, or download configuration, and wait for the client to finish parsing.
- Return to the main screen, select the node or policy group you just imported, then click start/connect.
- After connecting, open a browser and visit an IP lookup website to confirm whether the outbound IP has changed.
If the import fails, first check whether the link is complete, especially the node name after # and the parameters after ?—do not delete them manually. Some clients do not support certain special sharing formats, so you can try importing them into a client that supports conversion first, then exporting them as a sing-box-recognizable configuration.
3. What is the relationship between IP, DNS, and browser environment
Many people think that once a node is connected, it is definitely safe, but in fact you also need to see whether the IP, DNS, and browser environment are consistent. IP is the outbound address seen by websites, and after a successful connection it will usually change to the region where the node is located; DNS is responsible for domain name resolution, and if DNS still goes through the local ISP, DNS leaks or access issues may occur; the browser environment includes language, time zone, WebRTC, cache, and login status.
After connecting to a node, it is recommended to do three things: first, check whether the outbound IP has changed; second, check whether DNS is shown as the proxy route or a trusted public DNS; third, test in the browser’s incognito window to avoid old cookies and cache causing websites to continue identifying the original environment. If you need a more stable environment, you can disable browser WebRTC leaks or use a separate browser profile.
4. Troubleshooting connection failures and import issues
- Subscription update failed: switch networks and try again, and confirm that the subscription address has not expired or been copied incompletely.
- The node can be imported but cannot connect: switch to other nodes in the same subscription, or check whether the system time is accurate.
- Connected but webpages will not open: try switching DNS and closing other VPN/proxy software to avoid port conflicts.
- Only the browser does not work: check whether the browser is set to a fixed proxy, or whether an extension is overriding the system proxy.
- IP has not changed: confirm that the client is in “Global” mode or the correct rule mode, rather than proxying only some applications.
Overall, importing nodes into sing-box is not complicated. The key is to distinguish between the two methods, “subscription” and “single node,” and to check whether the IP, DNS, and browser environment match after connecting. When problems arise, troubleshoot in the order of link integrity, client support, DNS, and proxy mode, and you can usually identify the cause.