Test Results

Every AmneziaWG case we ran on 9 November 2026, with its result on an iPhone and on an Android phone: 70 of 70 cases passed on the iPhone and 65 of 65 on Android.

How these tests ran

The phones were an iPhone 12 with iOS 27.2 and a Samsung Galaxy A55 with Android 17, with the code of commit 0a699819 on both phones, as a Debug build on the iPhone and as a debug APK on Android; the iPhone's awg-release-… rows come from a Release build of the same code, the kind TestFlight ships, and the awg-kernel-module-… rows on both phones from builds with the same engine made before 0a699819's change to the log note. The server was our amneziawg-go fork (github.com/bigmoveus/amneziawg-go, tag v3.1.20260828-srp.1, built as AmneziaWG server shows) with amneziawg-tools 3.1.20260812 from the Amnezia packages, on Ubuntu 24.04 with Linux 6.8: eight interfaces like the one AmneziaWG server sets up, awg0 to awg7 on UDP ports 51830 to 51837, one for each generation of AmneziaWG (the Settings column names it; awg7 is awg4 without a header protection key), with a peer of its own for each phone and for the files without a preshared key and with the wrong one.

How to read the results

LabelMeaning
VERIFIED — TESTED SUCCESSFULLYThe case did what its row expects: it connected and moved its traffic through the tunnel, or it was refused with the message shown.
TESTED — FAILEDThe case did not do what its row expects; the row says what happened.
NOT VERIFIEDThe case did not run on that phone.

Speeds are averages over the whole transfer on our office line. They show that traffic moved, and are not a benchmark. When both directions ran at once on the iPhone, the uploads took most of the line.

Not tested in this round

Transfers and UDP

CaseSettingsTrafficExpectediPhoneAndroid
awg-downloadthe phone's awg0 file: AmneziaWG 2.0: S1-S4, H1-H4 ranges; Jc, Jmin, Jmax and I1 on the phone; MTU 1396; preshared keydownload, 60 sconnectVERIFIED — TESTED SUCCESSFULLY
211.21 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/ios1 8 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 4.0 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/android1 13 s before it was asked
awg-uploadthe phone's awg0 file: AmneziaWG 2.0: S1-S4, H1-H4 ranges; Jc, Jmin, Jmax and I1 on the phone; MTU 1396; preshared keyupload, 45 sconnectVERIFIED — TESTED SUCCESSFULLY
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
up 219.18 Mbit/s
the server had a handshake with the peer awg0/ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 8.3 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/android1 12 s before it was asked
awg-full-duplexthe phone's awg0 file: AmneziaWG 2.0: S1-S4, H1-H4 ranges; Jc, Jmin, Jmax and I1 on the phone; MTU 1396; preshared keydownload and upload at once, 60 sconnectVERIFIED — TESTED SUCCESSFULLY
down 81.19 / up 164.51 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/ios1 8 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 8.4 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/android1 13 s before it was asked
awg-many-connectionsthe phone's awg0 file: AmneziaWG 2.0: S1-S4, H1-H4 ranges; Jc, Jmin, Jmax and I1 on the phone; MTU 1396; preshared key16 downloads at once, 45 sconnectVERIFIED — TESTED SUCCESSFULLY
231.07 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 20.7 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/android1 13 s before it was asked
awg-udp-probethe phone's awg0 file: AmneziaWG 2.0: S1-S4, H1-H4 ranges; Jc, Jmin, Jmax and I1 on the phone; MTU 1396; preshared keydownload, 15 s, and a DNS query over UDPconnectVERIFIED — TESTED SUCCESSFULLY
193.93 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/ios1 7 s before it was asked
the UDP DNS query was answered, and saw the server's address
VERIFIED — TESTED SUCCESSFULLY
transfer 3.9 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/android1 16 s before it was asked
the UDP DNS query was answered, and saw the server's address

The generations of AmneziaWG

