VLESS + WebSocket (HTTP/2) + Reality

Reality makes the connection start like a visit to another TLS website, so the server needs no certificate of its own. In this case a WebSocket layer makes it look like a web socket connection.

VERIFIED — TESTED SUCCESSFULLY  Tested on 10 November 2026 on the current app build against WaterWall 1.5.42, the official release, unchanged.

Result

OutcomePassed: every check succeeded.
Test length100 seconds
Downloaded1,493 MB (119 Mbit/s on average)
Uploaded470 MB (38 Mbit/s on average)
Transfers89 downloads and 28 uploads of 16 MiB; 8/8 streams finished at the end
Errorsnone
Timeouts0
Through the tunnelYes: the HTTPS test server saw these transfers come from <SERVER_IP>, and it would have seen the phone's own network if they had left outside the tunnel
HTTPS check through the tunnelPing: 255 ms; Ping: 162 ms
UDPnot-applicable: The generated connector does not support application UDP

Test setup

PhoneiPhone 12 with iOS 27.2 (build 24B119), on Wi-Fi
AppSRP VPN Connect 1.2.0 (build 41), a Release build of commit e69cb668, installed by Xcode for the test. TestFlight build 41 is commit e44cf11d, with the same app code: the commits after it change only the tests and the change log
Server machineUbuntu 24.04.5 LTS, VMware virtual machine with 2 vCPUs and 2 GB RAM
Server programThe official WaterWall 1.5.42 release program, unchanged, the same program as our permanent test server, run as a separate test copy for each case
Server DNS lookups5 tries, WaterWall 1.5.42's default; the test copy's core.json does not set it
Server port4097, opened in the firewall only for our office address while the case ran
TrafficAn HTTPS test server on the same machine, port 28483, that serves a 16 MiB file and checks each upload. On Raw IPv4 and native WireGuard chains the phone reaches it at the server's private address 10.44.0.1, because iOS sends traffic for the server's own public address outside the tunnel; the test then trusts its certificate by comparing it with a copy, since the name in it is not that address
NetworkOur office broadband line, over the public internet
iPhone 12 with SRP VPN Connect
      |
      |  Wi-Fi, office broadband, internet
      v
Test server <SERVER_IP>
  WaterWall test copy, port 4097           the chain under test
      |
      |  inside the same machine
      v
  HTTPS test server, port 28483            download file and upload checker

Server configuration

The test harness wrote this file for the case and started our WaterWall program with it. It is shown as it ran; only the server address, the UUID and the passwords are replaced with placeholders. The certificate files are a self-signed test certificate made for the run. On your own server, use your own port, certificate and secrets, as described in Installation.

{
  "name": "ww-00258-vless-reality-peer",
  "nodes": [
    {
      "name": "listener",
      "type": "TcpListener",
      "settings": {
        "address": "<SERVER_IP>",
        "port": 4097
      },
      "next": "reality"
    },
    {
      "name": "reality",
      "type": "RealityServer",
      "settings": {
        "password": "<OUTER_PASSWORD>",
        "algorithm": "chacha20-poly1305",
        "salt": "waterwall-reality",
        "kdf-iterations": 12000,
        "destination": "cover"
      },
      "next": "http"
    },
    {
      "name": "http",
      "type": "HttpServer",
      "settings": {
        "path": "/",
        "http-version": 2,
        "websocket": true
      },
      "next": "vless"
    },
    {
      "name": "vless",
      "type": "VlessServer",
      "settings": {
        "uuid": "<UUID>",
        "verbose": true
      },
      "next": "out"
    },
    {
      "name": "out",
      "type": "TcpUdpConnector",
      "settings": {
        "address": "dest_context->address",
        "port": "dest_context->port",
        "dns-behaviour": {
          "resolve": true,
          "strategy": "prefer-ipv4"
        },
        "nodelay": true
      }
    },
    {
      "name": "cover",
      "type": "TcpConnector",
      "settings": {
        "address": "127.0.0.1",
        "port": 4098,
        "nodelay": true
      }
    }
  ]
}

The Reality cover site in this test was a second TLS server on the same machine:

{
  "name": "cover-peer",
  "nodes": [
    {
      "name": "listener",
      "type": "TcpListener",
      "settings": {
        "address": "127.0.0.1",
        "port": 4098
      },
      "next": "tls"
    },
    {
      "name": "tls",
      "type": "TlsServer",
      "settings": {
        "cert-file": "/tmp/srp-device-matrix/cert.pem",
        "key-file": "/tmp/srp-device-matrix/key.pem"
      },
      "next": "blackhole"
    },
    {
      "name": "blackhole",
      "type": "BlackHole",
      "settings": {
        "mode": "passive"
      }
    }
  ]
}
The test copy's core.json
{
  "misc": {
    "workers": 1,
    "ram-profile": "minimal",
    "splice": false,
    "try-enabling-bbr": false,
    "tcp-tune": false
  },
  "configs": [
    "/tmp/srp-device-matrix/peer.json",
    "/tmp/srp-device-matrix/cover.json"
  ]
}

