Reconnecting after the server stops and comes back
Checks that the app notices a server that stopped, and reconnects by itself once the server is back.
VERIFIED ā TESTED SUCCESSFULLY Tested on 10 November 2026 on the current app build against WaterWall 1.5.42, the official release, unchanged.
Result
| Outcome | Passed: every check succeeded. |
|---|---|
| Test length | 148 seconds, including connecting and disconnecting |
| HTTPS checks through the tunnel | Ping: 198 ms |
| Download phase 1 | 1,996 MB in 92 seconds (174 Mbit/s); errors: none |
| UDP phase 1 | Sustained UDP: 91.51 seconds, sent=900, received=900, errors=0, timeouts=0, passed=1, rtt_ms=36.949, jitter_ms=18.524, max_rtt_ms=209.550, retries=0 |
What the test does
- The profile uses Auto Reconnect on and Retry Times 2.
- The test connects. The test harness then stops the WaterWall copy on the server.
- The app must notice within 75 seconds that the connection no longer works.
- The harness starts the server copy again; the connection must be back within 45 seconds.
- The test runs the app's HTTPS check and 90 seconds of downloads and UDP echo exchange, then disconnects.
Passes when the app notices the failure, reconnects in time, and the checks after the reconnect succeed.
Test setup
The profile used the chain of the VLESS + TLS scenario, with the same server copy and profile settings, except the options the steps above change.
| Phone | iPhone 12 with iOS 27.2 (build 24B119), on Wi-Fi |
|---|---|
| App | SRP VPN Connect 1.2.0 (build 41), a Debug 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 program | The official WaterWall 1.5.42 release program, unchanged, the same program as our permanent test server, run as a test copy on port 4097 |
| Server DNS lookups | 5 tries, WaterWall 1.5.42's default; the test copy's core.json does not set it |
| Traffic | An HTTPS test server on the same machine, port 28483 |
| Network | Our office broadband line, over the public internet |
Gaps and limits
- The phone did not really sleep, and WaterWall inside the app did not really crash: a Debug build of the app accepts test commands that make the tunnel act as if it had. Stopping the server is real.
- Each step ran once, on one phone and one network.
Evidence
| Test case | lifecycle-peer-recovery-ww-00097-vless-tls |
|---|---|
| Run | 2026-11-10T10:58:13Z to 2026-11-10T11:08:39Z (UTC) |
| Step log times | 2026-11-10 14:04:23 to 2026-11-10 14:06:44 (phone time, UTC+3) |
| App source | commit e69cb668, Debug build |
| Server program | WaterWall 1.5.42, the official release, unchanged, SHA-256 38631081bd10347d⦠|
| Evidence file | waterwall-lifecycle-20261110T1058Z.json |