CaseSettingsTrafficExpectediPhoneAndroid
awg-gen-1-0the phone's awg1 file: AmneziaWG 1.0: S1, S2, single H1-H4; Jc, Jmin, Jmax on the phone; preshared keydownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
190.97 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg1/ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 3.9 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg1/android1 13 s before it was asked
awg-gen-1-5the phone's awg2 file: AmneziaWG 1.5: as 1.0, with I1-I3 on the phone; preshared keydownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
204.0 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg2/ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 4.0 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg2/android1 13 s before it was asked
awg-gen-3-0the phone's awg3 file: AmneziaWG 3.0: as 2.0, with HeaderProtectionKey and ContentPaddingAddition; the five timings and a 20-30 s keepalive on the phone; MTU 1404; preshared keydownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
198.02 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg3/ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 3.8 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg3/android1 12 s before it was asked
awg-gen-3-1the phone's awg6 file: AmneziaWG 3.1: as 3.0, with RandomTrailers and DisableCookies, single H1-H4; preshared keydownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
218.24 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg6/ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 3.9 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg6/android1 13 s before it was asked
awg-gen-3-1-rangesthe phone's awg4 file: AmneziaWG 3.1: as 3.0, with RandomTrailers and DisableCookies, H1-H4 ranges; preshared keydownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
201.05 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg4/ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 4.0 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg4/android1 12 s before it was asked
awg-gen-nonethe phone's awg5 file: no obfuscation (WireGuard's own format); preshared keydownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
207.33 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg5/ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 3.9 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg5/android1 13 s before it was asked

RandomTrailers with ranges in H1-H3, both directions

CaseSettingsTrafficExpectediPhoneAndroid
awg-ranges-trailers-downloadthe phone's awg4 file: AmneziaWG 3.1: as 3.0, with RandomTrailers and DisableCookies, H1-H4 ranges; preshared keydownload, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
185.36 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg4/ios1 8 s before it was asked
in the log: the session line, the obfuscation line
not in the log: ranges in H1-H3 and no HeaderProtectionKey, the current AmneziaWG engines drop some data packets, the file's private key, the file's preshared key, the file's header protection key
VERIFIED — TESTED SUCCESSFULLY
transfer 3.9 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg4/android1 13 s before it was asked
in the log: the session line, the obfuscation line
not in the log: ranges in H1-H3 and no HeaderProtectionKey, the current AmneziaWG engines drop some data packets, the file's private key, the file's preshared key, the file's header protection key
awg-ranges-trailers-uploadthe phone's awg4 file: AmneziaWG 3.1: as 3.0, with RandomTrailers and DisableCookies, H1-H4 ranges; preshared keyupload, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
up 213.81 Mbit/s
the server had a handshake with the peer awg4/ios1 8 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 8.4 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg4/android1 12 s before it was asked
awg-ranges-trailers-no-hpk-downloadthe phone's awg7 file: AmneziaWG 3.1 without header protection: as awg4, without HeaderProtectionKey; preshared keydownload, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
181.78 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg7/ios1 8 s before it was asked
in the log: the session line, ranges in H1-H3 and no HeaderProtectionKey
not in the log: the current AmneziaWG engines drop some data packets, the file's private key, the file's preshared key
VERIFIED — TESTED SUCCESSFULLY
transfer 3.8 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg7/android1 13 s before it was asked
in the log: the session line, ranges in H1-H3 and no HeaderProtectionKey
not in the log: the current AmneziaWG engines drop some data packets, the file's private key, the file's preshared key
awg-ranges-trailers-no-hpk-uploadthe phone's awg7 file: AmneziaWG 3.1 without header protection: as awg4, without HeaderProtectionKey; preshared keyupload, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
up 214.78 Mbit/s
the server had a handshake with the peer awg7/ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 8.3 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg7/android1 13 s before it was asked

The same against AmneziaWG's kernel module, unchanged

