This article explains how to configure a WS TLS node: from importing the node and checking its settings to testing the connection. It also clarifies how IP addresses, DNS, and browser settings affect the process. It applies to clients that support protocols such as VLESS and VMess. Field names may vary slightly between apps, so use the settings provided by your node provider.
1. Understand what WS and TLS are
WS stands for WebSocket, a transport method; TLS encrypts the connection. WS + TLS is not a standalone node protocol—it must be used with a protocol such as VLESS or VMess. Knowing only that a node “supports WS TLS” is not enough to configure it. You also need the server address, port, user ID, WS path, and possibly a separately specified Host and SNI.
Install the software from the client project’s official website or release page. If possible, use a complete share link or subscription URL to reduce the risk of manual entry errors. Subscription URLs may contain access credentials, so don’t share screenshots or send them to strangers.
2. Import the node and check the key fields
- Copy the node share link and choose “Import from clipboard” in the client. If you have a subscription URL, go to subscription management, add the URL, and update it.
- Open the node’s edit page and confirm that the protocol, server address, port, and user ID match the original information. Don’t assume the port should always be changed to 443.
- Set the transport to WebSocket or ws, then enter the Path provided by your provider. The path usually starts with “/”. Preserve its capitalization, trailing slash, and query parameters exactly as provided.
- Enter the WS Host. This is the hostname in the WebSocket request and may differ from the server address. If your provider hasn’t specified one, don’t enter the domain of another website.
- Enable TLS and check the SNI, which may also be labeled serverName or “Server Name.” Keep certificate verification enabled, and configure other advanced options according to the node instructions.
- Save and select the node, then enable the system proxy. On a phone, you may need to allow a VPN connection. Test the connection in the client first, then verify it by opening a webpage.
The server address, WS Host, and TLS SNI may be different: the first determines the connection destination, Host is used for HTTP request routing, and SNI is involved in the TLS handshake and certificate verification. Don’t change all three fields to the same IP just to make them “match.”
3. How do IP, DNS, and browser settings affect the connection?
If the server address is a domain name, DNS must resolve it to a destination IP. A failed or unexpected DNS lookup may prevent the connection. If you connect directly using an IP address but the certificate is issued for a domain, you will usually still need to enter the correct SNI. Don’t disable certificate verification to mask this issue.
Browser proxy extensions, secure DNS, cached data, and existing connections can cause browser tests to differ from client tests. If the node test succeeds but webpages won’t load, first disable other proxy extensions, make sure the browser uses the system proxy, and restart the browser. An incognito window can help rule out some cache and extension issues, but it does not change your exit IP.
4. Troubleshoot connection failures in this order
- First, check your local network and system time. An incorrect clock can cause certificate verification to fail.
- If the connection times out, check the address, port, DNS resolution, and whether the node is still active.
- If you see a TLS or certificate error, check the SNI, certificate domain, and client version.
- If the WebSocket handshake fails, focus on the Path, Host, and transport settings.
- If only the browser fails, check the proxy mode, routing rules, and extension conflicts.
Change only one setting at a time and test again to make it easier to identify the cause. If you’re using one of this site’s free nodes, check its instructions first. If the settings change after a subscription update, re-import the node rather than continuing to use an old configuration.