This guide explains how to import nodes into sing-box and why you might still be unable to open web pages, see no change in your IP, experience DNS leaks, or encounter browser environment issues after importing. It’s intended for beginners and walks you through importing a subscription or a single node, followed by some basic troubleshooting.
1. Get ready: client and node details
sing-box is a proxy core. It’s typically managed through a graphical client, such as sing-box GUI, SFI, or sing-box for Apple on Windows, Android, iOS, or macOS. Interface labels vary slightly between clients, but the basic process is the same: import a “subscription link” or a “configuration file.”
You’ll need one of the following:
- A subscription link: usually starts with https:// and contains multiple nodes.
- A single-node link: for example, a VLESS, VMess, Trojan, or Shadowsocks share link.
- A JSON configuration file: usually has a .json extension and is suitable for a prepared sing-box configuration.
This site compiles free nodes for testing, but their reliability depends heavily on your network environment. We recommend trying several nodes after importing them.
2. General steps for importing nodes into sing-box
- Install and open a sing-box client, then go to the “Configuration,” “Profiles,” or “Configuration Files” page.
- Select “Add,” “Import,” or “Import from URL.” If you have a subscription link, paste it in and save.
- For a single-node link, select “Import from Clipboard” or “Import Share Link.” For a JSON file, select “Import from File.”
- Once the import is complete, return to the home screen, select the configuration you just added, and tap “Start,” “Connect,” or “Enable VPN.”
- Visit an IP lookup site in your browser to confirm that your exit IP has changed.
If the client reports a format error, first check that you copied the entire link, especially any parameters at the end. If the subscription won’t update, try again on a different network or check that the link hasn’t expired.
3. How are IP, DNS, and the browser environment related?
Many people assume that once a node is connected, everything is working as it should. In fact, you need to check three things. First, your IP address determines the apparent location of your outgoing connection. If it hasn’t changed, the system proxy may not be enabled, or your browser may not be using the proxy.
Second, there’s DNS. DNS translates domain names into IP addresses. If the proxy is connected but DNS requests still go through your local network, you may be unable to open sites, see inconsistent location detection, or experience DNS leaks. We recommend enabling “Remote DNS,” “FakeIP,” or “DNS Proxy” in the client. The exact option name varies by client.
Third, there’s the browser environment, including cache, cookies, language, time zone, and WebRTC. Some sites assess all of these together. When testing, use a private window, disable WebRTC leaks if necessary, or clear old cookies to prevent a previous login session from affecting the results.
4. Troubleshooting connection failures and issues after importing
- Startup fails: Check whether the client supports the configuration. sing-box and Clash configurations aren’t directly interchangeable.
- Connected, but web pages won’t open: Try global mode and check whether your browser is using the system proxy.
- IP hasn’t changed: Check that VPN permissions, TUN mode, or the system proxy are enabled.
- Subscription update fails: Try opening the link in a browser to confirm that it’s accessible.
- Some sites won’t open: Try another node or compare rule mode with global mode.
In short, importing nodes into sing-box is straightforward: first confirm the node format, then import it via URL, clipboard, or file, and finally check your IP, DNS, and browser environment. If you run into problems, don’t focus only on the node. Troubleshoot in this order: client permissions, proxy mode, DNS, then browser cache. This usually helps pinpoint the cause.