CaseSettingsTrafficExpectediPhoneAndroid
awg-kernel-module-trailers-downloadthe phone's awg4 file: AmneziaWG 3.1: as 3.0, with RandomTrailers and DisableCookies, H1-H4 ranges; preshared key; against the kernel module from the Amnezia packages, unchangeddownload, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
199.06 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg4/ios1 8 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 3.9 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg4/android1 13 s before it was asked
awg-kernel-module-trailers-uploadthe phone's awg4 file: AmneziaWG 3.1: as 3.0, with RandomTrailers and DisableCookies, H1-H4 ranges; preshared key; against the kernel module from the Amnezia packages, unchangedupload, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
up 220.03 Mbit/s
the server had a handshake with the peer awg4/ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 8.3 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg4/android1 13 s before it was asked
awg-kernel-module-trailers-no-hpk-downloadthe phone's awg7 file: AmneziaWG 3.1 without header protection: as awg4, without HeaderProtectionKey; preshared key; against the kernel module from the Amnezia packages, unchangeddownload, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
212.17 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg7/ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 3.7 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg7/android1 13 s before it was asked
awg-kernel-module-trailers-no-hpk-uploadthe phone's awg7 file: AmneziaWG 3.1 without header protection: as awg4, without HeaderProtectionKey; preshared key; against the kernel module from the Amnezia packages, unchangedupload, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
up 31.02 Mbit/s
the server had a handshake with the peer awg7/ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 36.7 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg7/android1 13 s before it was asked

The configuration

CaseSettingsTrafficExpectediPhoneAndroid
awg-no-pskthe awg0 file of a peer without a preshared keydownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
194.97 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/nopsk 8 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 4.0 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/nopsk 12 s before it was asked
awg-no-keepalivethe phone's awg0 file without PersistentKeepalivedownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
196.39 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 3.9 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/android1 12 s before it was asked
awg-no-mtuthe phone's awg0 file without MTU (the app takes 1420 - S4 = 1396)download, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
195.67 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/ios1 7 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 3.9 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/android1 14 s before it was asked
awg-mtu-1280the phone's awg0 file with MTU = 1280download, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
180.89 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/ios1 8 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 3.9 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/android1 13 s before it was asked
awg-endpoint-ipthe phone's awg0 file with the server's address as Endpointconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer awg0/ios1 1 s before it was asked
held for 6 s
VERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer awg0/android1 3 s before it was asked
held for 6 s
awg-split-tunnelthe phone's awg0 file with AllowedIPs = 10.67.0.0/24download, 15 s, and a DNS query over UDPconnectVERIFIED — TESTED SUCCESSFULLY
200.09 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer awg0/ios1 8 s before it was asked
the UDP DNS query was answered, and saw the phone's own network
VERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer awg0/android1 19 s before it was asked
the UDP DNS query was answered, and saw the phone's own network
the server's tunnel address answered a ping: 3 packets transmitted, 3 received, 0% packet loss, time 2004ms
awg-manual-configurationthe phone's awg0 file: AmneziaWG 2.0: S1-S4, H1-H4 ranges; Jc, Jmin, Jmax and I1 on the phone; MTU 1396; preshared key; the same values entered under Manual Configuration instead of a fileconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer awg0/ios1 1 s before it was asked
held for 6 s
VERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer awg0/android1 3 s before it was asked
held for 6 s
awg-manual-configuration-3the phone's awg3 file: AmneziaWG 3.0: as 2.0, with HeaderProtectionKey and ContentPaddingAddition; the five timings and a 20-30 s keepalive on the phone; MTU 1404; preshared key; the same values entered under Manual Configuration instead of a fileconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer awg3/ios1 2 s before it was asked
held for 6 s
VERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer awg3/android1 3 s before it was asked
held for 6 s

Server and Port

CaseSettingsTrafficExpectediPhoneAndroid
awg-port-field-overrides-profilethe phone's awg0 file with Endpoint port 51839 (nothing listens); Port 51830connect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer awg0/ios1 1 s before it was asked
held for 6 s
VERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer awg0/android1 3 s before it was asked
held for 6 s
awg-server-field-overrides-profilethe phone's awg0 file with an Endpoint name that does not exist; Server: the server's nameconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer awg0/ios1 1 s before it was asked
held for 6 s
VERIFIED — TESTED SUCCESSFULLY
the server had a handshake with the peer awg0/android1 3 s before it was asked
held for 6 s

Refusals and damaged files

