This article addresses the question of “how to import nodes into sing-box“: it is suitable for users who have just installed a sing-box client, walks through subscription import and manual node addition step by step, and explains why IP, DNS, and the browser environment can affect access results after connecting.
1. What to prepare before importing nodes
sing-box itself is a proxy core. Most regular users will use a client with a graphical interface, such as SFI, sing-box for Android, nekobox, Hiddify, or another client that supports the sing-box core. Button names may vary slightly between clients, but the overall logic is basically the same: first prepare the nodes or subscription, then import the configuration, and finally enable the proxy.
- Subscription link: usually an https link; after you click update, it will automatically fetch multiple nodes.
- Single node link: commonly in formats such as VLESS, VMess, Trojan, and Shadowsocks.
- Local configuration file: usually a json file, suitable for users who already have a complete configuration.
This site compiles testable free node information. When using it, it is recommended to prioritize the subscription method, since future updates are more convenient. However, the stability of free nodes may fluctuate, so if the connection fails, you may need to switch routes.
2. General steps for importing a subscription into sing-box
- Open the sing-box client and go to the “Configuration,” “Profiles,” or “Subscription” page.
- Click “Add” or the plus sign in the upper right corner, then choose “Import from URL.”
- Paste the subscription link; for the name, you can enter “freevpn” or “backup nodes.”
- Click Save, then run “Update Subscription,” “Update,” or “Sync.”
- Return to the home page, select a node or policy group, and turn on the VPN/proxy switch.
If what you received is a single node link, you can choose “Import from Clipboard” or “Scan QR Code.” After importing, try not to change too many settings at once; keeping the default routing rules makes troubleshooting easier. If the client reports a configuration error, it is usually because the link is incomplete, the protocol is unsupported, or the subscription content is not in a format that sing-box can recognize.
3. How IP, DNS, and the browser environment relate after connecting
Many people successfully import nodes, yet web pages still will not open. The reason is not necessarily that the node is broken. Connection status involves three layers: IP, DNS, and the browser environment.
IP refers to the outbound address seen by websites. After a successful connection, visiting an IP-check website should show the region where the proxy node is located. If it still shows your local ISP IP, that means the system proxy or VPN mode has not taken effect.
DNS is responsible for resolving domain names into IP addresses. If DNS is still going through the local network, pollution, resolution errors, or reset connections may occur. It is recommended to enable built-in DNS, remote DNS, or rule-based DNS in the client. If you are unfamiliar with these settings, use the default recommended configuration first and avoid entering values manually at random.
The browser environment includes cache, cookies, WebRTC, language, time zone, and so on. Some websites use this information together to judge the access environment. When testing, you can use an incognito window, disable conflicting browser proxy extensions, and clear old cache. In particular, if Chrome or Edge has multiple proxy extensions installed, they may compete with sing-box for control of the proxy settings.
4. Troubleshooting checklist when you cannot connect after importing
- Make sure the subscription link can be opened and is not expired, empty, or missing part of the content due to an incomplete copy.
- Switch to other nodes for testing so you do not mistake a single node failure for a client issue.
- Check whether the system time is accurate; an incorrect time can cause TLS handshake failures.
- Turn off other VPNs, accelerators, and proxy extensions to avoid port and routing conflicts.
- Switch between mobile data and Wi-Fi for testing to rule out local network restrictions.
- Check keywords in the logs, such as timeout, dns, handshake, and refused, and then troubleshoot accordingly.
If timeout appears repeatedly in the logs, the node is most likely unreachable or blocked by the network; if the error is DNS-related, check the DNS settings first; if it shows connected but web pages still do not load, focus on the browser proxy, routing rules, and the local firewall.
5. Usage recommendations
For beginners importing nodes into sing-box, it is recommended to start with the combination of “subscription URL import + default rules + VPN mode.” After confirming that access works normally, gradually adjust routing, DNS, and browser privacy settings. This makes problems easiest to pinpoint and also helps avoid making the configuration more and more chaotic. If free nodes are unstable, simply update the subscription or switch nodes in time.