This article answers the question “How do I import nodes into sing-box?” It’s for users who have just installed a sing-box client. Follow the steps to import a subscription or individual node, and learn why your IP, DNS, and browser environment can affect what you see after connecting.
1. What to prepare before importing
sing-box is a proxy core. Most users use a client with a graphical interface, such as SFI, sing-box GUI, NekoBox, or Hiddify. Interfaces vary slightly between clients, but the import process is generally the same: import a subscription link, import a configuration file, or enter the node details manually.
- Get a working node or subscription link. Our free nodes page also features importable resources from time to time.
- Make sure the client supports your protocol, such as VLESS, VMess, Trojan, Shadowsocks, or Hysteria2.
- Keep your phone or computer’s system clock accurate; otherwise, TLS verification may fail.
2. Import nodes using a subscription link
Subscriptions are the easiest option for beginners, and they make it easy to update nodes later. Follow these steps:
- Copy your subscription link. It usually starts with https://.
- Open the sing-box client and go to the “Configuration,” “Subscription,” or “Profiles” page.
- Tap “Add,” “Import from URL,” or “Import from Link.”
- Paste the subscription URL and enter a name, such as “freevpn,” or choose your own.
- Save it, then tap “Update Subscription” and wait for the client to fetch the nodes.
- Return to the node list, select a node, and tap “Connect” or “Enable.”
If you see a message saying the format isn’t supported, the subscription may not be in a format that sing-box can recognize. Try a client that supports format conversion, or use a subscription that provides sing-box-compatible configuration.
3. Import a local configuration file or a single node
If you have a config.json file, select “Import from File” in the client, choose the file, and save it. If you have a single share link, such as vless://, trojan://, or ss://, you can usually import it using “Import from Clipboard.” After importing, open the node details and check that the server address, port, UUID/password, and transport settings are all present.
Note: Don’t change fields you don’t understand, especially Reality, TLS, SNI, and public key settings. An incorrect value can prevent the connection from working.
4. How IP, DNS, and your browser environment are related
Once connected, websites should see the proxy server’s IP address, not your local broadband IP. You can check this on an IP lookup site. If your IP hasn’t changed, the system proxy may not be enabled, your browser may not be using the proxy, or the client may have started the core without routing your traffic through it.
DNS matters too. Some websites may not load because DNS requests are still going through your local network, causing interference or resolving to the wrong address. If the client has options such as “Remote DNS,” “Prevent DNS Leaks,” or “Fake-IP,” enable the recommended defaults. If you’re unsure, don’t combine multiple DNS tools.
Your browser environment includes cache, cookies, language, time zone, WebRTC, and more. If the connection works but websites still behave strangely, try an incognito window, clear site data, or disable browser extensions that prevent WebRTC leaks. Remember: changing nodes does not change your browser fingerprint; they’re separate things.
5. Quick troubleshooting for connection failures
- Update the subscription first, then test 2–3 different nodes.
- Check whether your phone or computer is set to sync the time automatically.
- Switch networks: if Wi-Fi doesn’t work, try mobile data, or vice versa.
- Close other VPN or proxy apps to avoid port conflicts.
- Check the logs. A timeout usually indicates that the network is unreachable; TLS or handshake errors usually mean the settings don’t match.
In summary, there are three main ways to import nodes into sing-box: subscription links, configuration files, and share links. Once the import succeeds, check whether your IP has changed, whether DNS is going through the proxy, and whether your browser has cached data or leaks. This should help you pinpoint most issues.