This article addresses a common question: how to import nodes into sing-box. You’ll learn how to import free nodes, subscription links, or individual node links into a sing-box client, and understand how the imported configuration relates to your IP address, DNS, and browser environment. This makes it easier to determine whether a problem is caused by the node, the configuration, or the web environment.
1. What to prepare before importing
sing-box is a proxy core. Most users use a client with a graphical interface, such as a tool that supports the sing-box core on Windows, Android, or iOS. Before importing nodes, make sure you have the following:
- A working node link in a format such as VLESS, VMess, Trojan, or Shadowsocks;
- Or a subscription link, usually beginning with http or https;
- A client that supports sing-box, with permission to create a VPN configuration;
- A working network connection that can at least open regular webpages.
Our site collects free nodes for testing, which are suitable for temporary learning and configuration checks. However, free-node stability can vary depending on the route, number of users, and time of day, so we recommend testing several nodes after importing them.
2. Steps for importing subscription nodes into sing-box
If you have a subscription URL, we recommend importing it as a subscription so it’s easier to update later. The interface varies slightly between clients, but the general process is the same:
- Open the sing-box client and go to the “Configuration,” “Profiles,” or “Subscription” page;
- Click “Add,” “+,” or “Import from URL”;
- Paste in the subscription link and enter a name, such as “Free Nodes,” or choose a custom name;
- Save it, then click “Update Subscription” or “Download”;
- Return to the node list and select a node with low latency or one that is available;
- Turn on the VPN/proxy switch, then open a browser to test access.
If the update fails, first check that there are no extra spaces in the subscription link and that it hasn’t been truncated by a messaging app. Some clients require you to allow VPN access in a system prompt; otherwise, the import may appear successful even though traffic isn’t being routed through the client.
3. Manually importing an individual node link
If you only have a vmess://, vless://, trojan://, or ss:// link, you can use “Import from Clipboard.” Copy the complete node link, then open the client and click “Import from Clipboard” or the equivalent option. After importing, check three things: whether the protocol was identified correctly, whether the server address and port are complete, and whether any transport parameters, such as TLS/Reality/WebSocket, are missing.
Some sing-box clients also support importing nodes by scanning a QR code. If the code comes from a screenshot, poor image quality may prevent it from being recognized. In that case, try copying the link instead. A successful import doesn’t guarantee a working connection: the node must be online, its parameters must match, and your local network must not be blocking the relevant ports.
4. How IP, DNS, and your browser environment are related
Many users only check whether webpages open after importing a node, but it’s important to distinguish between several factors. Your IP determines the apparent location of your connection to a website; DNS resolves domain names to addresses; and your browser environment includes information such as cache, cookies, language, time zone, and WebRTC.
- If an IP lookup site shows a changed IP address, the proxy is most likely working;
- If some websites won’t open, the cause may be DNS resolution, routing rules, or the node’s connection;
- If a webpage still reports a region mismatch, this may be related to browser cookies, your account’s region, or a WebRTC leak;
- If the issue occurs in only one browser, try private browsing, clearing the cache, or testing another browser.
After importing a node, first visit an IP lookup site to confirm your exit IP, then test the websites you normally use. Avoid switching nodes repeatedly and immediately logging in to important accounts, as this may trigger account security checks.
5. Quick troubleshooting for connection failures
If you can’t connect after importing a node into sing-box, check the following in order: first, confirm that the subscription updated successfully; second, make sure the node is selected and enabled; third, confirm that the system has granted VPN permission; fourth, check that the system time is correct, since some TLS nodes are sensitive to time differences; fifth, try a different network, such as switching from Wi-Fi to mobile data.
If the client log shows “timeout,” the node may be unreachable or blocked by your local network. If it shows terms such as “handshake,” “certificate,” or “reality,” the node parameters may be incomplete or the protocol may be incompatible. In that case, trying another node is usually more effective than repeatedly reinstalling the client. Once you understand this process, importing nodes into sing-box is straightforward. The key is to remember that “imported successfully” and “connected successfully” are not the same thing.