This article answers the question “How do you import nodes into sing-box?” It’s for users who have just installed sing-box and received a VLESS/VMess/Trojan/SS node or subscription link, but aren’t sure how to import it, verify the connection, or troubleshoot mismatches involving their IP, DNS, and browser environment.
1. First, identify the type of node you have
sing-box is a core program. Many everyday users choose a client with a graphical interface, such as SFI, sing-box GUI, Hiddify, or NekoBox. Button names may vary slightly between clients, but the import process is generally the same. Before importing, check which type of content you have:
- Subscription link: Usually starts with https:// and contains multiple nodes. Best for ongoing updates.
- Single-node link: Commonly starts with vless://, vmess://, trojan://, or ss://.
- Configuration file: Usually in JSON format and may need to be imported using “Import from file.”
If you’re using free nodes provided by this site, we recommend copying the subscription link first. If you only want to test a specific node, you can copy its individual link instead.
2. Steps to import nodes into a sing-box client
Here’s how to do it in a typical graphical client. Menu names may vary, but the steps are generally the same:
- Open the sing-box client and go to “Config,” “Configuration,” “Profiles,” or “Subscriptions.”
- Click “Add,” “+,” “Import,” or “Import from clipboard.”
- For a subscription link, choose “Add subscription,” paste the URL, and enter a name, such as “freevpn nodes.”
- For a single node, copy the full node link, then choose “Import from clipboard.”
- After importing, click “Update subscription” or “Refresh” and wait for the nodes to appear in the list.
- Select a node, then click “Start,” “Connect,” or “Set as active.”
Once connected, don’t rely solely on the client’s “Connected” status. Open a browser and visit an IP lookup site to confirm that your exit IP has changed. If it hasn’t, the system proxy, routing mode, or browser proxy may not be working.
3. How IP, DNS, and your browser environment relate after importing
Many people assume that importing a node and connecting is all it takes to access the internet through a proxy. In fact, there are three things to check. First, your exit IP, which determines where websites see you connecting from. Second, DNS, which determines how domain names are resolved. Third, your browser environment, including cache, cookies, WebRTC, time zone, and language.
If your IP has changed but DNS still shows your local ISP, you may have a DNS leak. In the client settings, try enabling options such as “Remote DNS,” “FakeIP,” or “Prevent DNS leaks.” The exact names vary by client. If your browser still reports an unexpected region, try clearing cookies for the site, disabling WebRTC in your browser, or testing again in a private window.
4. Common connection issues and how to troubleshoot them
- Empty subscription: Check that you copied the complete link and that it contains no spaces, then try updating the subscription again.
- Node won’t connect: Try another node. Free nodes may be unreliable depending on the number of users and network conditions.
- Connected, but webpages won’t load: Check that the system proxy is enabled, or switch between TUN, global, and rule-based modes.
- Only the browser is offline: Make sure the browser doesn’t have an incorrectly configured proxy of its own. Proxy extensions may also conflict.
- No internet on your phone: Check that VPN permission is enabled, disable battery-saving restrictions, and reconnect.
A practical approach is to import the subscription first, select a node and connect, check your IP, then test DNS and your browser environment. Following these steps in order should help you determine whether the issue is with the node, the client settings, or the browser environment.
In summary, importing nodes into sing-box is straightforward. The key is to identify whether you have a subscription, a single node, or a configuration file. After connecting, check your IP, DNS, and browser status to confirm that the proxy is actually working.