This guide explains how to configure a WS TLS node: from importing a subscription and checking WebSocket and TLS settings to troubleshooting connection failures, helping everyday users set up their clients. For team use, it also covers which settings should be standardized and how node configuration relates to account environment stability.
1. Confirm the node type and required parameters
WS is a WebSocket transport, while TLS encrypts the connection. Neither is a complete node protocol. Before configuring the client, confirm whether your provider uses VLESS, VMess, or another protocol, and choose a client that supports that combination. Do not enter a VLESS link as a VMess node.
First, obtain the complete subscription link, node share link, or client-specific configuration from your provider. You only need to enter the following details individually when adding a node manually:
- Basic settings: protocol, server address, port, and UUID or the corresponding authentication details.
- Transport settings: select WebSocket and enter the WS path and Host.
- TLS settings: enable TLS and enter the SNI/server name specified by your provider.
The server address, WS Host, and TLS SNI may differ, so use the values in the original configuration. WS paths typically start with “/”; do not change the capitalization or query parameters.
2. Import the configuration and check the settings
- Install software that supports your protocol from the client’s official release channel, such as v2rayN, v2rayNG, or a compatible Clash or sing-box client. Avoid modified versions from unknown sources.
- Copy the subscription link, then add and update it under “Subscription Management.” For a single-node share link, use an option such as “Import from Clipboard”; menu names vary by client.
- If the import fails, first check that the format is supported. VLESS share links, Clash YAML, and sing-box JSON are not universally supported by every import option. Request the appropriate format instead of submitting the configuration to an online conversion site.
- Open the node details and verify the protocol and authentication details. Set the transport to WS/WebSocket, then check the path, Host, TLS toggle, and SNI. Leave certificate verification enabled; do not treat “skip certificate verification” as a routine fix.
- Save the settings, select the node, and enable the system proxy or the client’s VPN mode. First try visiting the target website in rule mode, then check the connection logs.
A successful import does not guarantee a successful connection. A latency test may not indicate whether websites will actually load, so also check whether the site opens, whether DNS errors occur, and what the logs show about the handshake.
3. Troubleshoot connection failures step by step
If the connection times out, first check your local network, server address, and port. Then confirm that the subscription has not expired and that the node is still active. If you see a certificate error, check the device’s clock and whether the SNI matches the certificate. Do not hide the problem by turning off verification.
If the logs report a WebSocket handshake failure or an HTTP 400 or 404 error, focus on the WS path and Host, and contact your provider to confirm whether the settings have changed. If the connection succeeds but websites will not load, check the proxy mode, routing rules, and DNS settings. Change only one setting at a time to make it easier to identify the cause.
4. Team use and account environment stability
Teams can standardize client versions, configuration sources, and update procedures, but should not share subscriptions, UUIDs, or screenshots containing credentials publicly. Before sharing access, confirm that the provider’s terms allow it.
WS TLS does not provide a fixed egress IP or guarantee that accounts will never trigger security checks. Account environment stability is also affected by the egress IP, login location, device, browser, and user activity. For routine collaboration, avoid unnecessary changes between regions, enable multi-factor authentication, and follow the platform’s rules for team accounts. If your business requires a fixed egress IP, confirm separately whether the service supports it.