This article addresses common questions about importing nodes into sing-box: what to do with a subscription URL, a VLESS link, or a JSON configuration, and how to tell whether a problem is caused by the node, IP, DNS, or browser environment when the import succeeds but webpages still won’t load. Button names may vary between clients, so the steps below are organized by configuration type rather than tied to a particular version’s interface.
1. Check the client and node format
sing-box is a proxy core, and graphical clients that use it may not offer the same import options. First, install a client suitable for your system from the project’s official channels and check its configuration guide. Don’t install unfamiliar software just because its name looks similar.
- Subscription URL: Usually an HTTPS link, but the returned content may be sing-box JSON or another subscription format.
- Single-node link: For example, content starting with vless://, vmess://, or trojan://, which requires a client that can parse it.
- JSON configuration: Usually includes settings such as outbound and routing. Make sure it’s a complete configuration, not just a node fragment.
Support for the sing-box core does not necessarily mean that a client can directly import every share link or Clash subscription. If you get an unsupported-format message, ask the node provider for a compatible configuration or use a trusted local conversion tool. Don’t submit a subscription containing credentials to an unfamiliar online converter.
2. Import the configuration by type
- Open the client’s configuration management page, look for “Configuration,” “Profiles,” or a similar option, and add a configuration.
- If you have a compatible subscription, choose the option to add it from a URL, paste the full address, and save it. Then download or update it. Make sure not to omit any tokens or parameters in the URL.
- If you have a complete JSON file, choose the file import option. If the client supports pasting a configuration, you can also copy and import the entire contents. If validation fails, first check that you copied all the braces and that the configuration is compatible with your core version.
- If you only have a single-node link, check whether the client supports importing from the clipboard, scanning a QR code, or parsing a share link. If it doesn’t, don’t paste the link directly into a JSON editor.
- Select the configuration you just imported, choose a node if needed, and start the connection. On first launch, allow the client to add a VPN configuration when prompted by your system. On desktop, enable the system proxy or TUN as instructed by the client, and avoid running other proxy software at the same time.
After importing, make sure the configuration is selected and the service is running before testing a webpage. A failed subscription update doesn’t necessarily mean the node is down; the URL may have expired, the network may be unable to reach the subscription site, or the response may be a login page.
3. Check your IP, DNS, and browser after connecting
First, visit a regular HTTPS site, then check your exit IP using a trusted IP lookup page. If your IP hasn’t changed, check the system proxy, TUN permissions, and routing rules first. In split-tunneling mode, some sites may connect directly as expected, so don’t judge by just one page.
If the logs repeatedly show domain name resolution failures, check your DNS. Restore the client’s default DNS settings first, then temporarily disable other DNS tools and try again. Don’t enter an unfamiliar DNS server without checking it. Secure DNS settings in your browser and proxy extensions may conflict with the client, so you can temporarily disable them to compare results.
If only one browser can’t open a site, try an incognito window or another browser to rule out cache, extensions, and an outdated login session. Browser language, time zone, and cookies don’t determine whether a node can be imported, but they may affect how a site appears and how its risk controls respond. There’s no need to change these settings at random while troubleshooting the connection.
4. What to do if it still doesn’t work
Troubleshoot in this order: update the subscription, check configuration validation, confirm that traffic is being routed through the proxy, and review the error logs. Before sharing logs, redact subscription tokens, passwords, and node addresses. If you’re using the free nodes on this site, check their format and validity first. Node availability can change, so a continuous connection cannot be guaranteed.