CaseSettingsTrafficExpectediPhoneAndroid
awg-wrong-server-keythe phone's awg0 file with a server public key of nobodyconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.2 s
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51830 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51830 may be closed.
awg-unknown-client-keythe phone's awg0 file with a private key the server does not haveconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.2 s
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51830 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51830 may be closed.
awg-wrong-pskan awg0 file whose preshared key is not the server's for its peerconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.1 s
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51830 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51830 may be closed.
awg-closed-portthe phone's awg0 file with Endpoint port 51839 (nothing listens)connect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.2 s
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51839 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51839 may be closed.
awg-unknown-hostthe phone's awg0 file with an Endpoint name that does not existconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.4 s
The AmneziaWG endpoint no-such-host.srp.invalid could not be resolved.
VERIFIED — TESTED SUCCESSFULLY
The AmneziaWG endpoint no-such-host.srp.invalid could not be resolved.
awg-bad-keythe phone's awg0 file with a damaged private keyconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.5 s
Invalid AmneziaWG config: a key is not valid base64 (32 bytes).
VERIFIED — TESTED SUCCESSFULLY
Invalid AmneziaWG config: a key is not valid base64 (32 bytes).
awg-bad-preshared-keythe phone's awg0 file with a damaged preshared keyconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.4 s
Invalid AmneziaWG config: the PresharedKey is not valid base64 (32 bytes).
VERIFIED — TESTED SUCCESSFULLY
Invalid AmneziaWG config: the PresharedKey is not valid base64 (32 bytes).
awg-retry-before-connectthe phone's awg0 file with Endpoint port 51839 (nothing listens); Port 51839; Retry Times 2connect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 31.3 s
Could not connect after 3 attempts. (The server did not answer the AmneziaWG handshake.)
VERIFIED — TESTED SUCCESSFULLY
Could not connect after 3 attempts. (The server did not answer the AmneziaWG handshake.)
awg-no-addressthe phone's awg0 file without Addressconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.3 s
Invalid AmneziaWG config: The config has no [Interface] Address.
VERIFIED — TESTED SUCCESSFULLY
Invalid AmneziaWG config: The config has no [Interface] Address.
awg-garbage-configa file with [Interface] and [Peer] but no valuesconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.5 s
Invalid AmneziaWG config: The config has no [Interface] PrivateKey.
VERIFIED — TESTED SUCCESSFULLY
Invalid AmneziaWG config: The config has no [Interface] PrivateKey.
awg-wireguard-filethe phone's awg0 file without any AmneziaWG setting (a WireGuard file)connect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.2 s
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51830 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51830 may be closed.
awg-invalid-h1the phone's awg0 file with H1 = abcconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.4 s
Invalid AmneziaWG config: H1 must be a number or a range such as 1000000-1999999.
VERIFIED — TESTED SUCCESSFULLY
Invalid AmneziaWG config: H1 must be a number or a range such as 1000000-1999999.
awg-invalid-i1the phone's awg0 file with I1 = <x 12> (no such tag)connect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 1.1 s
AmneziaWG refused the configuration: failed to parse I1: unknown tag <x>
VERIFIED — TESTED SUCCESSFULLY
AmneziaWG refused the configuration: failed to parse I1: unknown tag <x>
awg-invalid-header-protection-keythe phone's awg3 file with a damaged HeaderProtectionKeyconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.4 s
Invalid AmneziaWG config: the HeaderProtectionKey is not valid base64 (32 bytes).
VERIFIED — TESTED SUCCESSFULLY
Invalid AmneziaWG config: the HeaderProtectionKey is not valid base64 (32 bytes).

Obfuscation that differs from the server's

