This article answers a common question: how do you import nodes into sing-box? Once you have a subscription URL, JSON configuration, or node link such as vless://, how can you tell whether it can be imported directly? And if websites won’t load after connecting, how should you check your IP, DNS, and browser settings? Import options vary by platform and client version, so the steps below follow the order you’re likely to use them.
1. Check the client and node format first
sing-box is a proxy engine, and import options vary between graphical clients. Install a client suitable for your device from the project’s official release page or a trusted app store. On first launch, grant VPN or network-extension permissions when prompted.
Using the sing-box engine doesn’t mean a client supports every subscription format. Before importing, check the client’s documentation to confirm whether it supports remote configurations, full JSON files, or single-node share links.
- Full JSON configuration: Usually includes inbound, outbound, and routing settings, and can be added from a file or as text.
- Subscription URL: Check that it returns a configuration format supported by your client. The name of the URL alone isn’t enough to tell.
- Links such as vless://, vmess://, and trojan://: Only clients that can parse share links can add these directly.
2. Import and start the connection
- Open the client’s “Configuration,” “Profiles,” or similar page, then select Add. The exact label depends on your version.
- If you have a compatible subscription, choose the remote configuration or URL import option. Paste the full address, enter a name you’ll recognize, and save it. Then download or update the configuration.
- If you have a full JSON file, choose the option to import from a file or paste the configuration. If you see a syntax, field, or version error, first check that the configuration is compatible with your sing-box version. Don’t delete fields mentioned in the error at random.
- If you only have a single-node link, check whether the client offers an import option for clipboard contents or share links. If not, ask the provider for a compatible configuration rather than changing the link’s extension to .json.
- Select the configuration you just added and enable the connection. For your first test, use the client’s default routing mode and make sure the system proxy or VPN/TUN mode is enabled.
A successful import doesn’t mean your traffic is going through the proxy. Test with a regular webpage, then check the client’s logs and connection records. For free nodes offered on this site, check the format and availability first. Free resources may stop working and shouldn’t be used for sensitive tasks.
3. Check your IP, DNS, and browser after connecting
An IP-checking page shows the exit IP for that particular request; it doesn’t necessarily mean every app is using the same exit. With rule-based routing, it’s normal for domestic websites to connect directly while some other sites go through the proxy. Check the destination and logs together rather than relying on a single IP-checking page.
If the logs keep showing domain resolution failures or DNS timeouts, try switching between mobile data and Wi-Fi, then check whether the configuration includes compatible DNS settings. Changing DNS is not a universal fix. An unavailable node, missing permissions, or an incorrect system clock can also cause connection failures.
Your browser’s Secure DNS setting, separate proxy extensions, and old cache data may affect test results. You can temporarily disable proxy extensions, try a private window, and test with another browser. Note your original settings before making changes, and restore them once you’ve finished troubleshooting.
4. If it still fails, troubleshoot in order
First, confirm that the subscription updates and that the configuration is selected. Then check VPN permissions and make sure other proxy software isn’t causing a conflict. Next, try another node or network. When reviewing the logs, distinguish between “configuration parsing failed,” “connection timed out,” and “certificate error”—don’t assume every issue is caused by DNS. When asking for help, include your system, client version, and a redacted error message. Don’t share your full subscription URL, token, or node password publicly.