This article explains how to configure a “WS TLS node” and why it might fail to connect after import. It describes how to enter the settings in a client that supports VLESS or VMess, and distinguishes the effects of node settings, IP addresses, DNS, and the browser environment. WS is the WebSocket transport, while TLS encrypts the connection; neither is a standalone node protocol. Before configuring the node, check whether the share link specifies VLESS or VMess.
1. Prepare the client and node details
Install the version suited to your system from the client’s official source. For example, you can use v2rayN on Windows or v2rayNG on Android. Menu names may vary between versions, but the key fields are similar. Get the share link, QR code, or subscription URL. If you only have text settings, they should include the server address, port, user ID, transport, WS path, and details such as TLS and server name.
Whenever possible, import using the complete share link or subscription to avoid missing a path, domain, or encoded character when copying settings manually. If you use a free node provided by this site, use the actual settings listed for that node. Share links and subscription URLs may contain access credentials, so do not post them publicly.
2. Import the node and verify the WS TLS settings
- Copy the node link and select “Import from Clipboard” in the client. If you have a subscription URL, open subscription management, add the subscription, and update it.
- Open the node’s editing page and check that the protocol, server address, port, and user ID match the source. For VMess, enter the other fields as specified in the original information—do not guess.
- Set the transport to WS or WebSocket, then enter the WS path. Paths often start with a slash. Preserve capitalization, trailing slashes, and any additional parameters.
- Enter the WS Host as required by the node, enable TLS, and verify the SNI (the TLS server name). Host and SNI may be the same, but they serve different purposes and should not be substituted for each other based on assumptions.
- Save the settings, select the node, enable the system proxy or the client’s recommended proxy mode, and test by opening a regular HTTPS webpage.
The server address, WS Host, and TLS SNI may differ. The server address determines where the connection goes; Host is used in the WebSocket request; and SNI is used during the TLS handshake and certificate verification. Do not change all three to the server’s IP, and do not disable certificate verification just to “fix the connection.”
3. What IP, DNS, and the browser affect
If the node address is a domain name, the client usually needs to resolve it via DNS to find the IP to connect to. Resolution failures or an unreachable result can cause a connection timeout. If you connect directly using an IP, TLS may still require the original domain as the SNI, so “switching to an IP” does not mean you can clear all the other settings.
The browser mainly affects whether webpage requests go through the proxy and how websites identify the current session. Secure DNS, proxy extensions, cache, and cookies in the browser can all interfere with troubleshooting. If a webpage won’t load, the node settings are not necessarily at fault. A website’s displayed region may also be affected by your account, cookies, and its database of exit IP addresses, so region alone cannot confirm whether the connection is working.
4. Troubleshoot connection failures in order
- First check your local network and system time, then confirm that the subscription updated successfully and the node is still available.
- If you see a TLS or certificate error, first check the SNI, system time, and certificate verification settings. Do not immediately enable “Allow insecure connections.”
- If the WebSocket handshake fails, check the WS path and Host, and make sure you have not selected a different transport by mistake.
- If the client’s connection test succeeds but the browser fails, check the system proxy setting, proxy extensions, and routing rules. Temporarily disable conflicting extensions and test again in a private window.
- If the connection still times out, compare it with another trusted node and check the client logs. Before sharing logs, redact sensitive information such as user IDs and subscription URLs.
Change only one setting at a time and record the result to make the cause easier to identify. Do not randomly change DNS, SNI, and the path over and over just to get a connection. If required settings are missing, ask the node provider to confirm them.