CaseSettingsTrafficExpectediPhoneAndroid
awg-s1-mismatchthe phone's awg0 file with S1 = 65 (the server has 64)connect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.2 s
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51830 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51830 may be closed.
awg-h1-mismatchthe phone's awg0 file with another H1 rangeconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.1 s
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51830 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51830 may be closed.
awg-hpk-mismatchthe phone's awg3 file with another HeaderProtectionKeyconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.1 s
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51833 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51833 may be closed.
awg-hpk-missingthe phone's awg3 file without HeaderProtectionKeyconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.1 s
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51833 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51833 may be closed.
awg-trailers-missingthe phone's awg6 file without RandomTrailersconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.1 s
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51836 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51836 may be closed.
awg-life-s4-mismatchthe phone's awg0 file with S4 = 25 (the server has 24); Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
ended after 45.5 s with: The server answers the AmneziaWG handshake but none of the traffic: S3, S4 or H4 may differ from the server's.
VERIFIED — TESTED SUCCESSFULLY
connected, ended 47.0 s later with: The server answers the AmneziaWG handshake but none of the traffic: S3, S4 or H4 may differ from the server's.
awg-life-h4-mismatchthe phone's awg0 file with another H4 range; Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
ended after 50.5 s with: The server answers the AmneziaWG handshake but none of the traffic: S3, S4 or H4 may differ from the server's.
VERIFIED — TESTED SUCCESSFULLY
connected, ended 47.0 s later with: The server answers the AmneziaWG handshake but none of the traffic: S3, S4 or H4 may differ from the server's.
awg-life-s4-mismatch-no-reconnectthe phone's awg0 file with S4 = 25 (the server has 24); Auto Reconnect offconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
ended after 50.5 s with: The server answers the AmneziaWG handshake but none of the traffic: S3, S4 or H4 may differ from the server's.
VERIFIED — TESTED SUCCESSFULLY
connected, ended 47.1 s later with: The server answers the AmneziaWG handshake but none of the traffic: S3, S4 or H4 may differ from the server's.

Log levels

CaseSettingsTrafficExpectediPhoneAndroid
awg-log-normalthe phone's awg3 file: AmneziaWG 3.0: as 2.0, with HeaderProtectionKey and ContentPaddingAddition; the five timings and a 20-30 s keepalive on the phone; MTU 1404; preshared key; Log Level Normaldownload, 40 sconnectVERIFIED — TESTED SUCCESSFULLY
194.05 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
in the log: the session line, the obfuscation line
not in the log: a private key line, a preshared key line, a header protection key line, the engine's private key, the engine's preshared key, the engine's header protection key, the 30-second handshake and byte line, AmneziaWG's own lines, the file's private key, the file's preshared key, the file's header protection key
VERIFIED — TESTED SUCCESSFULLY
transfer 3.8 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
held for 40 s
in the log: the session line, the obfuscation line
not in the log: a private key line, a preshared key line, a header protection key line, the engine's private key, the engine's preshared key, the engine's header protection key, the 30-second handshake and byte line, AmneziaWG's own lines, the file's private key, the file's preshared key, the file's header protection key
awg-log-expertthe phone's awg3 file: AmneziaWG 3.0: as 2.0, with HeaderProtectionKey and ContentPaddingAddition; the five timings and a 20-30 s keepalive on the phone; MTU 1404; preshared key; Log Level Expertdownload, 40 sconnectVERIFIED — TESTED SUCCESSFULLY
190.79 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
in the log: the session line, the 30-second handshake and byte line
not in the log: a private key line, a preshared key line, a header protection key line, the engine's private key, the engine's preshared key, the engine's header protection key, AmneziaWG's own lines, the file's private key, the file's preshared key, the file's header protection key
VERIFIED — TESTED SUCCESSFULLY
transfer 3.9 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
held for 40 s
in the log: the session line, the 30-second handshake and byte line
not in the log: a private key line, a preshared key line, a header protection key line, the engine's private key, the engine's preshared key, the engine's header protection key, AmneziaWG's own lines, the file's private key, the file's preshared key, the file's header protection key
awg-log-debugthe phone's awg3 file: AmneziaWG 3.0: as 2.0, with HeaderProtectionKey and ContentPaddingAddition; the five timings and a 20-30 s keepalive on the phone; MTU 1404; preshared key; Log Level Debugdownload, 4 sconnectVERIFIED — TESTED SUCCESSFULLY
141.03 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
in the log: the session line, AmneziaWG's own lines
not in the log: a private key line, a preshared key line, a header protection key line, the engine's private key, the engine's preshared key, the engine's header protection key, the file's private key, the file's preshared key, the file's header protection key
VERIFIED — TESTED SUCCESSFULLY
transfer 3.9 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
in the log: the session line, AmneziaWG's own lines
not in the log: a private key line, a preshared key line, a header protection key line, the engine's private key, the engine's preshared key, the engine's header protection key, the file's private key, the file's preshared key, the file's header protection key
awg-release-log-normalthe phone's awg3 file: AmneziaWG 3.0: as 2.0, with HeaderProtectionKey and ContentPaddingAddition; the five timings and a 20-30 s keepalive on the phone; MTU 1404; preshared key; Log Level Normaldownload, 40 sconnectVERIFIED — TESTED SUCCESSFULLY
157.52 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
Release build
in the log: the session line, the obfuscation line
not in the log: a private key line, a preshared key line, a header protection key line, the engine's private key, the engine's preshared key, the engine's header protection key, the 30-second handshake and byte line, AmneziaWG's own lines, the file's private key, the file's preshared key, the file's header protection key
NOT VERIFIED
awg-release-log-expertthe phone's awg3 file: AmneziaWG 3.0: as 2.0, with HeaderProtectionKey and ContentPaddingAddition; the five timings and a 20-30 s keepalive on the phone; MTU 1404; preshared key; Log Level Expertdownload, 40 sconnectVERIFIED — TESTED SUCCESSFULLY
189.92 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
Release build
in the log: the session line, the 30-second handshake and byte line
not in the log: a private key line, a preshared key line, a header protection key line, the engine's private key, the engine's preshared key, the engine's header protection key, AmneziaWG's own lines, the file's private key, the file's preshared key, the file's header protection key
NOT VERIFIED
awg-release-log-debugthe phone's awg3 file: AmneziaWG 3.0: as 2.0, with HeaderProtectionKey and ContentPaddingAddition; the five timings and a 20-30 s keepalive on the phone; MTU 1404; preshared key; Log Level Debugdownload, 4 sconnectVERIFIED — TESTED SUCCESSFULLY
142.78 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
Release build
in the log: the session line, AmneziaWG's own lines
not in the log: a private key line, a preshared key line, a header protection key line, the engine's private key, the engine's preshared key, the engine's header protection key, the file's private key, the file's preshared key, the file's header protection key
NOT VERIFIED
awg-release-downloadthe phone's awg0 file: AmneziaWG 2.0: S1-S4, H1-H4 ranges; Jc, Jmin, Jmax and I1 on the phone; MTU 1396; preshared keydownload, 60 sconnectVERIFIED — TESTED SUCCESSFULLY
193.34 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
Release build
the server had a handshake with the peer awg0/iosrel 8 s before it was asked
NOT VERIFIED
awg-release-wrong-server-keythe Release build's awg0 file with a server public key of nobody; Log Level Expertconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
Release build
ended after 11.1 s
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51830 may be closed.
NOT VERIFIED

