This article addresses a common question: “How do I import nodes into sing-box?” Once you have a subscription link, a node sharing link such as VLESS, or a JSON configuration, where should you import it? If you can’t connect afterward, how can you tell whether the issue is with the node, IP, DNS, or browser environment? Buttons and features vary between sing-box GUI clients, so follow the instructions for the interface you’re using.
1. Check what you have before importing
First, install a client that suits your system from the project’s official channels or a trusted app store. Confirm that it uses the sing-box core and check whether it supports subscription management. Using the sing-box core does not mean a GUI client supports every subscription format, so don’t assume subscriptions from other software can be used as generic configurations.
- Subscription link: Usually an HTTPS address. Check whether the provider says it supports your client or the sing-box format.
- Node sharing link: For example, text beginning with vless://, vmess://, or trojan://. The client must be able to parse the link.
- Configuration file: Usually in JSON format and includes settings such as outbound connections and routing. It should be compatible with your version of the core.
Check the format and update date of any free nodes provided by this site; free resources may not always be available. Don’t submit links containing subscription tokens to untrusted online conversion sites.
2. Import nodes based on the content type
- Import a subscription link: Open the client’s “Configuration,” “Subscriptions,” or “Profiles” page, choose the option to add a remote configuration, enter a name, and paste the link. Save it, then update it. If you get a format error, first check that you copied the full address, then confirm that the subscription is compatible with your client.
- Import a local configuration: Save the sing-box JSON file from the provider to your device, then select the option to import from a file on the configuration page. Some clients let you paste configuration text; once imported, validate it before enabling it.
- Import a single node: If the interface offers an option to “Import from clipboard” or scan a QR code, copy the sharing link and follow the prompts. If you don’t see this option, don’t paste the sharing link directly into the JSON editor. Ask the provider for a compatible configuration instead.
- Select the configuration you just imported and start the connection. When prompted the first time, grant the system’s VPN permission. If the configuration includes a node selection group, open the relevant group and select a node. A successful subscription update does not mean the proxy is running.
3. Check your IP, DNS, and browser after connecting
Successfully importing a configuration doesn’t mean your traffic is going through the proxy. First, open a regular webpage to confirm your basic internet connection is working, then test the target site. If the client uses routing rules, some sites may still use your local network. So, seeing your local public IP doesn’t necessarily mean the import failed; check the logs to see which rule the request matched.
If you get a domain resolution error, first check your system’s network connection, then see whether the DNS settings in the configuration are compatible with your current version. Your browser’s secure DNS, built-in proxy, or extensions may also change the route your traffic takes. Try temporarily disabling proxy extensions and testing in a private window as well. Private browsing can reduce interference from cache and extensions, but it won’t hide your public IP.
4. Troubleshoot import or connection failures
Try these steps in order: update the client, check the format, get a fresh subscription, check your device’s time, switch networks, and review the logs. If configuration validation reports an unknown field, check version compatibility. A connection timeout requires further investigation of the network or node status; it doesn’t necessarily indicate a DNS issue. Avoid running multiple VPNs at the same time. When sharing error reports, redact sensitive information such as subscription addresses, UUIDs, and passwords.