This guide explains how to import nodes into sing-box, what to do when a subscription cannot be added, and how teams can reduce changes to their account network environment. First confirm which configuration formats the client accepts, then import the configuration, enable it, and check the outbound connection. This is more effective than repeatedly switching nodes. The steps below use a sing-box client with a graphical interface; menu names may vary by platform and version.
1. Understand the difference between nodes, subscriptions, and configurations
sing-box is a proxy core, and graphical clients do not all support the same import methods. A node link that can be copied may not be directly importable into your current client, so first check which formats are supported on the “Add Configuration” page.
- Single-node links: Usually start with vless://, vmess://, or trojan:// and require a client that can parse them.
- Subscription links: Usually HTTPS URLs, but the returned content may be a Clash YAML file, a node list, or a sing-box configuration. You cannot determine the format from the URL alone.
- sing-box configurations: Usually JSON files. In addition to node details, they may include routing and DNS settings, so only use files from trusted sources.
When installing a client, use official project channels where possible and check the system requirements. The free nodes on this site can be used for connection tests, but their availability may change, so they are not suitable as the sole outbound connection for critical team operations.
2. Import a node or subscription by format
- Open the client, go to “Configuration,” “Profiles,” or a similar page, and add a new entry. Keep your existing working configuration so you can restore it if the import fails.
- If you have a complete sing-box configuration file, import it as a local file. If the subscription URL returns a compatible configuration, choose the remote configuration option, paste the URL, and download it.
- If you only have a single-node link, first check whether the menu offers “Import from Clipboard” or “Scan QR Code.” If it does not, ask the provider for a compatible configuration. Do not simply change the link into a JSON file.
- Name the configuration, for example, “Operations Team – Backup Egress,” then save it and run validation or update it. If you see an unknown field or parsing error, first check the configuration format and client core version.
- Select the configuration and start the connection, granting permission for the VPN or network extension if prompted by the system. If the client supports it, select the desired node, then visit a regular website to check that it loads properly.
Do not submit subscription links to unfamiliar online conversion sites. A link may contain access credentials. If conversion is necessary, use a compatible subscription provided by the provider or a trusted local tool.
3. Troubleshooting when the import succeeds but there is no internet access
First determine whether the problem is a failed configuration download or a failed node connection. For a failed download, check that the URL is complete, the subscription has not expired, and the download network is working. For a failed node connection, check the node status, device time, and error messages in the logs. Change only one setting at a time so that you can identify the cause instead of changing the node, DNS, and routing all at once.
If the client shows that it is connected but websites will not open, temporarily disable other VPN or proxy tools and check for conflicts. Then test a different trusted node for comparison. Before sharing logs, redact subscription URLs, UUIDs, passwords, and other sensitive information.
4. How does team use relate to account stability?
Importing a node does not automatically stabilize an account’s network environment. Platforms may assess risk based on a combination of outbound IP address, changes in region, device status, and login activity. Frequently switching outbound connections across regions may lead to additional verification, but using a fixed node cannot guarantee that an account will avoid security checks.
Teams should keep each member’s device and usual outbound region as consistent as possible, and record configuration sources and update times. Test changes with a small group before rolling them out, and keep a configuration for rollback. Do not share account passwords among multiple people or distribute subscriptions indiscriminately. Use the platform’s member permissions and two-factor authentication where available, and comply with local laws and terms of service.