This article explains how to import nodes into sing-box, connect after importing, and troubleshoot cases where webpages still won’t load in your browser. First, distinguish between node links, subscription URLs, and sing-box configuration files. Then import them using a method supported by your client, and finally check your IP, DNS, and browser settings to avoid mistaking an incompatible format for a broken node.
1. Before importing: check your client and node format
sing-box is a proxy core, and the menus and import options vary between graphical clients on different operating systems. Install a client suited to your system from the project’s official release page or a trusted app store, and note its version. If the desktop version is a command-line program, it won’t have a graphical “Add subscription” button.
A node link is not the same as a sing-box configuration. Content beginning with vless://, vmess://, or trojan:// is usually a share link for a single node. A subscription URL is generally an HTTPS link, but its response might contain a node list, a Clash configuration, or sing-box JSON. Don’t judge compatibility by the URL alone; check the format specified by the provider.
2. Choose an import method based on the configuration source
- You have a sing-box JSON file: Open the client’s “Configuration” or “Profiles” page, choose the option to add a configuration or import one from a file, then select the downloaded JSON file. Menu names vary by version.
- You have a sing-box configuration subscription: If your client supports remote configurations, choose the option to add one by URL, paste the full address, and save it. Update it manually once, confirm the download succeeded, then set that configuration as the active one.
- You only have a single-node link: First check whether the client supports importing from the clipboard or parsing protocol links. If it does, copy and import the complete link. If not, ask the provider for a compatible configuration. Don’t paste the link directly as JSON.
- You only have a subscription in another format, such as Clash: Don’t simply change the file extension. Get the sing-box format if possible. If you need to convert it, use a trusted local tool and check that protocol, TLS, and other settings have been preserved.
Subscription URLs may contain access tokens. Don’t submit them to unfamiliar online conversion sites or post full links in public comments. When using free nodes from this site, check the format details and last updated date as well. A successful import doesn’t mean a node will always be available.
3. How to confirm the connection is working after import
Select the configuration and start the connection. On mobile, you’ll usually be prompted for VPN permission. On desktop, enable the system proxy or TUN mode as instructed by your client. Test with just one connection method to avoid conflicts with other VPN or proxy software.
Open a familiar website in your browser, then use a trusted IP lookup page to check whether your exit IP matches the selected routing rules. A changed exit IP doesn’t mean all traffic is going through the proxy. Split-routing rules may send some sites directly, and DNS traffic may take a different route. The browser’s secure DNS, proxy extensions, and existing connections can also affect the results.
4. How to troubleshoot import or connection failures
- Parsing error: Check that the format is supported, the link was copied in full, and the subscription response isn’t a login or error page.
- Unsupported field: Check the client version and configuration requirements. Update to a stable release or ask for a compatible configuration. Don’t delete fields at random.
- Connection timeout: First confirm that your local network is working, then try another node and check the logs for timeout or TLS errors.
- Connected, but webpages won’t load: Confirm that the system proxy or TUN mode is enabled, quit other proxy software, and restart the browser. If the logs show a DNS resolution error, check the DNS settings using your client’s documentation.
Change only one setting at a time while troubleshooting, and keep a copy of the original configuration. If you need help, provide your operating system, client version, and a redacted error message. Don’t share subscription tokens, passwords, or full node details.