This article answers the question “How do you import nodes into sing-box?” You’ll learn how to import nodes using a subscription link or configuration file, and why you should check your IP, DNS, and browser environment after importing to avoid common issues like “connected, but webpages won’t load,” “my IP hasn’t changed,” and “DNS leaks.”
1. Before you import: Check the format of your node information
sing-box supports a range of proxy protocols, but the import process varies slightly between client interfaces. Most users use sing-box for Android, a graphical client on iOS, or a sing-box client with a graphical interface on Windows or macOS. Before importing, check which of the following you have:
- Subscription link: Usually an https link that returns multiple node configurations when opened.
- Single share link: For example, one starting with vless://, vmess://, or trojan://.
- JSON configuration file: The file may have a .json extension and can be imported directly or pasted.
This site provides free nodes and subscription information for testing. You can also use an airport subscription you already have. Don’t share your subscription link publicly on forums or in group chats, or others may misuse it.
2. General steps for importing nodes into sing-box
The button names may vary across platforms, but the process is much the same. Here’s an example using a typical graphical client:
- Open the sing-box client and go to “Configuration,” “Profiles,” or “Subscriptions.”
- Click “Add,” “New Profile,” or the plus sign in the top-right corner.
- For a subscription link, select “Import from URL,” paste the subscription address, save it, and then click Update.
- For a single node link, select “Import from clipboard” or “Import share link.”
- For a JSON file, select “Import from file,” locate the configuration file, and confirm.
- Return to the home screen, select the configuration you just imported, and tap Start or Connect.
Before connecting, we recommend closing any other VPN or proxy apps to avoid port conflicts. The first time you start the client, your system may prompt you to create a VPN connection. Select Allow.
3. Why check your IP, DNS, and browser environment after importing?
Many users assume that if the client starts after importing a node, everything is working. You should also verify that your traffic is actually going through the proxy. The simplest way is to visit an IP lookup site and check whether the displayed exit location has changed. If your IP hasn’t changed, the system proxy may not be enabled, the browser’s traffic may not match the rules, or the client may not have VPN permission.
DNS matters too. If webpages load but some sites behave strangely or show the wrong region, your DNS queries may still be going through your local ISP. You can enable remote DNS, FakeIP, or rule-based DNS in the client; the exact names vary. Most users don’t need to fine-tune the settings—start with the template recommended by the client.
Your browser environment can also affect the results. For example, browser cache, the region associated with your signed-in account, WebRTC, your local language, and your time zone may reveal information about your original environment. When testing, try using a private window. If necessary, disable WebRTC or switch to a clean browser profile.
4. Quick troubleshooting checklist for connection failures
- Subscription won’t update: Check that the link is complete, that it doesn’t require you to sign in, and that your network can reach the subscription URL.
- Subscription updates, but you can’t connect: Try another node and check whether the node is still active and whether its protocol is supported by your client.
- It shows connected, but webpages won’t load: Check system VPN permissions, proxy mode, rule mode, and DNS settings.
- Some websites won’t load: Test in global mode. If it works globally, the issue is with the routing rules.
- Unstable speeds: Try another route, avoid peak hours, and close apps that use a lot of bandwidth.
In summary, importing nodes into sing-box comes down to “add a subscription or configuration—update it—select the configuration—start the connection—verify your IP and DNS.” If something goes wrong, don’t focus only on the node itself. Check DNS and your browser environment as well; this often helps you find the cause faster.