This article explains how to import nodes into sing-box, what to do when a subscription isn’t recognized, and why team members may get inconsistent connection results. It clarifies the differences between node links, subscription URLs, and complete configurations, then covers how to import each one based on what the client actually supports. Importing correctly can reduce configuration errors, but it cannot guarantee a fixed exit IP or prevent third-party accounts from triggering verification.
1. Check the client and node format first
sing-box is a proxy core, and graphical clients offer different features across platforms. Menu names may also vary. First, check the version in the client’s “About” section or project documentation, then see whether it supports remote configurations, file imports, or node-link imports. Using the sing-box core does not mean the client can recognize every subscription format.
- Single-node links: Common formats include vless:// and trojan://. The client must explicitly support parsing them.
- Subscription URLs: Usually HTTPS links that may return a list of nodes or a complete configuration.
- sing-box configurations: Usually JSON files that may include routing, DNS, and inbound settings in addition to nodes.
Clash YAML configurations cannot be imported directly as sing-box JSON. For free nodes from this site or content from other sources, check the format, last-updated date, and client requirements first. Don’t assume compatibility based on how a link looks.
2. Import based on the content type
- Install the client from its official project or a trusted app store. On first use, follow the prompts to allow it to add a VPN configuration. Back up your current working configuration before modifying it.
- If you have a sing-box remote configuration URL, go to “Configuration,” “Profiles,” or a similar page, choose the option to add a remote configuration, paste the URL, and save. Once downloaded, check that a configuration name and update information are displayed.
- If you have a JSON file, choose the option to import from a file. Clients that support pasting configurations may also let you paste the complete JSON. If a parsing error appears, stop and don’t delete fields at random.
- If you only have a single-node link, use the client’s dedicated link-import feature. If there’s no such option, ask the provider for a compatible configuration. Don’t paste the link into a JSON editor.
- Select the configuration and connect. If it contains a node-selection group, choose a node from that group. Test with a regular webpage and check that the logs aren’t continuously reporting errors.
Subscription URLs may contain access credentials. Don’t share them publicly. If you need to convert a format, prefer a trusted tool that processes the data locally. Don’t submit URLs containing tokens to unfamiliar conversion websites.
3. How does team use relate to account stability?
Teams should standardize client versions, configuration sources, and update procedures, but don’t need to share the same private subscription. Record the configuration name used on each device and keep the previous version before updating, so it’s easier to revert and compare if something goes wrong.
A successful import doesn’t guarantee a stable account environment. Whether an account triggers security verification also depends on changes in exit region, devices, cookies, simultaneous logins from multiple locations, and platform rules. During work, avoid frequently switching nodes or regions, and don’t change multiple network settings at once. For team accounts, prefer the platform’s built-in member-permission features.
4. Troubleshooting import or connection issues
Check these items in order: Confirm that your original network works, update the subscription, and check your device’s date and time and the client version. A format error usually means you need to confirm the subscription type or configuration compatibility. A download failure may mean the URL has expired or wasn’t copied in full. If the connection times out, try another node in the same configuration. Other VPN or proxy tools may conflict, so quit them temporarily and try again. When reporting an issue, provide redacted logs and version details. Don’t send the full subscription URL, password, or token.