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

This article explains how to import nodes into sing-box. First, identify whether you have a subscription URL, a single node link, or a JSON configuration. Then import it using a method supported by your client, and check your IP, DNS, and browser settings to avoid being “connected but unable to open websites.” Menu names vary across platforms and client versions; the steps below use common graphical clients as examples.

1. Identify the node format before importing

sing-box is a proxy core, and clients that use it may not support the same import methods. Being able to copy a node link does not mean your client can recognize it directly. Check the client’s documentation first, then identify the format of the content you received:

  • Subscription URL: Usually begins with https://, but the content may be a sing-box configuration, a Clash configuration, or a list of node links. The URL alone does not tell you whether it is compatible.
  • Single node link: Commonly begins with vless://, vmess://, trojan://, or ss://. Your client must explicitly support parsing the link.
  • JSON file: It should be a complete client configuration compatible with your current sing-box version. A snippet containing only node parameters usually cannot run on its own.

Install the client from the project’s official page or a trusted app store. If you use this site’s free nodes, check their format and last updated date first; free resources may become unavailable. Don’t post your personal subscription URL in public comments.

2. Import based on the resource type

  1. Open the client and go to “Configuration,” “Config files,” or a similar page, then tap the add button. On first use, follow the system prompts to allow a VPN connection.
  2. If you have a compatible subscription, choose “Remote configuration” or “Import from URL,” paste the full address, enter a descriptive name, and download or update the configuration.
  3. If you have a JSON file, choose “Import from file” and locate the downloaded file. If the import fails, keep the original file and check the client’s message. Don’t delete fields you don’t understand.
  4. If you only have a single link, look for “Import from clipboard” or “Import share link.” If neither option is available, ask the provider for a compatible configuration. Don’t paste the link directly into a JSON editor.
  5. Select the imported configuration and run a check or try starting it. If the interface provides proxy groups, select a node, then enable the system proxy or VPN/TUN routing and test a webpage.

Whenever possible, use the sing-box-compatible configuration provided directly by the provider. Changing a file extension does not convert it between configuration formats. If you need to convert it, don’t submit links containing passwords or UUIDs to untrusted websites.

3. Troubleshooting when you’re connected but can’t access websites

Check the logs first: Configuration parse errors usually relate to the format, fields, or version; connection timeouts may be caused by an unavailable node, network restrictions, or an unreachable address; certificate errors warrant checking your device’s time and the source of the configuration. We don’t recommend bypassing these errors by disabling certificate verification.

Next, confirm that traffic is actually going through the client. Before testing, turn off other VPNs and duplicate proxy tools. System proxy mode may not cover every app, and VPN/TUN mode requires system authorization. Open a trusted public IP lookup page. If your IP hasn’t changed, that doesn’t necessarily mean the import failed—split-tunneling rules may be sending that site directly through your network.

DNS determines how domain names are resolved; it is not the same as your proxy’s exit IP. If your IP has changed but some domains won’t load, check the DNS settings in your configuration and the logs. Don’t make random changes to DNS settings in your system, client, and browser all at once. A browser’s own proxy settings, extensions, or secure DNS may also change how traffic is routed. Try temporarily disabling related extensions, then compare the results in another browser.

Finally, a proxy connection does not automatically clear cookies, sign-in status, or browser location permissions. So a website’s displayed region may not depend solely on your exit IP. Troubleshoot in this order—whether the configuration loads, whether a connection is established, whether traffic is being routed through the client, then DNS and browser settings—to pinpoint the problem more easily.

Leave a Comment

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

中文 EN
🚀

RedGate VPN

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

立即体验 →
⚡

告别卡顿

RedGate VPN
全球高速节点

免费下载 →
Scroll to Top