This article explains how to import nodes into sing-box, troubleshoot subscriptions that the client can’t recognize, and address frequent changes to account environments after team members connect. First, identify the format of the node information you received. Then import it using a method supported by your client, and finally check your actual outbound IP. Menus and features vary across sing-box GUI clients, so follow the instructions for the app you’re using.
1. Before importing, identify what you have
sing-box is a proxy core that most users access through a GUI client. Install it from the project’s official channels or a trusted app store, and confirm that the app explicitly supports sing-box configurations. Don’t install an app based on a similar name alone.
- Single-node link: Usually begins with vless://, vmess://, trojan://, or a similar scheme. The client must support parsing that link type.
- Subscription URL: Used to retrieve and update configurations, but it may return Clash YAML, a list of node links, or sing-box JSON. These formats aren’t interchangeable.
- Configuration file: Usually in JSON format. A valid file extension doesn’t guarantee valid content; the file must also meet the requirements of the current core version.
Support for the sing-box core doesn’t mean support for every subscription format. Check the provider’s format documentation before importing. If this site’s free nodes page offers multiple options, choose the one that matches your client. Don’t mistake a webpage URL for a subscription URL.
2. Import and connect based on the format
- Open the client and go to “Configuration,” “Profiles,” or a similar page. Choose the option to add a configuration. Menu names vary, but the goal is to create a configuration you can enable.
- If you have a subscription URL, choose “Import from URL,” “Remote Configuration,” or a similar option, paste the full URL, and save it. Use this method only if your client explicitly supports the subscription format. Don’t add conversion parameters yourself.
- If you have a single-node link, look for “Import from Clipboard” or “Scan QR Code.” If those options aren’t available, ask the provider for a compatible configuration. Don’t import a node link as JSON.
- If you have a JSON file, use “Import from File.” If configuration validation fails, first check which client and configuration versions are compatible. Don’t blindly delete fields that trigger errors.
- Select the new configuration, allow the client to create a VPN connection when prompted, and then start the proxy. If the configuration has a node selection group, open it and choose your target node. Don’t run another VPN app at the same time.
- Test a website you commonly use, then check your outbound region using a trusted IP lookup page. Passing a latency test doesn’t mean every website will be accessible, so test the pages you actually need for work.
3. How team usage relates to account environment stability
A successful import is just the starting point; it doesn’t guarantee a stable account environment. Switching nodes, automatic node selection after subscription updates, and different rules used by team members can all change the outbound IP or region. Shared free nodes may also change their exit IP, so don’t assume they provide a long-term fixed IP.
Teams can standardize client versions, configuration sources, and usage rules, and assign a clear owner to each account that requires authorized access. Avoid switching nodes mid-session, and check the actual outbound IP even when you keep selecting a node with the same name. Account security checks can also depend on the device, browser, login location, and user activity. A VPN can’t guarantee that you’ll avoid verification or restrictions.
4. Troubleshooting import or connection issues
If you see a parsing error, check that you copied the full link, that it doesn’t contain extra spaces, and that the subscription format is supported. If a remote download fails, check your network, the link’s expiration date, and the provider’s service status. If you can connect but can’t open webpages, first quit any other proxy, then check the routing mode, DNS errors, and system time. If the configuration stops working after an update, review its compatibility notes and keep a local backup before making changes.
Subscription URLs may contain access credentials. Don’t post them in group chats or on public conversion websites. When troubleshooting as a team, share only error logs with tokens, passwords, and sensitive server details removed. If any of these details are exposed, contact the provider promptly to reset them.