How to Import Nodes in sing-box: Subscription Links, Config Files, and Connection Troubleshooting Guide

This article addresses the practical question, “How do I import a node into sing-box?” Once you have a subscription link, a node link, or a JSON file, you need to know where to import it, how to start it afterward, and why websites may still be inaccessible even when the client says it’s connected. sing-box GUI clients don’t offer exactly the same features on every platform, so the steps below cover common workflows and explain how node configuration relates to your IP, DNS, and browser environment.

1. Check your client and node format

Install a client that’s suitable for your system from a source linked to by the official sing-box documentation, and avoid modified versions from unknown sources. When you launch it for the first time, grant VPN or network extension permissions when prompted. Note that the command-line core is different from a GUI client: the core program alone usually won’t have an “Add subscription” button.

Check what you have before importing it: a link starting with https:// may be a subscription URL; a link starting with vless://, vmess://, or trojan:// is usually a single-node share link; and a JSON file may contain a complete configuration. sing-box configurations, Clash YAML files, and node share links are different formats and can’t be converted into one another just by changing the file extension.

2. Import nodes based on what you have

  1. Subscription link: Open the client’s “Configuration,” “Config,” or “Profiles” page, choose the option to add a remote configuration, enter a name, paste the link, and download and save it. The link generally needs to return a sing-box configuration supported by the client. Whether a generic subscription can be imported depends on whether the client supports parsing it.
  2. Local JSON file: Choose the option to import from a file, locate the downloaded configuration, and save it. If you only have the JSON text, save it as a .json file first. Make sure it doesn’t include explanatory text or Markdown code fences.
  3. Single-node share link: First check whether the add menu offers “Import from clipboard” or an entry for the relevant protocol. If it doesn’t, ask the node provider for a configuration compatible with your client. Don’t paste the share link into the remote configuration URL field.
  4. Select the configuration you just imported, validate it or try starting it. If the interface lets you choose a node, select an available one in the proxy group, then allow the system to establish a VPN connection.

If our free nodes page offers a dedicated sing-box option, use that format if possible. Subscription URLs may contain access credentials, so don’t share screenshots of them. Avoid submitting them to unfamiliar online conversion sites as well.

3. How to confirm that the connection is working

Open a regular webpage, then check your exit IP on a trusted IP lookup site. “Connected” only means the client has started; it doesn’t guarantee that all traffic is going through the node. In rule mode, domestic websites may connect directly, so check the target website and the client’s connection logs rather than relying only on the status icon.

Your IP is your network’s exit address. DNS translates domain names into addresses. Your browser may also retain cookies, location permissions, and login information. Importing a node doesn’t clear this data or guarantee that the region shown in your browser will change immediately. When testing, try a private window and temporarily disable other proxy extensions to prevent proxy settings from conflicting.

4. Troubleshooting import and connection issues

  • Download failed: Check that the link is complete and hasn’t expired, and make sure your current network can reach the subscription URL.
  • Format error: Check whether you’re using a Clash subscription, webpage URL, or single-node link by mistake. Ask the provider for a compatible configuration based on the error message.
  • Startup failed: Check the first significant error in the logs, and confirm that the client version matches the configuration requirements. Don’t blindly delete fields.
  • The client starts, but websites won’t load: First confirm that your local network is working, then switch nodes. If the logs report a domain resolution failure, check the DNS settings in the configuration and whether your browser’s Secure DNS is conflicting with them.

Change one thing at a time and test again. Keep a working configuration before updating. This helps you tell the difference between an expired subscription, an unavailable node, and a problem with your local environment, without repeatedly reinstalling the client.

Leave a Comment

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

中文 EN
🚀

RedGate VPN

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

立即体验 →
⚡

告别卡顿

RedGate VPN
全球高速节点

免费下载 →
Scroll to Top