This guide explains how to configure a WS TLS node and troubleshoot why it won’t connect after import. It’s intended for everyday users of V2Ray, VLESS, and compatible clients. Verify the node settings using the steps below, then check your IP, DNS, and browser settings to avoid mistaking a browser issue for a node failure.
1. Understand the difference between WS, TLS, and node protocols
WS refers to WebSocket transport, while TLS encrypts the connection. Neither is a standalone node protocol; both are commonly used with protocols such as VMess and VLESS. Before configuring a node, obtain the complete link, QR code, or subscription URL from your service provider. Don’t create a node based only on the words “WS TLS”, because the server address, port, user ID, path, and domain may all vary.
We recommend installing the software from the client’s official release channel. Menu names vary slightly between clients, but you can usually find the import option under “Nodes,” “Configuration,” or “Subscriptions.”
2. Import using a link or subscription whenever possible
- Copy the complete node link, then select “Import from clipboard” in the client. If you have a subscription URL, open subscription management, add the URL, and update the subscription.
- Select the imported node and open its edit page. Confirm that the protocol matches the provider’s instructions; don’t manually change VLESS to VMess.
- Check the server address, port, and UUID or password. The transport type should be WS, and TLS should be enabled.
- Check the WebSocket path and Host, as well as the TLS SNI/server name. The path usually starts with “/”; preserve the capitalization and parameters exactly as provided.
- Save and enable the node. Turn on system proxy or VPN mode as prompted by the client, then test the connection by visiting a regular HTTPS website.
The server address, WS Host, and TLS SNI don’t have to be the same: the address determines where to connect, Host is used for the WebSocket request, and SNI is used during the TLS handshake. Enter the values provided by your service provider; don’t change them all to the same IP just for the sake of consistency. Clients such as Clash and sing-box require specific configuration formats, so if an import fails, first check whether the subscription format is supported.
3. If you can’t connect, check IP, DNS, and TLS in that order
Start by checking the client logs. If you see a domain resolution failure, check your local network and DNS first. If you see a connection timeout, check the address, port, current network, and whether the node is still available. If you see a certificate error, check your system time, SNI, and the server certificate status. If the TLS handshake succeeds but you get a WebSocket error, check the path and Host.
If the server is entered as a domain name, DNS resolution is required. If you enter an IP address directly, you may still need to keep the SNI and Host specified by your provider. Don’t treat disabling certificate verification as a routine fix: it reduces security and won’t resolve an unreachable port or an incorrect path.
4. The client works, but the browser still won’t load pages?
Check whether the browser uses the system proxy. Some browser extensions override proxy settings, so try temporarily disabling them and testing again. The browser’s Secure DNS, cache, and existing connections can also affect results. Try a window without extensions or a different browser for comparison, then check each setting in turn.
System proxy mode may not route traffic from every application. TUN/VPN mode also requires checking permissions and routing rules. If only certain websites won’t load, first check whether the rules route them through the proxy; don’t immediately change the node settings.
Finally, update the subscription and test another node for comparison. When using free nodes from this site or other sources, also verify their settings and availability. Treat subscription URLs and node links as sensitive information; if you ask for help, hide your UUID, password, and subscription token.