This article explains how to import nodes into sing-box, troubleshoot unrecognized subscriptions, and address inconsistent account environments after team members connect. Follow the steps in order—confirm the client, check the subscription format, import and enable it, then verify the network exit—to reduce cases where an import succeeds but you still cannot get online. Entry names may vary between clients, so follow the interface you actually see.
1. Confirm the client and node format
sing-box is a proxy core, and graphical clients that use it do not necessarily offer the same features. When installing, choose a version provided by the project’s official website or repository that is suitable for your system. Avoid modified versions from unknown sources. After opening the client, look for an entry such as “Configuration,” “Subscription,” or “Profiles.”
sing-box does not natively support every subscription format. A sing-box JSON configuration from a provider, a Clash YAML subscription, and a single-node link such as vless:// are different formats. Some graphical clients support conversion or importing by pasting, but that does not mean all clients do.
2. Import using a subscription URL
- On the node provider’s website, look for a “sing-box subscription” or import instructions for your client. Copy the full URL, including any parameters at the end.
- Open the client’s configuration management page and select “Add configuration” or “Remote configuration.” If there is only an option for local files, first check whether the client supports remote subscriptions.
- Enter a recognizable name, such as “Work configuration,” paste the subscription URL, and save it. Then download or update the configuration.
- Make sure there are no format errors, select the configuration, and start the connection. If the system prompts you for VPN permission for the first time, verify the app name before granting it.
- Open a commonly used website to check connectivity, then check your current exit IP and the client logs to confirm that traffic is actually going through the selected node.
If you use free nodes from this site, check the format and last update time first. Subscription links may contain access credentials, so don’t share them publicly or submit them to untrusted online conversion sites.
3. What to do if you only have a single-node link or a configuration file
If you have a link such as vless:// or vmess://, first check whether the client offers an “Import from clipboard” option. If it does, copy the full link and import it. If not, ask the node provider for a compatible sing-box configuration. Don’t change the link’s file extension and pass it off as a JSON file.
If you have a JSON file, select “Import file” on the configuration page. However, JSON is only a file format; its contents must still meet the requirements of the client’s core version. If you see an unsupported-field error, first update to a compatible version or obtain a configuration tailored to your client. We don’t recommend that ordinary users delete fields at random.
4. Team use and troubleshooting connection failures
Importing a node only sets up the connection; it does not ensure a stable account environment. Frequently changing exit regions, sharing an account among multiple people, or unusual activity may trigger verification by the service platform. Teams should agree on which configurations and exit regions members will use, and keep a working configuration before updating. A fixed node name does not mean the exit IP will remain unchanged.
- Subscription download fails: Check whether the URL has expired, whether it was copied in full, and whether your current network can access it.
- Parsing error: Check whether you used a Clash subscription by mistake, or downloaded a login or error page instead of a configuration.
- Connected, but webpages won’t open: First confirm that the node is working, then check for conflicts with other VPNs or system proxies and look for DNS errors. Change only one setting at a time.
- Only some apps bypass the proxy: Check the routing rules and proxy mode. Traffic handling may differ between systems and apps.
If you need help, note your system, client version, and the error message. Before sharing a screenshot, hide the subscription URL, passwords, and tokens. Follow the laws where you live and the rules of the platforms you use; a proxy connection does not guarantee that you can avoid risk controls.