This article addresses the question of “how to import nodes into sing-box“: it is suitable for first-time sing-box users and explains how to import a subscription or a single node, how to check whether it has taken effect, and the relationship between your IP, DNS, and browser environment after connecting, so as to avoid situations where “the software shows connected, but webpages won’t open or the IP hasn’t changed.”
1. Prepare the sing-box client and node information
sing-box itself is a proxy core. Ordinary users usually need a client with a graphical interface, such as a sing-box GUI client or a sing-box-based proxy tool on Android, Windows, or macOS. Before installing, it is recommended to download from the project’s official website, an app store, or a trusted release page, and avoid using modified versions from unknown sources.
Before importing nodes, you need to prepare any one of the following:
- Subscription link: usually an https URL, which the client can use to automatically fetch multiple nodes.
- Single node link: such as VLESS, VMess, Trojan, Shadowsocks, and other share links.
- Configuration file: usually in json format, suitable for users who already have a complete configuration.
This site will compile free node information that can be used for testing, but the stability of free resources may vary. It is recommended to treat them only as a temporary testing or backup option, and not use them for important accounts or sensitive operations.
2. Common steps for importing a subscription into sing-box
The names of interface options may differ slightly between clients, but the process is basically the same. Taking a common GUI client as an example, you can follow these steps:
- Open the client and go to the “Profiles,” “Configuration,” “Subscription,” or “Node Management” page.
- Click “Add,” “+,” or “Import.”
- Select “Import from URL,” “Subscription Link,” or “Remote Profile.”
- Paste your subscription URL and enter an easy-to-recognize name, such as “freevpn test subscription.”
- After saving, click “Update Subscription” or “Sync.”
- Return to the node list, select a node, and then click to start the connection.
If you only have a single node link, choose “Import from Clipboard” or “Import Share Link.” After copying the node link, open the client. Some clients will recognize it automatically; if not, paste it manually into the import box.
3. How to tell whether the import was successful
A successful import does not necessarily mean you can access the external network. You still need to confirm that the proxy is actually working. It is recommended to check in this order:
- Whether the new node appears in the node list within the client, and whether there are any obvious error messages.
- After clicking connect, whether the status shows “Running,” “Started,” or a similar message.
- Open an IP lookup website in your browser and check whether the outbound IP has changed.
- Visit commonly used test websites to confirm that webpages load properly.
If the IP has not changed, the system proxy may not be enabled, the browser may not be using the system proxy, or the client’s current mode may not be global/rule-based proxy mode. In this case, you can switch to system proxy in the client or temporarily use global mode for testing.
4. What is the relationship between IP, DNS, and the browser environment?
Many users assume that once a node is connected, the “environment switch” is complete, but in fact it also involves your IP, DNS, and browser fingerprint. IP is the outbound address seen by websites; DNS is responsible for resolving domain names; and the browser environment includes language, time zone, cache, cookies, WebRTC, and more.
If the proxy can connect but some websites still will not open, DNS may not be going through the proxy or may be polluted. You can enable “Remote DNS,” “Proxy DNS,” or similar options in the client settings, and avoid running multiple proxy applications at the same time. If the website still shows your original region, check whether the browser has WebRTC leaks enabled, local account-based location enabled, or site cache affecting the result.
For everyday use, it is recommended to use rule mode for normal browsing; when testing nodes, first use global mode to troubleshoot; and when logging into accounts, try to keep the same account on a relatively stable node and browser environment, and avoid switching regions frequently.
5. Quick troubleshooting for connection failures
- Subscription update failed: check whether the link is complete and whether you need to copy the original subscription URL.
- Node timeout: try other nodes; free nodes may be temporarily unavailable.
- Can connect but webpages won’t open: check the system proxy, DNS settings, and browser proxy status.
- The client reports a configuration error: this indicates that the node format may be incompatible; switch to a sing-box-supported subscription or update the client.
In summary, when importing nodes into sing-box, it is best to use a subscription link first because it is easier to update and switch; a single node is more suitable for temporary testing. After connecting, focus on whether the outbound IP, DNS, and browser are consistent, so you can determine whether the proxy environment has actually taken effect.