This article answers the common question, “How do I import nodes into sing-box?” It also explains why you should check your IP, DNS, and browser environment after importing. It’s intended for everyday users who have just installed sing-box and received a free node or subscription link but aren’t sure how to use it.
1. Check what type of node you have before importing
sing-box supports multiple proxy protocols, though the interface may vary between clients. First, check which of the following you have:
- Subscription link: Usually a URL beginning with https. Useful for keeping your nodes up to date.
- Single-node link: Such as vmess://, vless://, trojan://, or ss://.
- JSON configuration file: Usually a complete configuration that you can import directly or use to replace your current one.
If you’re using a free node provided by our site, we recommend using the subscription method. If a node stops working, you can simply update the subscription instead of copying nodes manually each time.
2. Common steps for importing nodes into sing-box
The names of options may vary between sing-box graphical clients, but the general process is the same: add a configuration, import nodes, select a server, and start the proxy.
- Open the sing-box client and go to “Configuration,” “Profiles,” or “Subscriptions.”
- For a subscription link, choose “Add Subscription” or “Import from URL,” paste the link, and save.
- For a single-node link, choose “Import from Clipboard” or “Import.” Copy the node link first, then import it.
- For a JSON file, choose “Import from File,” locate the configuration file, and confirm.
- After importing, click “Update Subscription” and wait for the node list to appear.
- Select a node, enable proxy or VPN mode, then visit a test site to confirm that the connection is working.
Successfully importing a node doesn’t guarantee that you’ll be able to access every website. The node may have expired, the network may be blocking traffic, or your device’s DNS settings or browser cache may affect the results.
3. How your IP, DNS, and browser environment are related
Many people only check whether a webpage loads after importing a node. We recommend checking three things instead: your IP, DNS, and browser environment.
IP determines the apparent location of your outgoing connection. If the proxy is working, an IP-checking site should show an address different from the one assigned by your home broadband or mobile network. If it still shows your local IP, the proxy may not be handling your browser or system traffic.
DNS translates domain names into IP addresses. If DNS is leaking, some domain lookups may still go through your local network even when your web traffic uses the proxy. This can cause connection issues or expose your privacy. sing-box can generally handle this through its built-in DNS rules. If you’re an everyday user, we recommend keeping the client’s default recommended settings and avoiding unnecessary DNS changes.
Your browser environment includes your cache, cookies, WebRTC, language, and time zone, among other things. Some websites use this information to determine your browsing environment. So if a site still shows your old region after you switch nodes, the node may be working fine—the cause could be your browser cache or account history.
4. Troubleshooting connection failures
- Update your subscription first, then try 2–3 different nodes to rule out a problem with a single node.
- Check that your system clock is correct. An incorrect time can cause TLS connection failures.
- Make sure VPN/TUN/system proxy mode is enabled in the client, and check that your browser doesn’t have an incorrect proxy configured separately.
- Turn off other VPNs, accelerators, or proxy extensions to avoid port conflicts.
- If webpages won’t load but chat apps work, try clearing your browser cache or opening an incognito window.
In summary, importing nodes into sing-box is straightforward. The key is to identify whether you have a subscription, a single-node link, or a configuration file. After importing, check whether your IP has changed, DNS is working properly, and your browser environment is clean. This will help you pinpoint the issue more accurately.