This article explains how to configure a WS TLS node. You’ll learn how to import a node into V2Ray, Clash, or a sing-box–based client, check the WebSocket and TLS settings, and determine whether a connection failure is caused by the node configuration, IP, DNS, or browser environment. The instructions assume you already have a node link or subscription; they don’t cover setting up your own server.
1. Understand WS, TLS, and node protocols
WS is a WebSocket transport method, while TLS encrypts the connection. Neither is a node protocol on its own. A node may use the VLESS or VMess protocol while also using WS transport with TLS enabled. So knowing only that a node uses “WS TLS” isn’t enough to configure it. You’ll also need the server address, port, user ID, and any provider-specified details such as the path, Host, and SNI.
Whenever possible, use the complete node link or subscription to avoid missing details when entering them manually. For free nodes provided by this site, use the parameters listed on the relevant page. Whether a node connects depends on its status and your current network; you can’t determine that from the protocol name alone.
2. Import the node and check the key settings
- Install a client from a reliable source that is still maintained, and make sure it supports the node’s protocol and WS transport. For Clash-based clients, also check that the core you’re using is compatible with the configuration.
- Copy the complete node link and choose “Import from clipboard.” If you have a subscription URL, add it under “Subscription management” and update it. Subscription formats aren’t necessarily compatible across clients, so use the link format recommended by the provider.
- Open the node’s edit page and check the server address, port, protocol, and user ID. Don’t paste an entire webpage URL into the server field or change the port to 443 without a reason.
- Set the transport to WS and enter the path exactly as provided, including the leading slash, capitalization, and query parameters. If the provider specifies a Host, enter it in the field corresponding to the WebSocket request header.
- Enable TLS and enter the SNI as required by the provider. Some clients call this “Server name.” Save your changes, select the node, and then enable the system proxy or the client’s VPN/TUN mode, if supported.
The server address, WS Host, and TLS SNI may differ: the first determines the connection target, Host is used for the WebSocket request, and SNI is used during the TLS handshake and certificate validation. Don’t change them just to make them match. If Host or SNI isn’t listed separately, keep the imported values or confirm them with the provider.
3. Troubleshoot connection failures in order
First, update the subscription and check the client logs. If you see a timeout, check the server address, port, current network, and whether the node is still active. If you see a certificate error, check the SNI, device time, and certificate validity. Disabling certificate verification should not be treated as a routine fix. If the logs report a WebSocket handshake failure or return a 404 or 403, check the path and Host first; the node’s entry point may also have changed.
If the server address is a domain name, a DNS resolution failure can interrupt the connection before it is established. First check whether ordinary websites load, then review the DNS settings using your client’s documentation. Avoid changing several settings at once. Replacing the server address with an IP doesn’t necessarily solve the problem: the node may still require the correct SNI and Host, and some services don’t allow connections this way.
4. How to tell whether the browser is the cause
If the client shows that it’s connected but your browser can’t open a page, first check that the system proxy is enabled, that your rules route the target website through the proxy, and that no browser proxy extension is overriding the settings. The browser’s Secure DNS feature may affect how domain names are resolved, but it generally won’t fix an incorrect WS path or SNI.
You can disable conflicting proxy extensions and use a private window to test a regular HTTPS website for comparison. Private browsing doesn’t change your outgoing IP. Your outgoing IP is determined by the actual routing and the selected node, not by your browser language, cache, or time zone. Change one setting at a time and record the result so you can identify the problem instead of repeatedly reinstalling the client.