This article answers common questions about importing nodes into sing-box: which option to choose when you have a node link or subscription, what to do if importing fails, and how to troubleshoot mismatches between your IP, DNS, and browser behavior after connecting. sing-box client interfaces vary across platforms, so follow the steps for your configuration type below rather than looking for an exact match to a particular button.
1. First, check whether your content can be imported directly
sing-box is a proxy core; not every client includes subscription conversion. First, install a client suited to your operating system from the project’s official channels or a trusted app store, then check which import formats it supports.
- Complete sing-box JSON configuration: You can usually add this from a file or remote address in a page such as “Configuration” or “Profiles.”
- Subscription link: First check whether the provider specifies the sing-box format or a Clash or generic node subscription. The latter two may not work directly.
- Single-node links such as vless://, vmess://, and trojan://: These can be imported directly only by clients with the corresponding parsing feature. They cannot be loaded as JSON files.
Being able to copy a link does not mean its format is compatible.If the page only offers “Import from file” and “Remote configuration,” do not paste an arbitrary node string there. First, ask the provider for a configuration compatible with your client. Before using a conversion tool, verify that it is trustworthy to avoid exposing your subscription token.
2. Import and connect step by step
- Open the client’s configuration management page and choose to add a configuration. If this is your first time, keep the default settings to avoid changing routing, DNS, and other options at the same time.
- If you have a JSON file, choose to import from a file. If you have a compatible remote configuration URL, choose to add it remotely and paste the full link. Make sure it contains no spaces, quotation marks, or line breaks.
- Give the configuration a recognizable name, save it, and download, update, or check it. If you see a parsing error, check the format first; do not repeatedly click Connect.
- Select the configuration you just imported. If the interface includes a node selector, choose an available node. A configuration with only one outbound may not have a node list.
- Start the connection and allow any VPN or network extension permissions requested by the system. On desktop, enable the system proxy or TUN as instructed by the client; you usually do not need to enable both at once.
- Visit a regular website and a website that requires a proxy, then check the client’s connection logs to confirm whether traffic is routed through the proxy.
A successful import only means the configuration was accepted; it does not guarantee that the node is online.Remote configurations should also be updated regularly. If a subscription URL has expired, return to the provider’s page to get a new one. For free nodes on this site, follow the format specified on the page; long-term availability is not guaranteed.
3. Troubleshooting import failures and connection issues
Messages such as “unknown field” or “unsupported configuration item” usually indicate an incompatible configuration format or client core version. Update to the latest stable client first, then get a configuration suited to that version. If a remote download fails, check whether the link has expired, whether it redirects to a login page, and whether your current network can access the subscription URL.
If the configuration is valid but you cannot connect, check the system time, confirm that VPN permissions are allowed, check for conflicts with other proxy software, and try a different node. In the logs, look for authentication failures, timeouts, or DNS resolution errors. Do not share complete logs that contain passwords, UUIDs, or subscription tokens.
4. Why your IP, DNS, and browser may not match
Your exit IP depends on the route your traffic actually takes. In split-tunneling mode, domestic websites may show your local IP while proxied websites show the node’s IP; this can be normal. DNS handles domain name resolution, so a single IP lookup page is not enough to determine whether DNS is behaving as expected.
Your browser environment does not reflect your proxy connection status on its own.Browser secure DNS, proxy extensions, cache, and login status can all affect test results. To troubleshoot, first disable other proxy extensions and retest in a private window, then compare the client’s routing and DNS settings. Do not disable certificate verification just to pass a test; it is safer to make adjustments after confirming the exact error.