This article explains how to import nodes into sing-box and why you should also check your IP, DNS, and browser environment after importing them. It’s intended for everyday users who have just installed sing-box and aren’t sure what to do with a free node or subscription link.
1. Get the client and node information ready
sing-box itself is a core program. Most users use a proxy client with a graphical interface, such as one for Windows, Android, iOS, or macOS that supports the sing-box core. The interface varies slightly between clients, but the import process is much the same: import a subscription link, or import an individual node link or configuration file.
- Subscription link: Usually a URL starting with https, suitable for updating multiple nodes at once.
- Individual node: May be a link such as vless://, vmess://, or trojan://.
- Configuration file: Usually a JSON file; the client must support importing it.
If you’re using the free nodes provided on this site, we recommend copying the “subscription URL” first, as it makes future updates easier. If you only have a single node link, you can add it manually.
2. General steps for importing nodes into sing-box
- Open the sing-box client and go to a page such as “Configuration,” “Profiles,” “Subscriptions,” or “Node Management.”
- Select “Add Subscription” or “Import from URL,” then paste in the subscription link.
- Give the subscription an easy-to-recognize name, such as freevpn-x or Backup Line.
- Click Update, Save, or Download Configuration, then wait for the client to fetch the node list.
- Return to the home screen or proxy page, select a node, and connect.
- Open a browser and visit an IP lookup site to confirm that your outgoing IP has changed.
For a single node link, select “Import from Clipboard,” “Add Share Link,” or “Import Node,” then paste in the vless:// or similar link. If the client reports a format error, check that the link doesn’t contain extra spaces, line breaks, or full-width punctuation.
3. How to check your IP, DNS, and browser environment after importing
Many people assume they’re all set once the node connects, but there are three more things to check. First, your IP address, which tells websites where your connection appears to come from. Second, DNS: a DNS leak could mean domain names are still being resolved through your local network. Third, your browser environment, including your language, time zone, and WebRTC settings.
After connecting, check these in order: Visit an IP lookup page and see whether your IP matches the node’s location. Then visit a DNS leak test page and check whether your local ISP’s DNS servers are exposed. Finally, disable unnecessary WebRTC features that could leak your information, or test in private browsing mode. Most users don’t need every setting to match perfectly, but should at least avoid the obvious issue of having an overseas IP while still using their local ISP’s DNS.
4. What to do if the connection fails or the subscription won’t update
If you can’t connect after importing, don’t rush to reinstall the client. Try these checks first:
- Subscription won’t update: Check whether the link has expired and whether your network can access the subscription URL.
- Node connection fails: Try another node; free nodes may be temporarily unavailable.
- Connected, but websites won’t load: Try switching the system proxy mode or TUN mode, or restart your browser.
- DNS issues: Enable remote DNS in the client settings, or use the DNS rules recommended by the client.
- Only some websites fail: This may be caused by routing rules. Temporarily switch to global mode to test.
Finally, remember that importing a subscription is only the first step. Whether it works also depends on the node’s status, client permissions, system proxy settings, and DNS configuration. If you run into problems, check these in order: can the subscription update, can the node connect, has your IP changed, and is DNS working correctly? This will usually help you pinpoint most sing-box issues.