How to Import Nodes in sing-box: A Guide to Subscriptions, Config Files, and Troubleshooting Connections

This guide addresses the practical question of how to import nodes into sing-box: first check whether your link can be used directly, then import the configuration and start the connection, and troubleshoot issues such as an unchanged IP, DNS problems, or websites not loading in your browser. Menus and import options vary across sing-box GUI clients, so follow the general steps below and refer to your client for the exact labels.

1. Distinguish node links, subscriptions, and configuration files

sing-box is a proxy core; that does not mean every client built on it supports the same import methods. Before installing, get a client for your system from the project’s official release page or a trusted app store, and check which formats it supports.

  • Single node links: Commonly start with vless://, vmess://, trojan://, and similar schemes. The client must be able to parse the relevant format.
  • Subscription URLs: Usually HTTPS links. The content they return might be a node list, a Clash configuration, or a sing-box configuration, so you cannot identify the format from the URL alone.
  • Configuration files: Usually JSON. In addition to nodes, they may include DNS, routing, and inbound settings. A correct file extension does not guarantee that the contents are compatible.

Clash YAML cannot be used directly as sing-box JSON. If the source offers multiple subscription formats, choose one explicitly marked as compatible with your client and version.

2. Import using a method supported by your client

  1. Open the client, go to “Configuration,” “Profiles,” or a similar page, and click Add. If this is your first time, keep the existing configuration so you can restore it if anything goes wrong.
  2. If you have a compatible remote configuration, choose “Import from URL” or “Remote Configuration,” paste the full URL, and save it. If the interface has an update button, click it once as well.
  3. If you have a JSON file, choose “Import from File.” If you only have a node sharing link, use “Import from Clipboard” or scan its QR code only if the client explicitly supports that method.
  4. Select the newly imported configuration and check for errors such as parsing failures, unsupported fields, or missing required settings. After importing a single node, some clients may also require you to generate a full configuration using their own template.
  5. Start the connection and grant VPN or network extension permissions if prompted by your system. On desktop, enable the system proxy or the client’s TUN mode as needed, then select an available node to test.

A successful import only means the configuration was accepted; it does not guarantee that the node will work. For free nodes on this site, check the format and last updated time, then test the connection. Do not submit subscription URLs containing tokens to unfamiliar online conversion sites.

3. How can IP, DNS, and your browser affect the results?

Your IP reflects the network egress used for requests. When split tunneling is enabled, domestic websites may still connect directly, so check your egress using a site expected to go through the proxy. Do not judge whether the connection works based on a single page. Browser extensions, built-in proxy settings, or other VPNs can also change the request path, so disable conflicting tools while testing.

DNS resolves domain names. If the logs show resolution failures or some domains fail to load, first check whether the DNS settings included with the subscription are compatible with your version and network. Avoid mixing snippets from different guides indiscriminately. Your browser’s Secure DNS may use a different resolution path; temporarily switch back to system DNS to compare.

4. Troubleshoot connection failures in order

First, turn off the proxy and confirm that your basic network connection works. Then check your system time, whether the subscription can be updated, and any configuration error messages. Next, try another node and check the logs for timeouts, authentication failures, or certificate errors. If apps work but your browser does not, focus on browser proxy extensions, cached data, and Secure DNS. If only some apps are affected, check the coverage of the system proxy or TUN mode. Do not disable certificate verification to hide connection errors; instead, check the node parameters with their source or update the configuration.

Leave a Comment

Your email address will not be published. Required fields are marked *

中文 EN
🚀

RedGate VPN

免费节点太挤太慢?
升级高速稳定专线

立即体验 →
⚡

告别卡顿

RedGate VPN
全球高速节点

免费下载 →
Scroll to Top