Sleep, a server that goes away, network changes and Retry Times

CaseSettingsTrafficExpectediPhoneAndroid
awg-life-sleep-modesthe phone's awg0 file: AmneziaWG 2.0: S1-S4, H1-H4 ranges; Jc, Jmin, Jmax and I1 on the phone; MTU 1396; preshared key; On Sleep Stay, Pause and Off, and Off with Auto Reconnect offconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
On Sleep Stay, Auto Reconnect on: connected again after 3.3 s
On Sleep Pause, Auto Reconnect off: connected again after 3.2 s
On Sleep Off, Auto Reconnect on: connected again after 3.2 s
On Sleep Off, Auto Reconnect off: ended after 3.4 s with: The connection was closed while the device slept.
VERIFIED — TESTED SUCCESSFULLY
stayed connected through 10 s of sleep; transfer after wake passed
paused at sleep, connected again at wake; transfer passed
closed at sleep, connected again at wake; transfer passed
ended at wake: The connection was closed while the device slept.
awg-life-server-restartthe phone's awg0 file: AmneziaWG 2.0: S1-S4, H1-H4 ranges; Jc, Jmin, Jmax and I1 on the phone; MTU 1396; preshared key; the server's awg0 restarts (awg-quick); Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
connected again after 16.1 s
VERIFIED — TESTED SUCCESSFULLY
traffic passed again 18.8 s after the restart; transfer passed
awg-life-outage-reconnectthe phone's awg0 file: AmneziaWG 2.0: S1-S4, H1-H4 ranges; Jc, Jmin, Jmax and I1 on the phone; MTU 1396; preshared key; the server's awg0 stops for 8 s; Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
connected again after 15.9 s
VERIFIED — TESTED SUCCESSFULLY
traffic passed again 18.8 s after the server stopped; transfer passed
awg-life-dead-path-reconnectsthe phone's awg0 file: AmneziaWG 2.0: S1-S4, H1-H4 ranges; Jc, Jmin, Jmax and I1 on the phone; MTU 1396; preshared key; every packet of the session dropped for 45 s; Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
connected again after 47.2 s
VERIFIED — TESTED SUCCESSFULLY
noticed the dead path after 31.9 s, connected again 48.0 s after the drop began; transfer passed
awg-life-server-down-no-reconnectthe phone's awg0 file: AmneziaWG 2.0: S1-S4, H1-H4 ranges; Jc, Jmin, Jmax and I1 on the phone; MTU 1396; preshared key; the server's awg0 stops for 150 s; Auto Reconnect offconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
ended after 35.2 s with: The server stopped answering: nothing came back for 30 seconds (auto reconnect is off).
VERIFIED — TESTED SUCCESSFULLY
ended 37.8 s after the server stopped with: The server stopped answering: nothing came back for 30 seconds (auto reconnect is off).
awg-life-retry-exhaustedthe phone's awg0 file: AmneziaWG 2.0: S1-S4, H1-H4 ranges; Jc, Jmin, Jmax and I1 on the phone; MTU 1396; preshared key; the server's awg0 stops for 120 s; Auto Reconnect on; Retry Times 2connect onlyconnectVERIFIED — TESTED SUCCESSFULLY
ended after 60.3 s with: Could not reconnect after 2 attempts. (The server did not answer the AmneziaWG handshake.)
VERIFIED — TESTED SUCCESSFULLY
ended 56.0 s after the server stopped with: Could not reconnect after 2 attempts. (The server did not answer the AmneziaWG handshake.)
awg-life-path-switchthe phone's awg0 file: AmneziaWG 2.0: S1-S4, H1-H4 ranges; Jc, Jmin, Jmax and I1 on the phone; MTU 1396; preshared key; the connection moved to the current networkconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
connected again after 0.2 s
VERIFIED — TESTED SUCCESSFULLY
followed the network to mobile data and back to Wi-Fi (2 changes); on mobile data 5 of 5 pings to the server's tunnel address were answered; transfer passed

