This article explains “how to configure a WS TLS node”: If you have a V2Ray/VLESS/VMess WebSocket + TLS node but aren’t sure where to enter each setting, or it connects after import but you can’t open webpages, follow the steps below to check your IP, DNS, and browser setup.
1. Understand what information a WS TLS node requires
WS TLS is not a standalone account type, but a common combination of proxy protocol and transport. You’ll usually receive a share link or a set of parameters: address, port, UUID/password, transport protocol, path, Host, TLS/SNI, and so on. If you’re a regular user, import a subscription or link whenever possible; enter the settings manually only if importing fails.
- Protocol: Common options include VLESS and VMess; it may also be Trojan.
- Transport: Select WebSocket, abbreviated as WS.
- TLS: Enable it. Port 443 is common, but use the port specified in the node details.
- Path: Usually a path such as /xxx. It must match exactly.
- Host/SNI: Usually the domain provided for the node. Don’t change it to an IP address without a reason.
2. Configure a WS TLS node in your client
For clients such as v2rayN, Clash Verge, and sing-box, we recommend the following steps:
- Copy the node link or subscription URL provided by this site or another source.
- Open your client and select “Import from clipboard” or “Subscription management.”
- Update the subscription, then select a WS TLS node.
- Enable the system proxy. Start with rule mode; you can temporarily use global mode for testing.
- Open a browser and visit a test site to check that it loads properly.
If you need to add the node manually, note that the address is usually a domain name. Enter the port provided for the node, select WS as the transport, enable TLS, and enter the Path, Host, and SNI exactly as provided. Don’t change the address to an IP just because you see one after DNS resolution; this can cause certificate validation to fail or the SNI to mismatch.
3. How IP, DNS, and your browser setup affect the connection
Many connection failures are caused not by a broken node, but by a mismatch with your local setup. Your IP mainly affects your outbound address and how your destination identifies you; DNS determines whether a domain resolves to the correct address; and your browser setup affects whether the proxy is actually being used.
For DNS, if your client supports “remote DNS” or “proxy DNS,” we recommend enabling it to avoid DNS tampering by your local ISP. In Clash-style clients, check that the DNS module is enabled; in sing-box, check the DNS settings in the app. If you’re a regular user, avoid changing your system network adapter’s DNS settings repeatedly. It’s more reliable to start with the client’s default settings.
For your browser, make sure you don’t have multiple proxy extensions that conflict with each other. In Chrome or Edge, enabling the system proxy in the client is usually enough. If you’ve configured a proxy separately in Firefox, change the setting to “Use system proxy.” Incognito windows, privacy extensions, and ad blockers can sometimes affect test results too.
4. Quick troubleshooting for connection failures
- “TLS handshake failed”: First check the SNI, Host, and whether your system clock is correct.
- Connected but webpages won’t load: Switch between rule and global mode, then check your DNS settings.
- Subscription imports with no nodes: Make sure the subscription URL is complete and that you haven’t copied extra spaces or line breaks.
- Latency shows -1: Test a different node or check whether your local network is blocking that port.
- Only the browser can’t connect: Disable proxy extensions and confirm that the browser is using the system proxy.
In summary, configuring a WS TLS node isn’t about entering more parameters; it’s about making sure the protocol, WS path, TLS, and Host/SNI all match. This site collects free nodes that you can import for temporary testing. If you can’t connect, use this article to check your client, DNS, and browser setup. This will usually help you identify most issues.