This article explains how to import nodes into sing-box, enable them after import, and troubleshoot cases where the connection succeeds but websites still won’t open. It also covers how IP, DNS, and browser settings can affect the results. The sing-box client interface varies across operating systems, so before you begin, check whether you have a subscription URL, a complete configuration file, or a single node share link.
1. Identify Your Node Information and Client
Install the app from the official sing-box project channels or the official release page for the client you’re using, and check the system requirements. A desktop command-line program and a graphical client work differently; this article uses a client with a configuration management interface as an example. Menu items may be labeled “Configuration,” “Profiles,” or “Add Configuration.”
- Subscription URL: Usually starts with HTTPS and is used to download and update a configuration, but the appearance of the link does not guarantee format compatibility.
- Configuration file: Usually a JSON file containing a complete client configuration compatible with your current sing-box version.
- Share link: For example, vless://, vmess://, or trojan://. Whether it can be imported directly depends on the client.
The sing-box core is not a general-purpose subscription converter. A Clash YAML subscription or a single share link cannot be assumed to work as sing-box JSON. Ask your node provider for a configuration explicitly labeled as compatible with sing-box.
2. Import Nodes Based on What You Have
- Open the client’s configuration management page and choose to add a configuration. If this is your first time using the app, keep the default settings.
- If you have a subscription URL, choose “Remote Configuration” or “Add from URL,” paste the full URL, and save it. Click Download or Update and check for format errors. If a webpage appears or parsing fails, check that the URL is correct and the format is supported.
- If you have a JSON file, choose “Local Configuration” or “Import from File,” select the file, and save it. A JSON file containing only node outbound sections may not work on its own, so ask for a complete client configuration.
- If you only have a single share link, first check whether the client supports importing by pasting or scanning a QR code. If there’s no such option, don’t paste the share link into the remote configuration field; ask the provider for a compatible configuration.
- Select the configuration you just imported and start the connection. Grant VPN or network extension permissions if prompted by the system. If the configuration provides a node selection group, choose the node you want to use.
Successful import only means the configuration was accepted; it doesn’t guarantee that the node is working. Try opening a regular HTTPS website first, then test the service you’re targeting. When using free nodes from this site, also check the format, last update, and availability. Don’t share your subscription URL publicly.
3. If You Can’t Connect, Check for IP, DNS, and Browser Issues
Start by checking the logs: configuration parsing or field errors usually point to format or version compatibility issues, while connection timeouts call for checking your local network, node status, and system time. Back up your configuration before making changes, and avoid changing multiple settings at once.
Your IP determines the network exit point websites see. If your exit IP hasn’t changed after connecting, check that the client has enabled a VPN, TUN, or system proxy mode appropriate for your operating system, and that routing rules aren’t sending the test website directly. A system proxy does not guarantee that all apps will use the proxy.
DNS resolves domain names. If websites won’t open by domain name or the logs report a resolution failure, first use a compatible configuration recommended by your provider and check that the DNS and routing rules work together. Don’t blindly enter unfamiliar DNS addresses.
Browser extensions, separate proxy settings, and secure DNS can also affect the results. You can temporarily disable proxy extensions and compare results in a private window; private browsing does not hide your exit IP. Changing nodes does not automatically clear cookies, account state, or your browser fingerprint, so website verification prompts or region notices don’t necessarily mean the import failed.