This guide explains how to configure a “WS TLS node,” troubleshoot connection failures after importing one, and understand why the account environment can still change when used by a team. For clients that support VLESS or VMess, check the WebSocket and TLS settings against the node details. A successful connection does not mean the account environment is fixed; you should also check the outbound IP and routing rules.
1. Understand the difference between WS, TLS, and node protocols
VLESS and VMess are node protocols, WS (WebSocket) is a transport method, and TLS encrypts the connection. These are not interchangeable options. Use the complete link or subscription provided by the node provider as your reference. Don’t change a standard TCP node to WS TLS or arbitrarily replace the domain, path, or port.
Have the server address, port, user ID, protocol type, WS path, Host, and TLS server name (SNI) ready. Host and SNI may be the same or different. If any details are missing, ask the provider instead of guessing.
2. Install a client and import the node
- Install a client from the project’s official release page or a trusted app store—for example, v2rayN for Windows or v2rayNG for Android. Avoid modified versions from unknown sources.
- Copy the complete share link and select “Import from clipboard” in the client. If you have a subscription URL, add it in subscription management and then update it. Menu names may vary between clients.
- Open the node editor and check the protocol, server address, port, and user ID. The transport method should be WS or WebSocket.
- Check that the WS path includes its leading “/” and that Host matches the provided details. Don’t enter the entire URL in the Host field or remove parameters from the path.
- Confirm that TLS is enabled and check the SNI. Keep certificate validation enabled; don’t leave “Skip certificate verification” turned on to suppress errors. For other options, use the imported values where possible.
- Save and select the node, enable the system proxy or the VPN mode required by the client, visit the target website in a browser, and then check the connection logs.
Clients such as Clash and sing-box should import configuration in the appropriate format; not every client can directly recognize the same type of share link. If you use the free nodes on this site, first confirm which clients they support and whether they’re active. Subscription URLs may contain access credentials, so don’t share them publicly.
3. Troubleshoot connection failures in this order
- Subscription won’t update: Check that the URL is complete and your local network is working, then rule out an expired subscription.
- Connection times out: Check the address and port, confirm that the node is available, and try a different local network for comparison.
- TLS or certificate error: Check the system clock, SNI, and certificate domain. Prefer getting the original configuration again.
- WS handshake fails: Check the path and Host first. If you see a 403 or 404, save the logs and ask the provider to investigate.
- The connection test succeeds, but websites won’t load: Check the system proxy, routing rules, and DNS, and confirm that the target website is actually routed through the proxy.
4. What else affects team account stability
WS TLS describes only the connection method; it doesn’t guarantee a fixed outbound IP or prevent account verification checks. Automatic switching, failover, or subscription updates can change the outbound IP. Differences in routing rules can also cause some traffic to a website to go direct while other traffic uses the proxy.
Teams should standardize client versions and rules, use a verified node consistently for work, and record the outbound region and times of any changes. Avoid letting users switch nodes at will. Assign account permissions through the platform’s team features rather than sharing passwords. If an account triggers an unexpected verification check, first review outbound IP changes, login devices, and the platform’s notices; don’t keep switching nodes and retrying the login.