Idle sessions

CaseSettingsTrafficExpectediPhoneAndroid
awg-idle-paddingthe phone's awg3 file: AmneziaWG 3.0: as 2.0, with HeaderProtectionKey and ContentPaddingAddition; the five timings and a 20-30 s keepalive on the phone; MTU 1404; preshared key; 3 minutes without traffic; Log Level Expert; Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
held for 180 s
in the log: the session line
not in the log: a server counted as gone, a new handshake, an end, the file's private key, the file's preshared key, the file's header protection key
VERIFIED — TESTED SUCCESSFULLY
held for 180 s
in the log: the session line
not in the log: a server counted as gone, a new handshake, an end, the file's private key, the file's preshared key, the file's header protection key
awg-idle-trailersthe phone's awg6 file: AmneziaWG 3.1: as 3.0, with RandomTrailers and DisableCookies, single H1-H4; preshared key; 3 minutes without traffic; Log Level Expert; Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
held for 180 s
in the log: the session line
not in the log: a server counted as gone, a new handshake, an end, the file's private key, the file's preshared key, the file's header protection key
VERIFIED — TESTED SUCCESSFULLY
held for 180 s
in the log: the session line
not in the log: a server counted as gone, a new handshake, an end, the file's private key, the file's preshared key, the file's header protection key

The server as the guide sets it up

CaseSettingsTrafficExpectediPhoneAndroid
awg-guide-udpthe guide's phone1.confdownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
136.77 Mbit/s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer phone1 26 s before it was asked
VERIFIED — TESTED SUCCESSFULLY
transfer 5.1 s
the transfers came through the tunnel (the stress server saw only the phone's tunnel address)
the server had a handshake with the peer phone1 19 s before it was asked
awg-guide-removedthe guide's phone2.conf, phone2 removed as part 5 saysconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 11.0 s
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51820 may be closed.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer the AmneziaWG handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, its obfuscation settings (S1-S4, H1-H4, HeaderProtectionKey, RandomTrailers) may differ from this profile's, or UDP port 51820 may be closed.