This article explains how to configure a WS TLS node and why it may fail to connect after import. It covers how to enter the server address, Host, SNI, and path, and clarifies the effects of IP addresses, DNS, and browser settings. It applies to V2Ray and VLESS clients that support WebSocket and TLS; refer to the node provider’s instructions for the exact parameters.
1. Confirm the node details before configuring it
WS is a WebSocket transport, and TLS encrypts the connection. Neither is a standalone node protocol. First confirm whether the node uses VLESS, VMess, or another protocol, then select the matching type. Don’t create a VLESS node just because you see “WS TLS.”
- Basic details: server address, port, and UUID or password.
- Transport details: transport type (WS), WebSocket path, and Host.
- Security details: whether TLS is enabled, and the SNI or server name.
The server address, WS Host, and TLS SNI are not the same field. The address determines where to connect, Host is used in the WebSocket request, and SNI identifies the server during the TLS handshake. These values may be the same or different—don’t change them to match each other without instructions.
2. Import or configure the node step by step
- Install a client from the project’s official website or a trusted app store, and confirm that it supports the node protocol as well as WS and TLS. Update the subscription or configuration first to avoid using outdated details.
- Whenever possible, copy the complete node link and add it using “Import from clipboard.” If you have a subscription URL, use “Add subscription”—don’t enter it in the server address field.
- To add the node manually, select the correct protocol and enter the server address, port, and authentication details. Use the port specified in the original parameters; don’t change it to 443 just because TLS is enabled.
- Set the transport to WS and enter the path exactly as provided, including the leading slash and any additional parameters. Enter the value provided for Host, without copying the https:// prefix.
- Enable TLS and enter the specified domain under “SNI” or “Server name.” If other protocol options are provided, set them accordingly as well; don’t reuse settings from another node.
- Save and select the node, then enable the system proxy or the client’s recommended proxy mode and test by visiting a webpage. A displayed latency alone doesn’t mean browser traffic is correctly routed through the proxy.
Don’t use “Skip certificate verification” as a routine fix. If you see a certificate error, first check the device’s time, SNI, and whether the node is still valid. Disabling verification weakens connection security.
3. How IP, DNS, and browser settings affect the connection
If the server address is a domain name, DNS must resolve it to an IP address. A failed or unexpected resolution can cause the connection to time out. However, replacing the domain with an IP address won’t necessarily solve the problem and may affect CDN routing. If you need to use an IP specified by the provider, keep the Host and SNI values as instructed.
Whether the browser uses the proxy depends on the system proxy, client rules, and browser extensions. Secure DNS, proxy extensions, or old proxy settings may conflict with the current configuration. If a webpage won’t open in the browser, that doesn’t necessarily mean the WS TLS parameters are wrong, and the exit IP alone can’t confirm that the configuration is fully correct.
4. Troubleshoot connection failures in order
First check that the node is valid and the device time is correct. Then verify the address, port, path, Host, and SNI. If the logs show a certificate error, focus on TLS settings. If the WebSocket handshake fails, check the path and Host. If the connection keeps timing out, check the network, address resolution, and node availability.
If the client connects but the browser can’t open webpages, confirm that the system proxy is enabled, temporarily disable other proxy extensions, and try another browser. If you’re using a free node from this site, check its specific instructions as well. Before sharing logs for help, hide your UUID, password, and complete subscription URL.