This article explains how to import nodes into sing-box, what to do when a subscription link cannot be added, and why team members may experience different connection results after importing the same configuration. Follow the steps below to first confirm which import formats your client supports, then add a configuration and test the connection. We’ll also explain how your exit IP relates to account environment stability, so you don’t mistake “connected” for “account environment is definitely stable.”
1. Check the client and node format first
sing-box is a proxy core, and graphical clients offer different features on different platforms. Menu names may include “Configuration,” “Profiles,” or “Subscription.” Install the version for your operating system from the project’s official website or release page. Avoid modified versions from unverified sources.
sing-box configurations, Clash subscriptions, and individual node links are not interchangeable. After receiving a link, check the format specified by the provider. sing-box typically uses JSON configurations; Clash YAML subscriptions and sharing links such as vless:// can be imported directly only if the client explicitly supports parsing or converting them. Changing a file’s extension to JSON does not convert its format.
2. Choose an import method based on what you have
- sing-box remote configuration URL: Open the client’s configuration page and choose to add a remote configuration or subscription. Paste the URL, give it a name, save it, and update it. Once the download succeeds, select the configuration as well; don’t leave it sitting in the subscription list.
- Local JSON file: Save the file to your device, then choose the file import option on the configuration page. Some clients let you paste configuration text. If there’s no such option, import the file instead; don’t paste the full JSON into a URL field.
- Individual node sharing link only: Check whether the client supports importing from the clipboard or a sharing link. If there’s no matching option, ask the node provider for a compatible sing-box configuration. A single outbound node’s details may not include the routing and DNS settings required for a working configuration.
- After importing, start the connection and allow VPN access or the system network extension if prompted. Test a regular webpage, then check the client logs for parsing, authentication, or connection errors.
If you use free nodes from this site or another source, check the format and last update first. Free nodes may become unavailable, so avoid relying on an unverified node as your team’s only connection.
3. How teams can keep their environments relatively consistent
Importing the same configuration does not mean you’ll always have the same exit IP. Automatic node selection, failover, and changes to the server’s exit IP can all change the apparent source of your traffic. When troubleshooting as a team, record the client version, configuration update time, selected node, and whether automatic switching is enabled. Start by reducing the number of variables.
For work accounts that need to stay logged in, avoid frequently switching regions in a short period or sharing accounts with multiple people, and follow the platform’s rules. Account status is also affected by the device, browser profile, login behavior, and the platform’s risk controls. A VPN cannot guarantee that an account won’t be asked to verify or be restricted. Subscription URLs may contain access credentials, so don’t post them in public groups or include them in screenshots.
4. Troubleshooting import or connection failures
- Download fails: Check that the URL is complete and hasn’t expired, and confirm that your current network can access the subscription URL.
- Invalid configuration: Check whether you’re using the wrong format, such as Clash, or whether the configuration includes fields that your current version doesn’t support. Ask for a configuration compatible with your version.
- The connection starts, but webpages won’t load: Confirm that the correct configuration is selected, check the system time, temporarily disable other VPN or proxy tools, and then review the logs.
- Only some team members have issues: First align the client version, configuration, and node, then compare network conditions and system permissions. Redact subscription tokens, passwords, and other sensitive information before sharing logs.