This article covers the most common questions everyday users have when using sing-box: how to import nodes into sing-box, why you might still be unable to access the internet after importing them, and how your IP, DNS, and browser environment can affect your results. Follow these steps if you already have a vmess, vless, trojan, or ss link, or a subscription URL.
1. What to prepare before importing nodes
sing-box is a proxy core, and different platforms have different graphical clients, such as sing-box clients or third-party control panels for Android, Windows, and macOS. First, make sure of three things: the client is installed, the node link is valid, and your system clock is correct. This site collects some free nodes for testing, but their reliability can vary, so start with a small number of nodes to verify that your configuration is working properly.
- Single node: Usually a link starting with vmess://, vless://, trojan://, or ss://.
- Subscription URL: Usually a URL starting with https:// that contains multiple nodes.
- Configuration file: May be a json file, suitable for clients that support importing full configurations.
2. General steps for importing nodes into sing-box
The names of options may vary slightly between clients, but the process is much the same. Follow these steps:
- Open the sing-box client and go to the “Configuration,” “Profiles,” or “Subscription” page.
- If you have a subscription URL, select “Add subscription” or “Import from URL,” paste the subscription link, and save it.
- If you have a single node link, select “Import from clipboard,” “Import share link,” or “Add node manually.”
- Click “Update subscription” or “Refresh,” and wait for the node list to appear.
- Select a node, turn on the proxy, and test access in your browser.
If the client reports a format error, first check that you copied the entire link, especially any parameters at the end. If the subscription is empty, the URL may have expired, your network may be unable to reach it, or the client may not support that subscription format.
3. How IP, DNS, and your browser environment are related
Many people assume that importing a node means they can access websites right away, but it also depends on whether your IP, DNS, and browser environment are configured appropriately. Once connected to a node, your public IP will generally change to the proxy server’s IP. If it still shows your local IP, your traffic is not going through the proxy. The system proxy may be disabled, the wrong mode may be selected, or your browser may be bypassing the proxy.
DNS translates domain names into IP addresses. If DNS requests are still handled by your local network, websites may fail to load, resolve to the wrong address, or identify your region incorrectly. We recommend using the client’s default recommended DNS or enabling an option such as “Remote DNS” or “Proxy DNS” to prevent DNS leaks.
Your browser environment includes cache, cookies, language, time zone, WebRTC, and other settings. Even after your proxy IP changes, websites may use old browser cookies or WebRTC to identify your original environment. When testing, try using a private window, clear the target website’s cookies if necessary, and disable or restrict WebRTC in your browser to prevent leaks.
4. Quick troubleshooting for connection failures
- Node times out: Try another node; free nodes may be temporarily unavailable.
- Connected, but webpages won’t load: Check your rules mode and switch to global mode to rule out routing issues.
- IP hasn’t changed: Make sure system proxy or VPN mode is enabled and that your browser isn’t configured to connect directly.
- Some websites behave unusually: Clear cookies, try a node in another region, and check your DNS settings.
- Subscription update fails: Try opening the subscription URL in a browser to see whether it’s reachable.
In short, the key steps for importing nodes into sing-box are: “add a subscription or link—update—select a node—enable the proxy.” If you still have problems after importing, don’t focus only on the node itself. Also check whether your IP has changed, DNS is going through the proxy, and your browser is not retaining your old environment. Following these checks in order will usually help you identify the issue quickly.