App settings

On the WaterWall configuration screen:

RowValue
ModeChain
InputConnections
ApplicationVLESS
MUXOff
ObfuscatorOff
HTTPWebSocket
HTTP Version2
BGP4 FramingOff
OuterReality
CarrierTCP

In the profile editor:

Server<SERVER_IP>, the test server's address
Port4097
SNI (optional)localhost, for chains with TLS, Reality or QUIC
TLS Server VerificationOff, because the test certificate is self-signed
UUID or Password<UUID>, a test value
Reality or AEAD Password<OUTER_PASSWORD>, a test value, when the chain uses one
Auto ReconnectOff, so that a reconnect cannot hide a failure
On SleepStay
Log LevelNormal
Remote DNS (Fake IP)On
Direct LAN RoutingOn
The client chain the app built (for reference)
{
  "name": "VLESS + WebSocket + REALITY",
  "nodes": [
    {
      "settings": {},
      "name": "ne",
      "type": "NEPacketDevice",
      "next": "ptc"
    },
    {
      "settings": {
        "max-total-pending-bytes": 16777216,
        "mtu": 1420,
        "fake-dns": {
          "address": "198.18.0.2",
          "netmask": "255.192.0.0",
          "enabled": true,
          "port": 53,
          "ttl": 60,
          "cache-size": 10000,
          "network": "100.64.0.0"
        },
        "max-pending-bytes": 65536
      },
      "name": "ptc",
      "type": "PacketsToConnection",
      "next": "router"
    },
    {
      "settings": {
        "port": "dest_context->port",
        "address": "dest_context->address",
        "protocol": "dest_context->protocol",
        "uuid": "<UUID>"
      },
      "name": "vless",
      "type": "VlessClient",
      "next": "http"
    },
    {
      "settings": {},
      "name": "router",
      "type": "Router",
      "next": "vless"
    },
    {
      "settings": {
        "path": "/",
        "http-version": 2,
        "host": "localhost",
        "websocket": true,
        "scheme": "https",
        "port": 4097
      },
      "name": "http",
      "type": "HttpClient",
      "next": "reality"
    },
    {
      "settings": {
        "kdf-iterations": 12000,
        "password": "<OUTER_PASSWORD>",
        "verify": false,
        "alpns": [
          "h2"
        ],
        "algorithm": "chacha20-poly1305",
        "verbose": false,
        "salt": "waterwall-reality",
        "sni": "localhost"
      },
      "name": "reality",
      "type": "RealityClient",
      "next": "connector"
    },
    {
      "name": "connector",
      "type": "TcpConnector",
      "settings": {
        "address": "127.0.0.1",
        "nodelay": true,
        "port": 4097
      }
    }
  ]
}

How it was tested

  1. Xcode installed the app's test build on the phone, and the test created the profile shown above in memory. It was not added to the app's profile list.
  2. The test connected the VPN and waited until iOS reported it connected.
  3. It ran the app's own HTTPS check through the tunnel: a request to https://gstatic.com/generate_204, which must answer 204.
  4. For at least 90 seconds it ran 4 downloads and 4 uploads at the same time, over and over. Each download fetched a 16 MiB file from the HTTPS test server. Each upload sent 16 MiB, and the server answered with the size and SHA-256 it received, which the test compared with what it sent.
  5. It ran the HTTPS check again and disconnected.

A case passes only if the VPN stayed connected, the test ran the full 90 seconds, every transfer finished, there were no errors and no timeouts, data moved in both directions, both HTTPS checks succeeded, and the HTTPS test server saw the transfers come through the tunnel (Direct mode and the GeoIP cases leave outside it by design and are not checked).

Gaps and limits

Evidence

Test caseww-00258-vless-reality
Why it was selectedpairwise (+2 pairs)
Run2026-11-10T11:39:10Z to 2026-11-10T15:17:28Z (UTC)
Case log times2026-11-10 15:15:36 to 2026-11-10 15:17:20 (phone time, UTC+3)
App sourcecommit e69cb668
Server programWaterWall 1.5.42, the official release, unchanged, SHA-256 38631081bd10347d…
Evidence filewaterwall-matrix-20261110T1139Z.json