This article explains how to configure a WS TLS node: from importing a node and checking WebSocket and TLS settings to troubleshooting connection failures. It helps everyday users set up their clients and explains how node and account environment stability relate to team use. The instructions below cover client-side operations only; you do not need to set up a server.
1. First, check that the node details are complete
WS is a WebSocket transport, while TLS encrypts the connection. Neither is a standalone proxy protocol; they are commonly used with VLESS, VMess, or Trojan. Before configuring a node, obtain a complete share link, subscription URL, or parameter list. Knowing only that it uses “WS+TLS” is not enough to configure it—you also need the server address, port, user credentials, and relevant domain information.
- Basic details: protocol type, server address, port, and UUID or password.
- WS details: select WebSocket as the transport and enter the Host and Path provided by the service provider.
- TLS details: enable TLS and check the server name (SNI). Set other options as directed by the node instructions.
Host is the hostname in the WebSocket request header, while SNI is used during the TLS handshake. They may be the same or different, so do not substitute one for the other.
2. Import the node first, then check the key fields
- Install a version suited to your device from the client’s official release channel, such as v2rayN, v2rayNG, or a Clash or sing-box graphical client that supports the relevant protocol.
- Copy the node share link and choose “Import from clipboard” in the client. If you have a subscription URL, go to subscription management, add the URL, and update it. Subscription formats are not necessarily compatible across clients, so check the format first if parsing fails.
- Open the node editing page and verify the protocol, address, port, and credentials. The transport type should be WS or WebSocket. Enter the path exactly as provided, paying attention to the leading slash and capitalization.
- Enable TLS, set SNI to the domain specified by the service provider, and enter the WS Host as instructed. Do not disable certificate verification just to get connected. If you see a certificate error, first check the domain, your device’s time, and the configuration.
- Save and select the node, then enable the system proxy. On mobile, follow the prompts to allow a VPN connection. First, use rule mode to access the target website, then check the client’s connection log.
If you use free nodes provided by this site, use the parameters and compatible clients listed in the current release. Free node availability can change, and a successful import does not guarantee that a connection will work.
3. Troubleshoot connection failures in this order
First, turn off any other VPN or proxy, confirm that your device can access the internet, and enable automatic time synchronization. Then check whether the subscription is up to date, the node is selected, and the system proxy is active. If the log reports a handshake or certificate error, focus on TLS, SNI, and your device’s time. If the WebSocket handshake fails, check Host and Path and confirm the service status with the provider. If the connection keeps timing out, try a different network or another available node.
Change only one parameter at a time and keep the original configuration so you can identify the cause. Before sharing logs, hide sensitive information such as the subscription URL, UUID, and password.
4. How does team use relate to account environment stability?
WS+TLS does not guarantee a fixed exit IP or prevent an account from being asked to verify its identity. An account environment is also affected by the exit region, device, browser session, and platform rules. Teams should keep a record of frequently used nodes, their purposes, and when they were last updated, and avoid having multiple people change the configuration at once. For important work, avoid frequently switching between exit nodes in different regions.
Do not share personal subscription details in group chats. Before sharing a subscription with a team, confirm that the provider permits multiple users. If prompted to verify a login, follow the platform’s instructions rather than repeatedly switching nodes. A correct configuration solves connection problems; it does not guarantee a stable account environment.