This article answers the question “How do you configure a WS TLS node?” It covers importing a node, checking the WebSocket and TLS settings, troubleshooting connection failures, and explains how these settings relate to account environment stability for team use. The steps below cover client-side operations only and apply to clients that support the relevant protocols, such as v2rayN and v2rayNG. Menu names may vary by version.
1. Prepare the node details and import from a subscription when possible
WS is a WebSocket transport, while TLS encrypts the connection; they are not separate node protocols. Before configuring a node, confirm whether it uses VLESS or VMess, and gather the server address, port, user ID, WS path, Host, and TLS server name. If the VMess configuration has additional parameters, enter them as instructed by the provider.
Import a complete share link or subscription whenever possible; don’t guess parameters based on keywords. Install a suitable version from the client’s official release channel, copy the node link, and add it using “Import from clipboard.” To add a subscription URL, go to subscription management and update it after adding the URL. For free nodes provided by this site, use the parameters and availability listed in the latest post; continuous availability is not guaranteed.
2. Manually configure a WS + TLS node
- Add a node, select the correct protocol, such as VLESS or VMess, and enter the server address, port, and user ID. The port is not necessarily 443; use the value provided for the node.
- Under transport, select “ws” or “WebSocket.” Enter the WS path exactly as provided, preserving the leading slash, capitalization, and query parameters. Don’t change it to the home page path.
- Enter the WS Host. This is the hostname in the WebSocket request and may differ from the server address. If the provider doesn’t specify one, don’t add one arbitrarily.
- Enable TLS and enter the specified domain under SNI or “Server Name.” The server address, WS Host, and SNI serve different purposes. Even if they happen to be the same for some nodes, don’t assume they will be the same for all nodes.
- Keep certificate verification enabled, save the node, and first test web access with the system proxy enabled. Enable TUN only if you specifically need to route traffic from other apps, following the client’s instructions.
Don’t use “Allow insecure” or skip certificate verification as a routine fix. If you see a certificate error, first check the SNI, system time, and whether the node details are outdated. If the imported node shows a transport other than WS, don’t change it directly; check with the provider.
3. Troubleshoot connection failures in this order
- Complete timeout: Confirm your local network is working and the subscription is up to date, then check the address and port. Compare the result with a known working node.
- TLS handshake or certificate error: Check the device’s time, SNI spelling, and certificate verification settings. Contact the provider if needed.
- WebSocket handshake failure or a 403 or 404 error: Check the path and Host first. The status code is a clue, but it doesn’t identify the cause on its own.
- The client shows a connection, but apps can’t access the internet: Check the system proxy, routing rules, and DNS. Also make sure no other proxy software is overriding the settings.
4. How does team use relate to account environment stability?
WS + TLS primarily determines how the client connects to a node. It does not provide a fixed exit IP or guarantee that an account won’t be asked to verify its identity. Account environment is also affected by changes in exit IP, login region, device, browser session, and platform rules. Even the same subscription may include different exit IPs.
Teams should standardize client versions and configuration instructions, and keep a record of which nodes members use and their required exit regions. Avoid having members switch regions arbitrarily or share account sessions. Manage team access through proper collaboration permissions, and don’t post configurations containing user IDs, passwords, or subscription tokens in public groups. When troubleshooting, change one parameter at a time and record the error while keeping credentials hidden. If the configuration is correct but still doesn’t work, update the subscription or contact the provider first.