How to Import Nodes in sing-box: Add Subscriptions and Config Files, and Troubleshoot Connection Issues

This article explains how to import nodes into sing-box. It helps you distinguish node links, subscription URLs, and configuration files, then walks you through importing, starting the client, and checking connectivity. It also explains why IP, DNS, and browser settings can affect the results. Menus may differ across operating systems and client versions, so follow the interface you see.

1. Check whether your source can be imported directly

sing-box is a proxy core, and clients that use it may not all offer the same import options. First, check the client name, version, and download source. Prefer official project releases and avoid modified versions from unknown sources.

  • Single-node link: Usually starts with vless://, vmess://, trojan://, or ss://. The client must support parsing the corresponding link format.
  • Subscription URL: Usually an HTTPS link. It may return a node list, a Clash configuration, or a sing-box configuration, so you cannot determine the format from the URL alone.
  • Configuration file: Usually in JSON format. A correct file extension does not guarantee compatibility; the contents must also meet the requirements of your sing-box version.

Supporting the sing-box core does not mean supporting every node link and subscription format. If the import page only accepts full configurations, you cannot paste in a single VLESS link.

2. Import using a method supported by your client

  1. Open the client and go to “Configuration,” “Profiles,” or a similar page. Tap “Add” and check whether it offers import from a remote configuration, local file, or clipboard.
  2. For a subscription, select the remote configuration option, enter a name, and paste the full URL. Confirm that the provider explicitly supports sing-box. If there is a format option, select the format compatible with your client.
  3. For a local configuration, save the file to your device first, then import it using the file picker. Do not use a screenshot or text displayed on a web page in place of the original configuration file.
  4. Use clipboard import only if the client explicitly supports parsing single-node links. If it does not, ask the provider for a compatible configuration. Do not paste a node link into a field intended for a configuration URL.
  5. After saving, manually update or download the configuration. Make sure there are no parsing errors, then select the configuration and start the client. If a system VPN permission prompt appears for the first time, check the app name before granting permission.

Subscription URLs often contain access credentials, so do not share them publicly. Do not submit them to untrusted online conversion sites to change their format. Free nodes on this site also need to be checked for format compatibility and validity; they are not guaranteed to work at all times.

3. What to check if the import succeeds but you cannot access the internet

Check the logs first to distinguish between configuration parsing errors, domain name resolution failures, and connection timeouts. For parsing errors, check the configuration format, client version, and fields mentioned in the error. For timeouts, try updating the subscription or switching to an available node, and make sure your device’s clock is correct and your current network can access the internet. Temporarily disable other proxies or VPNs while troubleshooting to avoid conflicts.

If your browser still shows your original IP, that does not necessarily mean the node failed to import. System proxy or VPN routing may not be enabled, or your current routing rules may be sending the site directly. First confirm that the client is running, then check whether the test request is going through the proxy.

For DNS errors, check the resolution settings in the configuration and whether “Secure DNS” in your browser is changing the resolution path. Node import, exit IP, DNS, and the browser environment are separate parts of the process. A proxy does not usually clear cookies, sign you out of accounts, or change your browser fingerprint automatically. If only one browser is having trouble, compare the results in a private window and check your proxy extensions. Do not assume every issue means the node is unavailable.

Leave a Comment

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

中文 EN
🚀

RedGate VPN

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

立即体验 →
⚡

告别卡顿

RedGate VPN
全球高速节点

免费下载 →
Scroll to Top