This article explains how to configure a WS TLS node, from importing it and checking its settings to testing the connection. It shows where to enter the server address, WS Host, and TLS SNI, and explains how IP addresses, DNS, and browser settings can affect connectivity. It applies to V2Ray, Clash-style, and sing-box clients that support the relevant protocols; it does not cover server setup.
1. Check the protocol and node settings
WS is a WebSocket transport, and TLS encrypts the connection. Neither is a complete node protocol; they are usually paired with VLESS, VMess, or Trojan. When installing a client, use the project’s official website or release page where possible, and confirm that the version supports the node protocol and WS transport.
Have the server address, port, UUID or password, WS path, Host, and TLS SNI provided by your service provider ready. Use the node’s original instructions as the source of truth; don’t assume that all domain fields should have the same value. Preserve the path’s capitalization, leading slash, and any query parameters.
2. Import a node or configure it manually
- Copy the complete node link and select “Import from clipboard” in the client. If you received a subscription URL, go to subscription management, add the URL, and update it. Don’t enter a subscription URL as if it were a single node.
- To add a node manually, select the correct protocol first, then enter the server address, port, and credentials. Use the port specified by your provider; don’t change it to 443 just because TLS is enabled.
- Set the transport type to WS or WebSocket, then enter the path and Host. Depending on the client, Host may be under “Request headers” or “Transport settings.”
- Enable TLS and enter the certificate domain specified by your provider in the SNI or “Server name” field. Keep certificate verification enabled; don’t use “Allow insecure” as a routine fix.
- Save the node and select it as the current outbound connection. Enable the system proxy or TUN mode as instructed by the client, then test by opening a webpage. A successful latency test doesn’t mean every website will be accessible.
3. How do IP, DNS, and the browser affect the connection?
The server address determines the connection target and can be a domain or an IP address. WS Host is used for the WebSocket request, while SNI is used during the TLS handshake; they serve different purposes. Changing the server domain to an IP address doesn’t mean you should also change Host and SNI to the IP address. If the certificate only covers the domain, changing SNI incorrectly may cause verification to fail.
DNS resolves domain names. If the node’s domain can’t be resolved, the client may not be able to connect. Whether website domains are resolved locally or on the proxy side depends on the operating mode and DNS settings. Start with the configuration recommended by the client, and avoid stacking multiple DNS tools.
Browser proxy extensions, separate proxy settings, and Secure DNS may change the route your traffic takes, but they won’t correct your node settings. If the client connects but the browser can’t open websites, temporarily disable proxy extensions and test with another browser for comparison.
4. Troubleshoot connection failures in order
First, make sure your local network is working and your device’s clock is accurate. Then update the subscription and check that the node is still active. Next, verify the protocol, credentials, port, WS path, Host, and SNI, making sure no spaces were copied along with the settings.
Check the client logs: if name resolution fails, check DNS; if there’s a certificate error, check the device time and SNI; if the handshake fails or an HTTP error appears, recheck the WS settings—the remote service may also be experiencing problems. Finally, try another network or compare with another working node. Before sharing logs, hide your subscription URL, UUID, and password. Free nodes may stop working, so rely on the actual connection results.