This article explains how to import nodes into sing-box, why a subscription may fail to connect after being added, and how teams can reduce frequent changes to their account environment. First, confirm whether you installed the sing-box command-line program or a graphical client based on sing-box. The import methods differ, and menu names may vary between mobile and desktop versions.
1. Before importing, check what you received
A sing-box configuration, a subscription URL, and a node share link are not the same thing. Don’t paste everything directly into the configuration editor.
- Full configuration: Usually a JSON file containing outbound and routing settings. It must be compatible with your client version.
- Subscription URL: Usually starts with HTTPS, but the returned format may be Clash, sing-box, or another format. Check the provider’s instructions.
- Single-node link: For example, vless://, vmess://, or trojan://. The client must explicitly support parsing it; you can’t use it directly as a native JSON configuration.
For free nodes on this site, choose the format indicated on the page. Don’t submit URLs containing subscription tokens to untrusted online conversion sites; they may serve as your subscription credentials.
2. Importing through a graphical client
- Install the client from the project’s official release page or a trusted app store, and check which operating systems, subscription formats, and configuration methods it supports.
- Open “Configuration,” “Profiles,” or a similar page, and choose to add a profile. If you received a compatible subscription, choose remote configuration and paste the URL. If you received a full JSON file, import it as a local file.
- If you only have a single-node link, look for “Import from clipboard” or “Scan QR code.” If these options aren’t available, don’t keep trying; ask the provider for a compatible configuration.
- Give the configuration a recognizable name and save it, then update it. Make sure there are no parsing errors before setting it as the active configuration.
- Click Start, allow the VPN connection or related network permissions when prompted by the operating system, then select an available outbound to test.
Successful import doesn’t mean traffic is already being routed through the client. Desktop clients may also require you to enable the system proxy or TUN mode; check the client’s documentation. On mobile, make sure the VPN is actually running. Don’t run multiple proxy tools at once during initial testing, as this can cause routing conflicts.
The command-line version doesn’t have a standard “paste subscription” button. First obtain a compatible full configuration, then validate it with sing-box check -c config.json. If validation passes, start it according to the official documentation. Don’t save a share link directly as a JSON file.
3. Troubleshooting import or connection failures
If you see a “format error,” first check the subscription type and version compatibility. If the subscription won’t update, check that the URL is complete and hasn’t expired, and that your current network can reach it. If the configuration starts but you can’t open webpages, check the selected node, system time, proxy permissions, and DNS-related logs in that order. If you encounter a certificate error, don’t disable verification right away; first confirm the configuration source and device time. Before sharing screenshots or logs, hide tokens, passwords, and node credentials.
4. How does team use relate to account environment stability?
Importing nodes by itself does not guarantee a stable account environment. Frequently switching exit IPs, regions, and devices may trigger security checks on some platforms, but whether this happens depends on the platform’s rules. Teams can agree on relatively consistent regions and configurations for authorized members, and avoid switching connections repeatedly just for testing. Continue using multi-factor authentication as usual; a proxy is no substitute for account security measures.
We recommend standardizing client versions and update procedures. Each team member should use their own authorized credentials, and subscription details should not be shared in group chats. Free nodes may vary in availability and exit locations, so they should not be relied on as the sole connection method for critical operations.