Share Link Parameters
Mole supports an extended set of parameters for each protocol. Below are the technical details for correctly forming links.
VLESS
The recommended protocol for bypassing blocks using Reality and Vision.
Example:
vless://uuid@host:port?security=reality&sni=google.com&fp=chrome&pbk=publicKey&sid=shortId&flow=xtls-rprx-vision&type=tcp#ServerName
| Parameter | Description |
|---|---|
security |
reality or tls |
sni |
Domain to imitate |
fp |
Browser fingerprint (chrome, firefox, safari, edge) |
pbk |
Public Key for Reality |
flow |
xtls-rprx-vision (recommended for TCP+Reality) |
type |
Transport: tcp, ws, grpc or xhttp |
alpn |
ALPN list, e.g. h3 for HTTP/3. Implies TLS |
mode |
XHTTP mode: auto (default), stream-one, stream-up, packet-up |
Transports that no longer exist
Xray-core removed both the HTTP/2 (type=h2) and the standalone QUIC
(type=quic) transports, so links using them cannot connect on any client built
on a current core — Mole rejects them with an explanatory message rather than
failing silently. QUIC's replacement is XHTTP over HTTP/3: type=xhttp with
mode=stream-one and alpn=h3. For a QUIC-based protocol, use Hysteria2.
Hysteria2
A QUIC-based protocol, optimized for unstable networks.
Example:
hysteria2://password@host:port?sni=example.com&obfs=salamander&obfs-password=pass&up=100&down=200#ServerName
| Parameter | Description |
|---|---|
sni |
Domain presented in the TLS handshake |
obfs |
salamander — the only obfuscation Hysteria2 defines. Needs obfs-password to take effect |
obfs-password |
Obfuscation password |
up / down |
Bandwidth in Mbps. Also accepted as upmbps / downmbps, and with a unit suffix (up=100mbps). Declaring both switches on the "brutal" congestion controller; omit them to stay on BBR |
insecure |
1 or true disables certificate verification |
alpn |
ALPN to pin. Left to the core's default (h3) when absent |
fp |
Browser fingerprint |
Shadowsocks (SS)
Support for AEAD ciphers and SIP002.
Example:
ss://base64(cipher:password)@host:port#ServerName