This guide explains how to import nodes into sing-box, including importing subscription links and configuration files, adding nodes manually, and checking your IP, DNS, and browser environment after connecting. It’s written for everyday users who are new to sing-box and want to follow the steps as they go.
1. Before You Import
sing-box is a proxy core, and on most systems it’s used with a graphical client, such as a sing-box client for Windows, macOS, Android, or iOS. Before importing nodes, make sure you have valid node information. Common formats include subscription links, share links for VLESS/VMess/Trojan/Hysteria, and JSON configuration files. This site also collects free node resources, but the stability of free nodes depends on the network route and the number of users, so it’s a good idea to have a few backups ready.
- Subscription link: Usually starts with https:// and can import multiple nodes at once.
- Share link: Such as vless:// or trojan://, suitable for importing a single node.
- Configuration file: Usually a .json file, suitable for directly replacing or importing a configuration.
2. Import Nodes Using a Subscription Link
If you have a subscription link, this is the recommended method because it makes updating nodes easier later. Button names vary slightly between clients, but the general process is the same.
- Open the sing-box client and go to the “Configuration,” “Profiles,” or “Subscriptions” page.
- Click “New,” “Add,” or the plus sign in the upper-right corner.
- Select “Import from URL,” “Remote Profile,” or “Subscription.”
- Paste the subscription link and enter a name, such as “Free Nodes,” or choose your own.
- Save it, then click “Update Subscription” and wait for the node list to load.
- Select a node, return to the home page, and turn on the proxy connection.
If you see a format error, first check that you copied the entire link, especially the https:// at the beginning, and that you didn’t include any extra spaces. If the subscription link opens but no nodes appear, the subscription may be temporarily unavailable or the client may not support its format.
3. Manually Import a Single Node or Configuration File
If you only have a single node link, select “Import from Clipboard” in the client. Copy the complete node link first, then click Import. Once it’s imported successfully, the node will usually appear in the node list under its corresponding name.
If you have a JSON configuration file, select “Import File.” We recommend backing up your existing configuration first in case it gets overwritten and you can’t restore it. If the client reports a configuration validation error after import, the JSON may be incomplete, missing required fields, or incompatible with your version of the client.
4. Check Your IP, DNS, and Browser Environment After Connecting
Successfully importing a node and connecting doesn’t necessarily mean your browser is configured correctly. We recommend checking the following in order:
- IP check: Open an IP lookup website and confirm that the displayed exit location matches the node’s region.
- DNS check: If DNS still shows your local ISP, you may have a DNS leak. Enable remote DNS or rule-based DNS in the client.
- Browser check: Turn off browser proxy extensions to avoid conflicts from having both the extension and sing-box route traffic.
- System time: An incorrect system time can cause TLS handshake failures, so enable automatic time synchronization.
If only your browser can’t access the internet while chat apps or other applications work normally, the issue is usually related to the browser cache, proxy extensions, or secure DNS settings. Try an incognito window, turn off the browser’s built-in secure DNS, or test with another browser.
5. Troubleshooting Common Connection Failures
If you can’t connect, don’t keep reinstalling the client. Troubleshoot in this order: First, update the subscription and try another node. Second, check whether you can access domestic websites normally. Third, close any other VPNs, network accelerators, or proxy software. Fourth, check the client logs for messages such as timeout, TLS, or DNS.
If the logs show timeout, the node is probably unreachable or the network connection is blocked. If they show certificate or handshake failed, the issue may be the system time, protocol settings, or client version. If they show a DNS resolution failure, check the DNS settings first. In practice, node availability, DNS settings, and your browser environment all affect the final browsing experience. Test each one rather than focusing only on the node itself.