This article answers common questions about “how to import nodes into sing-box”: what to do with a subscription link, a single-node link, or a JSON configuration, and how to check your exit IP, DNS, and browser settings if the import succeeds but websites still won’t load. Button names may vary between clients, so refer to the interface in your current version.
1. Check your client and node format first
sing-box is a proxy core, and graphical clients that use it don’t necessarily offer the same import options. Install a client compatible with your system from the project’s official website or release page. When you first launch it, follow the prompts to allow it to add a VPN configuration. Avoid running multiple VPNs at the same time, as they may compete for the system’s network interface.
A node link is not the same as a complete configuration. There are three common types of materials: a subscription URL beginning with https, a single-node share link beginning with something like vless://, and a sing-box JSON configuration file. Whether a client can recognize them directly depends on whether it supports the corresponding parsing function.
2. Import based on what you have
- Subscription link: Go to the “Configuration,” “Profiles,” or “Subscription” page, choose to add a remote configuration, paste the link, and save it. Then update it. It will load properly only if the client supports that subscription format or the link returns a compatible sing-box configuration.
- Single-node link: Look for “Import from clipboard” or “Add node.” If there’s no such option, don’t paste the share link directly into the JSON editor. Ask the provider for a compatible configuration, or use a client that explicitly supports the format.
- JSON file: Select “Import local file,” open the file, and save it. If you only have the configuration text, first save it as a .json file as required by your client. If you see a version or field error after importing, check that the configuration is compatible with your sing-box version.
- Select the newly imported item from the configuration list, start the connection, and authorize the VPN. If the interface offers proxy groups, open one and select an available node. Finally, test by opening a webpage—don’t assume you’re connected just because the status says “Running.”
Free nodes provided by this site should also be imported according to their actual format, and their availability may change. Subscription URLs usually contain access credentials, so don’t share screenshots or forward them, and don’t submit them to untrusted online conversion sites.
3. Import succeeded, but why won’t websites load?
Start by checking the client logs. Parsing failures or unknown fields usually mean you should check the configuration format and version. For timeouts or connection refusals, try updating the subscription, switching nodes, switching between Wi-Fi and mobile data, and confirming that your system clock is correct. Change only one thing at a time while troubleshooting so you can identify the cause.
Your exit IP can help determine whether traffic is going through the proxy as expected. After connecting, check it using a trusted IP lookup page. In split-tunneling mode, different websites may use different exits, so an unchanged IP doesn’t necessarily mean the entire configuration has failed. If needed, temporarily switch to the client’s global proxy mode for comparison.
DNS handles domain name resolution. If the logs keep showing resolution errors, first restore the DNS settings recommended by the client and check for conflicts with your system’s encrypted DNS or other network tools. Don’t blindly layer multiple settings on top of one another.
4. What if only the browser is acting up?
If other apps are working normally, first check the browser’s proxy extensions, secure DNS settings, and cache. Try disabling proxy extensions and then test again. On desktop, some apps may not follow the system proxy when it’s enabled; TUN mode usually requires additional permissions. Changing your browser fingerprint won’t fix a failed node connection—first confirm that the proxy connection is working, then troubleshoot sign-in status or website compatibility.