This article addresses the common question of “how to import nodes into sing-box” and also explains why, even after importing, you may still run into issues such as an unchanged IP, DNS leaks, or browsers not opening websites. It is suitable for users who are using sing-box for the first time and do not know how to configure it after receiving free nodes or a subscription link.
1. First, confirm what type of node you have
sing-box itself is a proxy core. Common clients include SFI, SFA, SFM, or third-party graphical clients. Before importing, first identify what you have:
- Subscription link: usually starts with https://, and the client can automatically update nodes.
- Single node link: such as vless://, vmess://, trojan://, ss://, etc.
- JSON configuration file: a complete sing-box configuration, suitable for direct import or replacing the existing configuration.
This site also compiles testable free node information, but free nodes tend to be unstable, so it is recommended to prioritize subscription links for easier future updates.
2. General steps for importing nodes into sing-box
- Install a client: on Android, you can use SFA; on iOS, use a client that supports sing-box; on Windows/macOS, choose a sing-box client with a graphical interface.
- Open the client and find the entry labeled “Configuration,” “Profiles,” “Subscription,” or “Import.” The exact name may vary slightly between clients.
- If it is a subscription link, choose “Import from URL,” paste the link, save it, and then click update.
- If it is a single node link, choose “Import from Clipboard” or “Add Manually,” then paste the vless, trojan, or other link.
- If it is a JSON file, choose “Import from File,” then check whether the configuration is enabled after importing.
- Return to the home page, select a node, enable the connection, and then visit an IP lookup website to confirm whether the outbound IP has changed.
If the list is empty after importing, it is most likely due to an incompatible subscription format, an invalid link, or the network being unable to fetch the subscription. You can first copy the link into a browser to test whether it opens, or try a different client.
3. The relationship between IP, DNS, and the browser environment after importing nodes
Many people assume that once a node is connected, the “environment is clean,” but that is not entirely true. IP represents your outbound address. After a successful connection, it will generally change to the region where the node is located; if it does not change, the system proxy may not be taking effect, the mode may be incorrect, or the node may be unusable.
DNS is responsible for domain name resolution. If the proxy only handles traffic while DNS still goes through the local network, a DNS leak may occur, causing websites to detect that you are still on your original network. It is recommended to enable system proxy and TUN/VPN mode in the client, and to use the client’s default remote DNS strategy.
The browser environment includes language, time zone, cache, cookies, WebRTC, and more. For example, your IP may already be overseas, but if the browser language is still Chinese or the account history looks unusual, some websites may still trigger risk controls. Ordinary users do not need to overcomplicate things, but when troubleshooting, you can try using an incognito window, clearing the cache, disabling WebRTC leaks, or switching browsers.
4. Quick troubleshooting for connection failures
- Node timeout: switch to another node, or update the subscription and try again.
- Connected but web pages will not open: check whether global/TUN/VPN mode is enabled.
- Some websites will not open: switch between rule mode and global mode for comparison testing.
- Subscription update failed: confirm that the subscription link has not expired and that your current network can access the link.
- IP unchanged: check whether system proxy permissions and VPN permissions have been granted.
Summary: the key to importing nodes into sing-box is identifying the three source types—”subscription,” “single node,” and “JSON”—and then using the corresponding import entry in the client. After connecting, do not just look at whether the button is turned on; also check the IP, DNS, and browser environment so you can more accurately determine whether the proxy is actually working.