This article explains how to import nodes into sing-box, troubleshoot unrecognized subscriptions, and prevent inconsistent egress when team members use the same setup. Follow these steps in order: confirm the client, import the configuration, verify the connection, and establish consistent usage rules. This helps reduce issues caused by format mismatches or accidentally switching routes. Note that a successful node connection does not guarantee account stability: platforms may also consider the device, login location, and user activity.
1. First, identify the type of node information you have
sing-box is a proxy core. Graphical clients for different systems may have different import options and support different formats. Download the software from the project’s official website, official release page, or a trusted app store, and make sure its documentation explicitly states that it supports sing-box. Don’t assume that another client uses the same menu names.
- Single node link: Usually begins with vless://, vmess://, trojan://, or a similar prefix. Whether you can import it directly depends on the client.
- Subscription URL: Used to retrieve and update configurations, but the content may be Clash YAML, a list of links, or sing-box JSON. These formats are not interchangeable.
- JSON configuration file: Must meet the requirements of your current sing-box version. Having the same file extension does not guarantee compatibility.
Check which formats your client supports before choosing an import method. If the provider only offers a Clash subscription, ask whether they have a sing-box configuration compatible with your client. Simply changing the file extension to .json will not work.
2. Import and start the client based on the type of information you have
- Open the client and look for “Configuration,” “Profiles,” or a similar option. If there is no graphical interface, first check the documentation for loading configurations in your application.
- To import a subscription, choose an option such as “Add from URL,” paste the full address, give it a name, save it, and update it. If parsing fails, first check the format returned by the subscription instead of refreshing it repeatedly.
- To import a file, select the local JSON file. To import a single link, use the clipboard or QR code option only if the client explicitly supports it. If it doesn’t, ask the provider for a compatible configuration.
- Select the new configuration and review the node or outbound selection options. For your first test, manually select a route to avoid confusion caused by automatic selection.
- Start the connection and grant VPN or network extension permissions if prompted by the system. Open a regular webpage, then visit the target service to confirm that both the network and the service are working.
Treat subscription URLs and configuration files as sensitive information. Don’t submit them to unfamiliar online conversion sites or post URLs containing tokens in public group chats. The free nodes on this site can be used for basic connectivity tests, but don’t assume that they will provide a consistent egress over the long term.
3. How teams can reduce account environment changes
A node affects some characteristics of your network egress, but the same node name does not guarantee a fixed egress IP: the provider may change routes, and automatic policies may switch egress. Teams should record each member’s client version, configuration name, selected route, and update time so they can reproduce issues during troubleshooting.
For services that require a persistent login, try to keep the device, browser configuration, and usual region consistent, and avoid switching routes repeatedly during a single session. Follow the platform’s rules on account sharing. For collaboration, use the platform’s official member permissions rather than relying on a proxy to bypass account restrictions.
4. What to do if the import succeeds but you can’t connect
First, update the subscription and check that it hasn’t expired. Then verify the device’s time, system network permissions, and whether another VPN is running at the same time. If the connection starts but webpages won’t load, check the logs for DNS, timeout, or handshake errors. If only the target service fails, check its regional restrictions and service status. Don’t change several settings at once: adjust one setting at a time and test again.
If you need help, provide the client version, system version, and a redacted error log. Hide subscription tokens, passwords, and node authentication details; never share the full configuration publicly.