How to Add Nodes to sing-box: Subscriptions, Config Files, and Connection Troubleshooting

This article explains how to import nodes into sing-box in three scenarios: using a subscription link, a configuration file, or a single-node link. It also covers how to check your IP, DNS, and browser environment if you can’t get online after importing. Menu names and import options vary between sing-box clients, so refer to the interface you’re using.

1. Check the client and node format first

sing-box is a proxy core, and graphical clients built around it don’t necessarily offer the same features. Before installing a client, check the project’s official documentation to make sure it supports your operating system. After installation, look for an option to add a configuration on a page called “Configuration,” “Profiles,” or something similar.

Support for protocols such as VLESS does not necessarily mean the client can import their share links directly. Some clients support subscriptions or QR codes; others only accept sing-box JSON configurations. Before importing, check what type of content you have:

  • Subscription URL: Usually an HTTPS link. The client must support the subscription format it uses.
  • Configuration file: Usually a JSON file containing settings such as outbound connections and routing.
  • Single-node link: For example, vless://, vmess://, or trojan://. The client needs to provide an option to parse these links.

2. Import a node based on what you have

  1. Import a subscription: Open configuration management and choose “Add Remote Configuration,” “Import from URL,” or a similar option. Paste the subscription URL and give it a name. Save it, then download or update it. Check for parsing errors, then set it as the active configuration. A remote configuration option may not be able to convert subscription formats from other clients.
  2. Import a file: Save a sing-box JSON file compatible with your version to your device, then choose “Import from File” on the configuration page. Some clients let you paste configuration text. After importing, run a check or try starting it. If you see an invalid-field error, request a compatible version rather than deleting fields at random.
  3. Import a single-node link: If the interface has a “Import from Clipboard” or QR code option, copy the link and use that. If not, ask the provider for a sing-box configuration or convert it locally with a trusted tool. Avoid submitting links containing passwords or UUIDs to unknown online conversion sites.
  4. Start the connection: Select the configuration you just imported, click Start, and allow VPN access when prompted by the system. If the configuration includes a proxy group, open the relevant page and select a node. Configurations without a proxy group may not show a node list.

When getting free nodes from this site or other sources, check their format and validity as well. A successful import only means the configuration was accepted; it doesn’t mean the node is currently working. Subscription URLs may contain access credentials, so cover them up before sharing screenshots.

3. If you can’t get online after importing, troubleshoot in order

Start with the logs: If a download fails, check the subscription URL, your network connection, and whether the link has expired. If parsing fails, check the configuration format and version first. If the connection times out, try another node and make sure your device’s clock is correct.

Next, check whether traffic is going through the client. On desktop, starting the core may not automatically route browser traffic through it; you may need to enable the system proxy or TUN mode as described in the client’s documentation. On mobile, check that the VPN is connected. While troubleshooting, pause other VPNs and proxy extensions to prevent them from overriding one another.

4. How do IP, DNS, and the browser environment affect the connection?

Your exit IP can help determine whether a request is going through the proxy, but routing rules may send traffic for different sites through different exits. DNS resolves domain names. If you can access sites by IP address but not by domain name, check your configured DNS settings and the logs; don’t switch to a public DNS server without a specific reason.

Browser proxy extensions, Secure DNS, cache, and login state can also affect the results. Try disabling proxy extensions and comparing results in a private window. Private browsing mode does not automatically change your exit IP. To determine whether the connection is working, check the logs, try loading actual web pages, and use an exit-IP test. Don’t rely solely on the region a website displays.

Leave a Comment

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

中文 EN
🚀

RedGate VPN

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

立即体验 →
⚡

告别卡顿

RedGate VPN
全球高速节点

免费下载 →
Scroll to Top