This guide explains how to import nodes into sing-box, enable them after import, and troubleshoot cases where the connection succeeds but webpages still won’t load. First, identify whether you have a complete JSON configuration, a subscription URL, or a single-node link such as vless://, then choose the appropriate method to avoid pasting the link into the wrong place.
1. Check the client and node format before importing
The sing-box core and graphical clients built on it are not the same thing. Import options and subscription support vary by platform. If you’re a regular user, download a graphical client for your operating 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. Don’t download modified versions from unfamiliar file-sharing sites.
Supporting the sing-box core does not mean a client supports every subscription format. Check the client’s documentation before importing, and identify which type of content you have:
- Complete JSON configuration: Usually contains fields such as outbound and routing settings, and can be imported through the configuration file option.
- Remote configuration URL: Returns a complete configuration compatible with the client and can be added as a remote configuration. Not every “subscription link” uses this format.
- Single-node share link: For example, vless:// or trojan://. The client must explicitly support parsing these links; otherwise, you can’t use one directly as JSON.
2. Import the configuration and start the connection
- Open the client, go to “Configuration,” “Profiles,” or a similar page, and tap Add. The name varies by client, so follow the labels in your interface.
- If you have a JSON file, choose the option to import from a file. If you have JSON text, save it as a .json file first, or use the client’s clipboard import feature.
- If you have a remote configuration URL, choose the option to add from a URL, paste the full address, and download it. If you see a login page, webpage source code, or a format error, the URL may return the wrong content or require authentication.
- If you only have a single-node link, look for an “Import share link” option. If there isn’t one, ask the provider for a compatible configuration. Don’t just change the file extension, and don’t give links containing credentials to unfamiliar online conversion sites.
- After saving, select the configuration. If the interface lets you choose a node, select one, then start the connection and approve the system VPN permission. Test it by opening a commonly used website; don’t assume it works just because the status says “Connected.”
If you’re using a free node from this site, make sure its format is compatible with your client. Subscription URLs and node links may contain access credentials, so don’t share screenshots or forward them.
3. The import worked, so why won’t webpages load?
Start by checking the client logs. Configuration parsing errors are often related to fields or version compatibility. A connection timeout may mean the node is unavailable, the address can’t be reached, or the current network is restricted. Authentication failures usually mean the credentials need checking. First, get a compatible configuration again rather than changing parameters you don’t understand.
Your IP, DNS, and browser setup can affect the results, but they aren’t prerequisites for importing a node. Try these checks in order: First, quit any other VPN or proxy software, then compare the results on Wi-Fi and mobile data. Next, check which mode you’re using. In system proxy mode, some apps may not use the proxy. VPN/TUN mode generally covers more traffic, but the routing rules still determine what gets routed through it.
If the logs report a domain resolution failure, check the DNS settings in the configuration and the client’s documentation. Avoid enabling multiple DNS interception tools at the same time. Secure DNS in your browser, proxy extensions, and existing connections can also affect testing. Temporarily disable proxy extensions and try again in a private window. Private browsing does not automatically change your exit IP.
Finally, use an IP lookup page to help check your exit IP. In split-tunneling mode, the lookup site may connect directly, so don’t conclude that the connection has failed based on a single page. If the problem persists, note the client version, the format of the configuration source, and the error message with any sensitive details removed, then ask for help.