This article answers common questions about “how to import nodes into sing-box”: after receiving a subscription URL, node link, or JSON file, where should you import it, and what should you check if the import succeeds but you still can’t access the internet? It also explains how exit IPs, DNS, and browser settings relate, so you don’t assume every website issue means the node is down.
1. Check the client and node format first
sing-box is a proxy core, and import options and menus vary between graphical clients. Download the installer for your system from the project’s official website or repository, and make sure your system is supported. If you only have the command-line program, you won’t see graphical options such as QR code scanning or subscription management. Most users should choose a graphical client that clearly uses the sing-box core and is still maintained.
Support for the sing-box core doesn’t mean support for every subscription format. Before importing, identify what you received:
- Subscription URL: Usually an HTTPS link. Check which format the provider says it uses.
- Single-node link: For example, vless://, vmess://, or trojan://. Whether it can be imported directly depends on the client.
- Complete JSON configuration: Usually includes settings such as inbounds, outbounds, and routing; it’s not just a few parameters with a server address.
2. Import nodes based on their format
- Using a subscription URL: Open the client’s “Configuration,” “Profiles,” or “Subscription” page, choose the option to add a remote configuration, paste the URL, and save it. Then download or update it. If you see a format-not-supported message, first ask the provider whether a sing-box format is available. Simply changing the file extension to JSON won’t help.
- Using a JSON file: Choose “Import from file” or a similar option, then select the configuration file. If the client supports importing from the clipboard, you can also copy the complete contents and add them. If validation fails, check whether the file downloaded as a webpage and whether the configuration is compatible with your core version.
- Using a single-node link: Do this only if the client has an “Import link” or QR code scanning option. If it doesn’t, ask the provider for a compatible configuration or subscription. Don’t paste the node link directly into the remote configuration URL field.
- Enable the configuration: Select the configuration you just imported, authorize the VPN connection or enable the system proxy as prompted, and start the connection. If there’s a node selection page, choose an available node and test a webpage.
If the free nodes page on this site provides format instructions, follow them to choose the right option in your client. Don’t submit subscription URLs containing tokens to untrusted online conversion websites. Before sharing a screenshot of an error, also hide the URL and any credentials.
3. After importing, check your IP, DNS, and browser
A successful import doesn’t mean your traffic is going through the proxy. First check that the client is running and that system proxy or VPN mode is enabled. Visit a trusted IP lookup page and see whether your exit IP has changed. In split-tunneling mode, different websites may use different exits, so a single lookup can’t confirm that all traffic is being proxied.
If a domain won’t open or some websites fail to load, check the logs for DNS resolution timeouts. Keep the DNS settings in the original configuration while troubleshooting, rule out conflicts with other VPN or proxy tools, and then make changes according to the client’s documentation. A browser’s Secure DNS setting or proxy extension may change the resolution or connection path, but its on/off status alone doesn’t tell you whether there’s a DNS leak.
If only one browser is affected, compare results in a private window or another browser, and temporarily disable proxy extensions. Cookies, account region, and location permissions can also affect the region a website displays; this doesn’t mean your exit IP hasn’t changed.
4. Troubleshoot connection failures in order
Check the following in order: can the subscription be downloaded, can the configuration be validated, can the connection start, and can webpages be accessed? If the subscription fails, check your network and whether the URL has expired. If the configuration fails, check its format and version. If the connection times out, try updating the subscription, switching nodes, or changing networks. If the problem persists, check the specific error in the logs and note the client version and a redacted error message before asking for help. There’s no need to reinstall repeatedly.