This article addresses the question “how to import nodes into sing-box“: it is intended for users using sing-box for the first time, explains how to import a subscription or a single node, and clarifies why the IP, DNS, and browser environment you see after connecting can affect access results.
1. First, prepare the sing-box client and node information
sing-box itself is a core engine. Ordinary users typically use GUI clients based on it, such as sing-box GUI, SFI, or third-party panels on Windows, macOS, Android, and iOS. Different clients may use slightly different interface labels, but the core process is the same: add a configuration, import a subscription, select a node, and start the proxy.
You need to prepare one of two types of information: one is a subscription link, usually starting with https://; the other is a single node link, such as vless://, vmess://, trojan://, or ss://. This site provides collections of free testable nodes. Before use, it is recommended to copy the latest link first to avoid expiration.
2. Import nodes using a subscription link
- Open the sing-box client and go to the “Configuration,” “Profile,” or “Subscription” page.
- Click “Add,” “Import,” or “New Profile.”
- Select “Import from URL” or “Remote Subscription.”
- Paste the subscription link and give it a name, for example freevpn-x.
- Click save, then run “Update Subscription” or “Refresh.”
- Return to the node list, select a node, and click Start or Connect.
If the import succeeds but no nodes appear, first check whether the link is complete, especially making sure the opening https:// is not missing. Some clients only support native sing-box JSON subscriptions; when you encounter generic Clash/V2Ray subscriptions, you may need to use a client that supports conversion or switch to a different subscription format.
3. Manually import a single node
If what you received is a node share link, you can choose “Import from Clipboard,” “Import from Clipboard,” or “Scan QR Code” in the client. First copy the complete node link, then click import. After importing, it is recommended to check whether fields such as protocol, server address, port, UUID/password, TLS, Reality, and SNI have been correctly recognized automatically. Ordinary users do not need to modify underlying parameters unless the node provider explicitly instructs otherwise.
Before connecting, it is recommended to change only one thing: the proxy mode. Common modes include global, rule-based, and direct. When troubleshooting as a beginner, you can first test with global mode; after confirming access works, switch back to rule mode to avoid misjudgment caused by rule-based traffic splitting.
4. What is the relationship between IP, DNS, and the browser environment?
- IP: After a successful connection, when you visit an IP lookup site, the displayed exit IP should change to the network where the node is located. If it still shows your local broadband IP, it means the proxy has not taken over browser or system traffic.
- DNS: DNS is responsible for resolving domain names into IP addresses. If DNS still goes through the local network, you may encounter situations such as sites not opening, being redirected to local pages, or abnormal region detection. In the client, you can enable options such as “Remote DNS” or “Prevent DNS Leaks.”
- Browser environment: Browser cache, cookies, language, time zone, and WebRTC can all affect how websites identify you. Even if the proxy works successfully, old cookies may still cause a website to continue recognizing your original region.
When testing, you can open an incognito window, disable conflicts from browser proxy extensions, and refresh the DNS cache. Do not run multiple VPNs, proxy extensions, and system proxy tools at the same time, otherwise it is very easy to run into the situation where “the node is connected but web pages will not open.”
5. Quick troubleshooting for connection failures
If you encounter a failure, check in order: whether the subscription has expired, whether the system time is accurate, whether the node has been deleted, whether the network can access the subscription address, whether the client has VPN permissions, and whether it is being blocked by security software. On Android and iOS, you should also confirm that the VPN configuration permission prompt from the system has been allowed.
If a particular node times out, it is not necessarily a client error; the node may simply be temporarily unavailable. You can update the subscription and try another node. Finally, it is recommended to keep one working configuration as a backup so that when problems occur, it is easier to determine whether the issue is with the node, DNS, or an access anomaly caused by the browser environment.