How to Import Nodes in sing-box: Subscriptions, Single Nodes, and Their Relationship with IP, DNS, and Browser Environment

This article addresses the practical question of “how to import nodes into sing-box“: after an ordinary user obtains VLESS, VMess, Trojan, or Shadowsocks node links or a subscription URL, how to import them into a sing-box client, and understand why your IP, DNS, and browser environment can affect the access result after connecting.

1. What you need to prepare before importing

sing-box itself is a proxy core, and different platforms have different GUI clients, such as SFA on Android and common clients with a sing-box core on Windows/macOS. You should prepare these three things first:

• An installed sing-box GUI client;
• A working node link or subscription URL, which may come from your airport service or from the free nodes compiled by this site for temporary use;
• Make sure your phone or computer time is accurate, and that your network can normally access domestic websites.

If what you received is a full address beginning with https, it is generally a subscription link; if it begins with vless://, vmess://, trojan://, or ss://, it is usually a single node link.

2. Common steps for importing nodes into sing-box

1. Open the sing-box client and go to the “Configuration,” “Profiles,” or “Subscription” page. The name varies slightly between clients.
2. Select “Add” or “Import.” If it is a subscription URL, choose “Import from URL”; if it is a single node, choose “Import from Clipboard” or “Scan QR Code.”
3. Paste the subscription link or node link, and enter an easy-to-recognize name, such as “Free Nodes – Today.”
4. Click save or update subscription, then wait for the client to fetch the configuration.
5. Return to the home page, select the configuration you just imported, and click start or connect.
6. Open a browser and visit an IP-check website to confirm whether the outbound IP has changed.

If the list is empty after import, first check whether the link was copied completely, especially making sure you did not miss the ending parameters; if it says the format is incorrect, the client may not support directly recognizing this type of share link, and it may need to be converted into sing-box configuration format.

3. What is the relationship between nodes, IP, DNS, and the browser environment?

Many users think that as long as a node is imported successfully, all access will automatically work normally. In reality, the result is also related to your IP, DNS, and browser environment. After a successful connection, what websites usually see is the proxy node’s outbound IP, not your local broadband IP. If the IP has not changed, it may be because the system proxy was not enabled, the routing mode was chosen incorrectly, or the browser is using an independent proxy setting.

DNS is responsible for resolving domain names into IP addresses. If DNS still goes through the local network, situations such as “it connects but some websites won’t open,” “access gets redirected,” or “DNS leaks” may occur. It is recommended to enable the client’s default recommended DNS or remote DNS, and if you are unfamiliar with it, do not change complex rules casually.

The browser environment can also affect your judgment. For example, browser cache, logged-in accounts, WebRTC, location permissions, time zone, and language settings may all allow websites to identify your real usage environment. For everyday use, there is no need to overcomplicate things, but when testing, it is recommended to use an incognito window and disable unnecessary location permissions.

4. Troubleshoot connection failures in this order

• First confirm that the local network is working normally, and switch between Wi-Fi/mobile data for testing;
• Update the subscription. Free nodes become invalid quickly, so it is recommended to try several nodes;
• Check whether the system time is accurate. Incorrect time can cause TLS handshake failure;
• Switch to global mode for testing. If global mode works, it means there is a problem with the original rule-based routing;
• Turn off other VPN or proxy software to avoid port conflicts;
• If only the browser cannot connect, check the browser’s proxy extension or DNS settings.

In summary: the core of importing nodes into sing-box is distinguishing between subscription links and single-node links, then after import, confirming whether the proxy mode, outbound IP, and DNS are all working properly. Beginners are advised to first get it working with the client’s default configuration, and then gradually adjust rules and the browser environment.