This article explains how to import nodes into sing-box, what to do when a subscription link isn’t recognized, and why team members may end up with different exit IPs after connecting. First, confirm which import formats the client supports, then add the configuration and test it. For team use, standardize the configuration source and switching rules to reduce login verification caused by frequent changes in exit IPs. However, this cannot guarantee that an account won’t trigger security checks.
1. Check the client and node format first
sing-box is a proxy core, and import options vary between graphical clients. Install a client suitable for your system from the project’s official website or a channel linked from its official repository, and note its version. Menu names below are common examples; the actual interface may differ.
Node links, subscription URLs, and sing-box configuration files are not the same thing. Once you have the content, use the following guidelines to identify it:
- Links beginning with vless://, vmess://, trojan://, and similar prefixes are usually single-node share links, which the client must explicitly support parsing.
- A URL beginning with https:// might be a subscription URL or just a webpage. Check the format specified by the provider.
- A JSON file containing fields such as outbounds may be a sing-box configuration, but you still need to check version compatibility and whether the file is complete.
Clash YAML cannot be used directly as sing-box JSON. If the provider offers multiple subscription formats, choose the one specified as compatible with sing-box or your current client.
2. Import a subscription or local file
- Open the client’s “Configuration,” “Profiles,” or similar page and click Add. It’s a good idea to back up your existing configuration before proceeding.
- If the client supports remote configurations, choose URL import, paste in a compatible subscription URL, enter a descriptive name such as “Team Work Configuration,” then download and save it.
- If you have a complete JSON file, choose file import. Some clients let you paste configuration text; follow the on-screen instructions if so.
- If you only have a single-node link, check for an “Import from clipboard” option. If there isn’t one, ask the provider for a compatible configuration. Don’t paste the share link directly into a JSON editor.
- Select the new configuration, grant permission for the VPN connection when prompted, and start the service. Choose the desired route on the node or outbound page, then test whether you can open a regular webpage.
A successful import doesn’t necessarily mean the connection works. Check the logs for errors and confirm that the actual exit IP is what you expect. When using free nodes from this site or another source, verify their format and availability. Don’t rely on a temporarily available route for stable work access.
3. How does team use affect account stability?
The import process itself won’t make an account more stable. What matters is the exit IP, routing, and switching behavior after the configuration is enabled. Logging in to the same account from different regions within a short period may trigger additional security checks. Even if the node has the same name, that doesn’t mean its exit IP is fixed.
Teams should document client versions, configuration update times, and the expected exit region, and agree on when to update or switch routes. For work accounts, verify the exit IP for the target website before signing in. Don’t share account passwords or make subscription links public just to sync configurations—subscription URLs may contain access credentials. Whenever possible, use separate authorizations permitted by the service provider.
4. Troubleshoot import failures and connection issues
If you see a parsing error, first check whether the format is supported, whether any characters were missed when copying, and whether the download returned a login page instead. If the error says a configuration field isn’t supported, check that the client and configuration versions are compatible. If the configuration is enabled but you can’t connect, check your local network, system time, node availability, and any connection errors in the logs. If only certain websites are affected, check routing and DNS settings. Change one setting at a time while troubleshooting, and keep the original configuration so you can revert if needed.