This guide explains how to import nodes into sing-box and why webpages may still fail to load, your IP may remain unchanged, DNS may leak, or your browser environment may behave unexpectedly after importing. It’s intended for first-time sing-box users. Follow the steps to import a subscription, enable the proxy, and perform basic troubleshooting.
1. Prepare the sing-box client and node information
sing-box is a proxy core. Most users use a client with a graphical interface, such as sing-box GUI on Windows, SFA on Android, or a third-party client that supports sing-box configurations. Download the client from the project’s official website or a trusted app store to avoid unofficial modified versions.
You’ll need one of the following node sources: a subscription link, an individual share link, or a JSON configuration snippet. This site collects free nodes and subscription information, but free nodes may vary in reliability. If importing fails, try another node.
2. Common ways to import nodes into sing-box
- Import a subscription link: Open the client and find the “Profiles / Configuration / Subscription” section. Select “Add Subscription,” paste the subscription URL, and save it. Then click Update. Once the update succeeds, multiple nodes will appear. Choose one with low latency or one that connects successfully.
- Import a share link: If you have a link beginning with vless, vmess, trojan, hysteria2, or another protocol name, select “Import from Clipboard” or “Import Share Link” in the client. After importing, check that the name, server address, port, and protocol are displayed correctly.
- Import a JSON configuration: Some clients let you paste sing-box JSON directly. Go to the “Configuration” page, create a new configuration, paste in the contents, save, and start it. If you’re a regular user, avoid editing complex fields manually, as formatting errors can prevent the configuration from starting.
After importing, return to the home screen, select the relevant configuration, and click Start or Connect. If the client offers different modes, try “Rule Mode” for everyday browsing. If webpages still won’t load, temporarily switch to “Global Mode” to test.
3. How IP, DNS, and the browser environment are related
Importing a node is only the first step. Whether you can access the internet through the proxy also depends on your IP, DNS, and browser environment. After connecting, visit an IP lookup site. If it shows the node’s location, your traffic is probably going through the proxy. If it still shows your local ISP’s IP, the system proxy may not be handling your traffic, your browser may not be using the proxy, or the client may not have started successfully.
DNS translates domain names into IP addresses. If DNS requests are still handled by your local network, you may be unable to open websites, experience unexpected redirects, or expose your browsing activity. We recommend enabling the client’s built-in or remote DNS and avoiding browser-specific DNS settings that conflict with the client.
Your browser environment can also affect the results. For example, Chrome, Edge, and Firefox may cache old DNS records, retain location information from previous logins, or be affected by extensions. To troubleshoot, try an incognito window, disable other proxy extensions, and clear site data before testing again.
4. Troubleshooting checklist for connection failures after importing
- Subscription update fails: Check that the link is complete and that your network can reach the subscription address. If needed, paste the link into a browser to test it.
- The client starts, but webpages won’t load: Switch to Global Mode, try another node, and make sure your system clock is accurate.
- Your IP hasn’t changed: Check whether the system proxy, VPN mode, or TUN mode is enabled. The setting may have a different name in different clients.
- DNS issues: Turn off secure DNS in your browser, restart the client, and then refresh a DNS test page.
- Some websites won’t load: The rules may not be matching your traffic. Try updating the rule set or temporarily switching to Global Mode.
If you’re not sure what’s causing the problem, troubleshoot in this order: update the subscription, try another node, switch to Global Mode, check your IP, check DNS, and try another browser. Most issues can be identified with these steps.
In summary, importing nodes into sing-box is straightforward. The key is to make sure the node format is valid, the client is handling your traffic, and your IP, DNS, and browser environment are consistent. Once everything is working, choose a suitable node based on its reliability.