This guide explains “how to import nodes into sing-box” and how to troubleshoot common issues after importing, such as being unable to access websites, your IP address not changing, DNS leaks, or pages not loading in your browser. It’s intended for everyday users who already have a free node, subscription link, or individual share link. Just follow the steps below.
1. Prepare the sing-box client and node information
sing-box is a proxy core. On phones and computers, you’ll typically need to use it with a graphical client, such as a client that supports the sing-box core. After installing the client, first check what type of node information you have:
- Subscription link: Usually a URL beginning with https://, suitable for updating multiple nodes at once.
- Individual node link: Common formats include vless://, vmess://, and trojan://.
- Configuration file: Usually a JSON file, suitable for importing a complete configuration directly.
If you’re using free nodes from this site, we recommend using the subscription method, as it makes future updates easier. Keep in mind, though, that free node stability depends on the route and the number of people using it at the same time. If a connection fails, try another node.
2. General steps for importing nodes into sing-box
- Open the client and go to the “Configuration,” “Profiles,” or “Subscription” page.
- Select “Add subscription” or “Import from URL,” paste the subscription link, and enter a name such as freevpn or one of your choice.
- Click “Update,” “Download,” or “Save,” then wait for the client to retrieve the node list.
- Return to the node page and select a node with low latency or one that’s available.
- Enable system proxy or VPN mode. Once the status shows that you’re connected, open a browser to test it.
If you have an individual node link, select “Import from clipboard” or “Add manually” on the add page, paste the vless:// link or similar, and save it. If you have a JSON configuration file, select “Import file,” then enable the configuration after importing it.
3. How IP, DNS, and your browser environment are related
Many people assume that connecting to a node means everything is working, but you should also check whether your IP, DNS, and browser environment are consistent. Your IP address is the exit address websites see when you access them. DNS translates domain names into IP addresses. Your browser environment includes information such as cached data, proxy settings, WebRTC, language, and time zone.
After importing a node, check things in this order: Visit an IP lookup site to see whether your exit IP has changed. Then open a DNS test page and make sure the DNS server isn’t your local ISP’s. Finally, visit the target website in a private window to rule out browser cache issues. If you have other proxy extensions installed in your browser, disable them first to avoid conflicts with sing-box.
4. How to troubleshoot connection failures after importing
- Subscription won’t update: Check that the link is complete and that your network can access the subscription URL. If necessary, try again on a different network.
- You can select a node, but websites won’t load: Try another node or restart proxy/VPN mode in the client.
- Your IP hasn’t changed: Make sure system proxy or TUN/VPN mode is enabled. Saving the configuration without connecting won’t be enough.
- Some websites won’t open: Try switching between rule and global modes, or clear your browser’s DNS cache.
- DNS issues: Enable remote DNS in the client settings or use a recommended secure DNS configuration.
If the logs show a timeout, the node is probably unavailable or your network can’t reach that route. If you see a parse, format, or JSON error, the subscription content or configuration format isn’t recognized by your current client. Try a different client or copy the link again.
5. Tips for use
For everyday use, save at least two working configurations. If you can’t connect, update the subscription first, then switch nodes. Don’t run multiple proxy apps at the same time, as this can cause port conflicts. After importing, make sure that your traffic is actually going through the proxy, that DNS isn’t leaking, and that old browser extensions aren’t interfering. These checks should be enough to confirm whether the sing-box node was imported successfully.