This article explains how to configure a WS TLS node and why the same node may behave differently with different IPs, DNS settings, or browser environments. It’s for everyday users who have VLESS/VMess + WebSocket + TLS node details but aren’t sure how to enter them in V2RayN, Clash, or sing-box, or how to troubleshoot connection failures.
1. Understand what information a WS TLS node requires
WS TLS usually means that WebSocket is used at the transport layer, with TLS encryption enabled on top. When importing a node, don’t just check the “address and port”—make sure all the parameters are present. These generally include the server address, port, UUID or password, protocol, transport (WS), TLS setting, SNI, Host, and Path.
- Protocol: Usually VLESS or VMess. Don’t mix up the settings for different protocols.
- Address: This may be a domain name or an IP address. If SNI is provided, you should usually enter the domain name.
- Port: Often 443, but use the port specified in the node details.
- Transport: Select WebSocket or ws.
- TLS: Enable it. Enter the SNI/Server Name provided for the node.
- Path: For example, /xxx. Match the capitalization and slashes exactly.
- Host: If the node specifies a Host value, enter it under WS Host or the Host override field.
If you copy a subscription link from our free nodes page, we recommend importing the subscription directly. This reduces the chance of mistyping the Path or SNI.
2. Configure the node in common clients
Different clients may use slightly different labels, but the underlying settings are the same. To add a node manually, follow these steps:
- Open the client and create a new node. Select VLESS or VMess as the protocol.
- Enter the server address, port, and user ID/UUID or password.
- Select WebSocket/ws as the transport. Don’t select TCP, gRPC, or HTTP.
- Enable TLS and select tls as the security option. If there’s an option to skip certificate verification, ordinary users should avoid enabling it without good reason.
- Enter the SNI, Host, and Path. Don’t guess values that haven’t been provided.
- Save the node, select it, and enable the system proxy or TUN/virtual network adapter mode.
- Visit a test website. If it won’t load, check the error in the client logs first.
In a Clash configuration file, you’ll typically see fields such as network: ws, tls: true, servername, ws-opts, path, and headers Host. In sing-box, the corresponding fields are transport, tls, server_name, path, and headers. As long as the fields have the same meaning, you don’t need to worry about the differences in their names.
3. Why IP, DNS, and browser settings can affect the connection
A WS TLS node may appear to involve only a “client connecting to a server,” but the connection also depends on your local network, DNS resolution, and browser proxy settings. If DNS resolves to an unexpected address, or the browser isn’t using the proxy, the node may show as connected while websites remain inaccessible.
IP and network conditions: Public Wi-Fi, corporate networks, and campus networks may block ports other than 443 or interfere with some TLS connections. Try switching to a mobile hotspot or home network to see whether the current network is the problem.
DNS: If your client supports remote DNS or fake-IP, enable it using the client’s recommended settings to avoid DNS pollution caused by local resolution in the browser. If you’re using system proxy mode only, the browser may still use system DNS, so check whether “Secure DNS/DoH” is enabled.
Browser settings: Proxy extensions in Chrome or Edge, the system proxy, and the client proxy can override one another. When troubleshooting, disable other proxy extensions and use only the VPN client. Testing in an incognito window can help rule out issues caused by the cache or extensions.
4. Quick checklist for connection failures
- Check that you selected the right protocol: don’t add a VLESS node as VMess.
- Make sure TLS is enabled and the SNI matches the node details.
- Check that the WS Path is complete, especially the leading /.
- Make sure the subscription is up to date. Old nodes may no longer work.
- Check the logs: timeout usually indicates a network or address issue; tls handshake often points to an SNI/TLS issue; 404/400 usually indicates a Path or Host issue.
- Test another node to determine whether the problem is with one node or the client configuration.
In short, the key to configuring a WS TLS node is to make sure the protocol, WS, TLS, SNI, Host, and Path all match. Rather than changing settings at random, troubleshoot the IP and network, DNS resolution, and browser proxy settings one by one. This will usually help you identify the cause.