This article addresses the question of “how to import nodes into sing-box“: including importing via a subscription link, importing via a local configuration file, and why you still need to check your IP, DNS, and browser environment after connecting. It is suitable for ordinary users who have just installed sing-box and want to import free nodes from this site or other sources.
1. What to prepare before importing
sing-box itself is a core program, and many users use it together with a graphical client, such as clients on Windows, Android, iOS, and macOS that support the sing-box core. Different clients may use slightly different interface labels, but the basic idea is the same: obtain node information, import it into the client, select a node, and start the proxy.
- Make sure the client supports sing-box or the sing-box configuration format.
- Prepare a subscription link or a JSON configuration file.
- Keep the system time accurate to avoid TLS certificate validation errors.
- Close other VPN/proxy software to avoid port conflicts.
If you are using the free nodes provided by this site, you will usually see a subscription address or individual node links. Free nodes may become invalid or congested, so if you cannot connect after importing, do not rush to change system settings—try switching nodes first.
2. Importing nodes with a subscription link
Subscriptions are suitable when nodes are updated frequently, as the client will fetch the configuration from the link. The common steps are as follows:
- Copy the subscription link, being careful not to include extra spaces or line breaks.
- Open the sing-box client and go to “Configuration,” “Subscription,” or “Profiles.”
- Click Add, then choose “Import from URL” or “Remote Profile.”
- Paste the subscription link, save it, then click update/refresh.
- Return to the node list, select a node, and then click to start the connection.
If it says parsing failed, the subscription format is usually not recognized by the current client. You can try updating the client, or check whether the subscription page offers different formats such as Clash, V2Ray, and sing-box. Choosing a subscription specifically for sing-box is more reliable.
3. Importing via a local configuration file
If what you received is a config.json file, you can choose “Import from File.” On desktop, this usually means clicking import file; on mobile, you may need to save the file to the “Downloads” folder first and then select it from the client. After importing, do not edit the JSON content casually—even a missing comma may prevent the configuration from starting.
If startup fails, first check the client logs. Common errors include the port being occupied, JSON format errors, the node address failing to resolve, or the protocol not being supported. If you encounter a port conflict, you can close other proxy software or change the local HTTP/SOCKS port in the client settings.
4. Check your IP, DNS, and browser environment after connecting
If the node shows as connected, that does not necessarily mean the browser is definitely using the proxy. It is recommended to check in the following order:
- Open an IP lookup website and confirm that the displayed exit IP has changed.
- Check for DNS leaks. If DNS still shows your local ISP, enable DNS proxying in the client or use rule mode.
- If your browser has a proxy extension installed, it may override the system proxy, so it is recommended to disable the extension first for testing.
- Test once in an incognito window to rule out the effects of cache, cookies, and extensions.
Many issues where “it connects but webpages won’t open” are actually related to DNS resolution or the browser’s proxy environment, and do not necessarily mean the node is broken. If only one specific website will not open, you can switch to global mode for testing. If global mode works but rule mode does not, that indicates the rules or traffic-splitting configuration need to be updated.
5. Quick troubleshooting for connection failures
Handling it in this order saves the most time: first switch nodes, then update the subscription; restart the client; confirm your local network is working properly; check the system time; close other VPNs; and review log keywords. If timeout appears repeatedly in the logs, the node is most likely unreachable or the network is blocking it; if you see authentication or bad request, the node information may have expired.
In summary: the core ways to import nodes into sing-box are “import via subscription URL” or “import via JSON file.” After a successful import, you should also confirm whether the IP, DNS, and browser proxy environment are consistent, so you can determine whether the problem lies with the node, the client, or your local environment.