This article explains how to configure a WS TLS node and why it may fail to connect after import. Follow these steps in order: enter the settings in your client, test the connection, then troubleshoot IP and DNS issues. WS is a WebSocket transport, and TLS encrypts the connection. They are not standalone proxy protocols and are typically used with VLESS or VMess. You cannot create a working node based only on the words “WS TLS.”
1. Confirm the node details before configuring it
First, get the complete share link, subscription URL, or connection parameters from your node provider. At a minimum, confirm the protocol, server address, port, user ID, WebSocket path, Host, and TLS server name. The server address, WS Host, and TLS SNI may be different, so enter each value as provided rather than replacing them all with the same domain.
You can use clients such as v2rayN or v2rayNG that support the relevant protocol. Install them from the projects’ official release pages or a trusted app store. Clash-based clients typically require a compatible subscription configuration; you cannot simply paste any share link into a YAML file.
2. Import or manually enter a WS TLS node
- When possible, copy the complete share link and select “Import from clipboard” in the client. If you have a subscription URL, go to subscription management, add the URL, and update the subscription. Do not enter the subscription URL in the server field.
- If you need to add a node manually, select VLESS or VMess first, then enter the server address, port, and user ID. Enter any additional VMess parameters or VLESS encryption options as specified by the provider; do not use an unfamiliar template.
- Under transport settings, select “ws” or “WebSocket” and enter the path and Host. The path usually starts with “/”; preserve its capitalization and any query parameters exactly as provided.
- Enable TLS and enter the server name in the SNI or Server Name field. Do not enable “Skip certificate verification” as a shortcut. If you get a certificate error, first check the domain, system time, and node validity.
- Save and select the node, then connect. On a computer, enable the system proxy if needed; on a phone, allow the client to create a VPN connection. Test a regular webpage first, then the target website.
Field names vary between client versions; what matters is entering each value in the correct field. Whether you use free nodes from this site or another source, rely on the complete configuration. If a node stops working, changing local settings may not restore it.
3. If you can’t connect, distinguish IP, DNS, and browser issues
The server IP and the public IP shown by a website are not the same thing. The server address is used to establish the connection; the IP a website sees depends on whether your traffic is routed through the proxy and on your routing rules. Do not simply replace the domain with its resolved IP. Even if you can substitute the address, you will usually still need to keep the original TLS SNI and WS Host.
If the logs indicate a domain resolution failure, first make sure your local network is working, then check the client’s DNS settings and whether the server domain can be resolved. A browser’s Secure DNS setting may affect how the browser resolves domains, but it does not necessarily determine how the proxy client resolves the server domain. Changing DNS alone does not prove that the node is fixed.
If the connection times out, check the address, port, and current network. If you see a certificate error, check the system time and SNI. If the WebSocket handshake fails, double-check the path and Host; the remote service may also be having issues.
If the client connects but webpages won’t load in the browser, check that the system proxy is working, that your routing rules aren’t sending traffic directly, and that no browser proxy extension is causing a conflict. An incognito window can help rule out cache and extension issues, but it won’t automatically change your IP. Change one setting at a time and test again to make it easier to identify the cause.