How to Import Nodes in sing-box: Import Configs, Update Subscriptions, and Troubleshoot Connections

This article explains how to import nodes into sing-box, troubleshoot unrecognized subscriptions, and fix websites that remain inaccessible after connecting. It also clarifies how your exit IP, DNS, and browser settings affect connectivity. Menus vary across sing-box graphical clients and platforms, so check the client name and version before following these steps rather than applying instructions for other software.

1. First, determine whether you have a node or a configuration

sing-box uses JSON configurations, but not every JSON file is compatible. Common links such as vless://, vmess://, and trojan:// are individual node share links. A Clash YAML file or node-list subscription is not the same as a sing-box configuration. Whether you can paste a node directly depends on whether the client supports parsing it; sing-box does not provide one universal import method for this.

When installing, use an official project release channel or a trusted app store, and check the system requirements. Prepare a sing-box configuration file or dedicated subscription URL from your service provider. If you use this site’s free nodes, check the format and validity information first.

2. Import according to the configuration source

  1. Open the client and look for an add option under “Configuration,” “Profiles,” or a similar page. If the software only supports command-line operation, use a graphical client for your platform instead; this article does not cover launching sing-box from the command line.
  2. If you have a compatible JSON file, select “Import from file,” grant permission to read the file, and choose the configuration. If pasting is supported, copy the complete JSON and make sure no brackets or quotation marks are missing.
  3. If you have a remote configuration URL, select “Import from URL” or “Remote configuration,” enter a name and the URL, then save and download or update it. Only subscription formats supported by that option will work.
  4. If you only have a single-node link, first check for an “Import from clipboard” option. If there isn’t one, ask the provider for a compatible configuration. Do not enter a share link in the remote JSON URL field.
  5. Set the new configuration as the current one, check the node selection, and tap Start. The first time you use it, allow the app to create a VPN connection when prompted by the system. If an error occurs, check the logs first rather than repeatedly reinstalling the app.

A subscription URL may contain access credentials, so don’t post it in public group chats or submit it to unfamiliar online conversion sites. If an update fails, first check that the URL is complete, that it can be reached over your network, and that the provider hasn’t changed the configuration.

3. After importing, how to confirm it’s working

Open a website you can usually access, then test the target site and check the client logs for connection records. To check your exit IP, use a trusted IP lookup page. Routing rules may send traffic from different websites through different exits, so don’t judge all traffic based on a single lookup result.

Your IP indicates the network exit visible to websites; DNS resolves domain names to addresses; and your browser may use its own proxy, extensions, or secure DNS. A connected node does not mean all browser traffic is going through the proxy. If only one browser is having problems, first pause any proxy extensions, check its proxy settings, and then compare results in a private window.

4. Troubleshoot connection failures in this order

  • Format error during import: Check whether you mistakenly used a Clash configuration or a standard node subscription, and make sure the configuration is compatible with your core version.
  • No websites open after startup: Check the system time and VPN permissions, and make sure there are no conflicts with other VPNs. Then check the logs for timeouts or DNS resolution errors.
  • Only some domains won’t open: Check your routing rules and DNS settings. Don’t copy DNS parameters from an unverified source.
  • It stopped working after an update: Keep a copy of the error details without any credentials, check whether the node has expired or is temporarily unavailable, and then try another configuration the provider has confirmed is working.

Change only one setting at a time while troubleshooting, and keep a backup of the original configuration. This makes it easier to identify the cause if changing DNS, routing, and browser settings all at once doesn’t help.

Leave a Comment

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

中文 EN
🚀

RedGate VPN

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

立即体验 →
⚡

告别卡顿

RedGate VPN
全球高速节点

免费下载 →
Scroll to Top