Test Results

Every OpenVPN case we ran on 8 November 2026, with its result on an iPhone and on an Android phone: 76 of 76 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 48eaf2f7 on the iPhone, as a Debug build, and of cd3916be, which follows it, on Android, as a debug APK; the iPhone's rows of the ovpn-release-… cases come from a Release build of 48eaf2f7's code, the kind TestFlight ships. The server was OpenVPN 2.6.19 and stunnel 5.72 on Ubuntu 24.04, set up as OpenVPN server describes, with these additions for the tests: a management interface on each OpenVPN server, which the cases asked for the connected clients, a stunnel listener on port 9443 with a certificate of its own CA that also has the name cdn.example.com, one on port 9444 that allows only TLS 1.2, and three more OpenVPN servers that each differ from the UDP one in the setting their rows name.

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 downloads took most of the line.

Not tested in this round

Transfers and UDP

CaseSettingsTrafficExpectediPhoneAndroid
ovpn-udp-downloadUDP profile, certificate logindownload, 60 sconnectVERIFIED — TESTED SUCCESSFULLY
132.85 Mbit/s
the server listed the client ovpn-cert1 directly, tunnel address 10.8.0.2, cipher AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 6.0 s
the server listed the client ovpn-cert1 directly, tunnel address 10.8.0.2, cipher AES-256-GCM
ovpn-udp-full-duplexUDP profile, certificate logindownload and upload at once, 90 sconnectVERIFIED — TESTED SUCCESSFULLY
down 100.13 / up 44.34 Mbit/s
the server's log: data channel AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 10.6 s
the server listed the client ovpn-cert1 directly, tunnel address 10.8.0.2, cipher AES-256-GCM
ovpn-udp-uploadUDP profile, certificate loginupload, 60 sconnectVERIFIED — TESTED SUCCESSFULLY
up 125.58 Mbit/s
the server's log: data channel AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 8.2 s
the server listed the client ovpn-cert1 directly, tunnel address 10.8.0.2, cipher AES-256-GCM
ovpn-udp-many-connectionsUDP profile, certificate login16 downloads at once, 45 sconnectVERIFIED — TESTED SUCCESSFULLY
132.06 Mbit/s
the server listed the client ovpn-cert1 directly, tunnel address 10.8.0.2, cipher AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 29.4 s
the server listed the client ovpn-cert1 directly, tunnel address 10.8.0.2, cipher AES-256-GCM
ovpn-tcp-downloadTCP profile, certificate logindownload, 60 sconnectVERIFIED — TESTED SUCCESSFULLY
128.8 Mbit/s
the server listed the client ovpn-cert1 directly, tunnel address 10.8.1.2, cipher AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 7.1 s
the server listed the client ovpn-cert1 directly, tunnel address 10.8.1.2, cipher AES-256-GCM
ovpn-tcp-full-duplexTCP profile, certificate logindownload and upload at once, 60 sconnectVERIFIED — TESTED SUCCESSFULLY
down 111.38 / up 18.56 Mbit/s
the server's log: data channel AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 12.5 s
the server listed the client ovpn-cert1 directly, tunnel address 10.8.1.2, cipher AES-256-GCM
ovpn-stunnel-downloadstunnel profile (TCP to port 443), certificate login; stunnel ondownload, 60 sconnectVERIFIED — TESTED SUCCESSFULLY
159.83 Mbit/s
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 9.3 s
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
ovpn-stunnel-full-duplexstunnel profile (TCP to port 443), certificate login; stunnel ondownload and upload at once, 60 sconnectVERIFIED — TESTED SUCCESSFULLY
down 8.16 / up 167.36 Mbit/s
the server's log: data channel AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 17.2 s
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
ovpn-stunnel-uploadstunnel profile (TCP to port 443), certificate login; stunnel onupload, 45 sconnectVERIFIED — TESTED SUCCESSFULLY
up 185.27 Mbit/s
the server's log: data channel AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 10.6 s
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
ovpn-udp-probeUDP profile, certificate logindownload, 15 s, and a DNS query over UDPconnectVERIFIED — TESTED SUCCESSFULLY
124.89 Mbit/s
the server listed the client ovpn-cert1 directly, tunnel address 10.8.0.2, cipher AES-256-GCM
the UDP DNS query was answered, and saw the server's address
VERIFIED — TESTED SUCCESSFULLY
transfer 6.0 s
the server listed the client ovpn-cert1 directly, tunnel address 10.8.0.2, cipher AES-256-GCM
the UDP DNS query was answered, and saw the server's address

Username and password

CaseSettingsTrafficExpectediPhoneAndroid
ovpn-pass-udp-downloadUDP profile, password logindownload, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
129.54 Mbit/s
the server listed the client ovpnuser1 directly, tunnel address 10.8.2.3, cipher AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 6.0 s
the server listed the client ovpnuser1 directly, tunnel address 10.8.2.3, cipher AES-256-GCM
ovpn-pass-tcp-downloadTCP profile, password logindownload, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
121.1 Mbit/s
the server listed the client ovpnuser1 directly, tunnel address 10.8.3.2, cipher AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
the server listed the client ovpnuser1 directly, tunnel address 10.8.3.2, cipher AES-256-GCM
ovpn-pass-stunnel-downloadstunnel profile (TCP to port 8443), password login; stunnel on; stunnel Port 8443download, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
149.32 Mbit/s
the server listed the client ovpnuser1 through stunnel (127.0.0.1), tunnel address 10.8.3.2, cipher AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 9.4 s
the server listed the client ovpnuser1 through stunnel (127.0.0.1), tunnel address 10.8.3.2, cipher AES-256-GCM
ovpn-pass-special-charactersUDP profile, password login; a user whose password has spaces, punctuation and letters outside ASCIIconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpnuser2 directly, tunnel address 10.8.2.2, cipher AES-256-GCM
held for 6 s while the server listed the client
VERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpnuser2 directly, tunnel address 10.8.2.2, cipher AES-256-GCM
held for 6 s while the server listed the client
ovpn-pass-wrongUDP profile, password login; wrong passwordconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
the server's log: the username/password check failed
ended after 0.5 s
The server refused the login. Check the username and password.
VERIFIED — TESTED SUCCESSFULLY
the server's log: the username/password check failed
The server refused the login. Check the username and password.

Server and Port

CaseSettingsTrafficExpectediPhoneAndroid
ovpn-port-field-overrides-profileUDP profile whose remote line names port 1199 (nothing listens); Port 1194connect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 directly, tunnel address 10.8.0.2, cipher AES-256-GCM
held for 6 s while the server listed the client
VERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 directly, tunnel address 10.8.0.2, cipher AES-256-GCM
held for 6 s while the server listed the client
ovpn-server-field-overrides-profileUDP profile whose remote line names a host that does not exist; Server is the server's addressconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 directly, tunnel address 10.8.0.2, cipher AES-256-GCM
held for 6 s while the server listed the client
VERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 directly, tunnel address 10.8.0.2, cipher AES-256-GCM
held for 6 s while the server listed the client
ovpn-two-remotes-failoverUDP profile with two remote lines: port 1199 (nothing listens), then port 1194; Port 1199connect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 directly, tunnel address 10.8.0.2, cipher AES-256-GCM
held for 6 s while the server listed the client
VERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 directly, tunnel address 10.8.0.2, cipher AES-256-GCM
held for 6 s while the server listed the client

stunnel

CaseSettingsTrafficExpectediPhoneAndroid
ovpn-stunnel-udp-profileUDP profile, certificate login; stunnel onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
held for 6 s while the server listed the client
VERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
held for 6 s while the server listed the client
ovpn-stunnel-host-fieldTCP profile, certificate login; Server is the server's address; stunnel on; stunnel Host: the server's name (Server: its address)connect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
held for 6 s while the server listed the client
VERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
held for 6 s while the server listed the client
ovpn-stunnel-private-castunnel profile (TCP to port 443), certificate login; stunnel on; stunnel Port 9443; CA Certificate: the stunnel server's own CA; stunnel on port 9443 with a certificate of its own CAconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
held for 6 s while the server listed the client
VERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
held for 6 s while the server listed the client
ovpn-stunnel-private-no-castunnel profile (TCP to port 443), certificate login; stunnel on; stunnel Port 9443; stunnel on port 9443 with a certificate of its own CAconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.4 s
The stunnel server's certificate is not trusted for SERVER_HOST (another name, expired, or not from a public certificate authority; import its CA Certificate if the server has its own CA).
VERIFIED — TESTED SUCCESSFULLY
The stunnel server's certificate is not trusted for SERVER_HOST (another name, expired, or not from a public certificate authority; import its CA Certificate if the server has its own CA).
ovpn-stunnel-private-wrong-castunnel profile (TCP to port 443), certificate login; stunnel on; stunnel Port 9443; CA Certificate: a CA that signed nothing on the server; stunnel on port 9443 with a certificate of its own CAconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.4 s
The stunnel server's certificate is not signed by the imported CA Certificate, or not issued for SERVER_HOST.
VERIFIED — TESTED SUCCESSFULLY
The stunnel server's certificate is not signed by the imported CA Certificate, or not issued for SERVER_HOST.
ovpn-stunnel-custom-snistunnel profile (TCP to port 443), certificate login; stunnel on; stunnel Port 9443; stunnel SNI cdn.example.com; CA Certificate: the stunnel server's own CA; stunnel on port 9443 whose certificate has a second nameconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
held for 6 s while the server listed the client
VERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
held for 6 s while the server listed the client
ovpn-stunnel-sni-mismatchstunnel profile (TCP to port 443), certificate login; stunnel on; stunnel SNI cdn.example.comconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.7 s
The stunnel server's certificate is not trusted for cdn.example.com (another name, expired, or not from a public certificate authority; import its CA Certificate if the server has its own CA).
VERIFIED — TESTED SUCCESSFULLY
The stunnel server's certificate is not trusted for cdn.example.com (another name, expired, or not from a public certificate authority; import its CA Certificate if the server has its own CA).
ovpn-stunnel-tls12-onlystunnel profile (TCP to port 443), certificate login; stunnel on; stunnel Port 9444; server: stunnel on port 9444 with sslVersionMax = TLSv1.2connect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
held for 6 s while the server listed the client
VERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
held for 6 s while the server listed the client
ovpn-stunnel-closed-portstunnel profile (TCP to port 443), certificate login; stunnel on; stunnel Port 4443; nothing listens on stunnel port 4443connect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.4 s
The stunnel server SERVER_HOST:4443 refused the connection: nothing listens on that port.
VERIFIED — TESTED SUCCESSFULLY
The stunnel server SERVER_HOST:4443 refused the connection: nothing listens on that port.

TLS Fragmentation

CaseSettingsTrafficExpectediPhoneAndroid
ovpn-frag-offstunnel profile (TCP to port 443), certificate login; stunnel on; TLS Fragmentation Offconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
the server received the ClientHello as TCP segments of 1525, 80, 78, 371, 90, 94 … bytes
held for 6 s while the server listed the client
VERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
the server received the ClientHello as TCP segments of 517, 64, 78, 1666, 90, 94 … bytes
held for 6 s while the server listed the client
ovpn-frag-autostunnel profile (TCP to port 443), certificate login; stunnel on; TLS Fragmentation Autoconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
the server received the ClientHello as TCP segments of 43, 256, 256, 256, 256, 256 … bytes
held for 6 s while the server listed the client
VERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
the server received the ClientHello as TCP segments of 43, 256, 218, 43, 21, 78 … bytes
held for 6 s while the server listed the client
ovpn-frag-manualstunnel profile (TCP to port 443), certificate login; stunnel on; TLS Fragmentation Manual 10/40connect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
the server received the ClientHello as TCP segments of 10, 40, 40, 40, 40, 40 … bytes
held for 6 s while the server listed the client
VERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
the server received the ClientHello as TCP segments of 10, 40, 40, 40, 40, 40 … bytes
held for 6 s while the server listed the client
ovpn-frag-auto-private-ca-snistunnel profile (TCP to port 443), certificate login; stunnel on; stunnel Port 9443; stunnel SNI cdn.example.com; CA Certificate: the stunnel server's own CA; TLS Fragmentation Auto; stunnel on port 9443 whose certificate has a second nameconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
the server received the ClientHello as TCP segments of 43, 256, 256, 256, 256, 256 … bytes
held for 6 s while the server listed the client
VERIFIED — TESTED SUCCESSFULLY
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
the server received the ClientHello as TCP segments of 43, 214, 43, 21, 78, 1666 … bytes
held for 6 s while the server listed the client
ovpn-frag-manual-downloadstunnel profile (TCP to port 443), certificate login; stunnel on; TLS Fragmentation Manual 32/256download, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
124.62 Mbit/s
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 8.3 s
the server listed the client ovpn-cert1 through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM

Refusals and damaged profiles

CaseSettingsTrafficExpectediPhoneAndroid
ovpn-revoked-certificateUDP profile with a revoked certificateconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
the server's log: VERIFY ERROR: certificate revoked
ended after 42.4 s
The server stopped answering after the TLS handshake. It may have refused the client certificate (revoked, from another CA or expired); the server's log names the reason.
VERIFIED — TESTED SUCCESSFULLY
the server's log: VERIFY ERROR: certificate revoked
The server stopped answering after the TLS handshake. It may have refused the client certificate (revoked, from another CA or expired); the server's log names the reason.
ovpn-rogue-client-certificateUDP profile with a client certificate of another CAconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
the server's log: VERIFY ERROR: unable to get local issuer certificate
ended after 42.4 s
The server stopped answering after the TLS handshake. It may have refused the client certificate (revoked, from another CA or expired); the server's log names the reason.
VERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
The server stopped answering after the TLS handshake. It may have refused the client certificate (revoked, from another CA or expired); the server's log names the reason.
ovpn-wrong-server-caUDP profile whose CA did not sign the server's certificateconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.4 s
The server's certificate could not be verified with the profile's CA (OpenSSLContext::SSL::read_cleartext: BIO_read failed, cap=2640 status=-1: error:0A000086:SSL routines::certificate verify failed).
VERIFIED — TESTED SUCCESSFULLY
The server's certificate could not be verified with the profile's CA (OpenSSLContext::SSL::read_cleartext: BIO_read failed, cap=2640 status=-1: error:0A000086:SSL routines::certificate verify failed).
ovpn-wrong-tls-crypt-keyUDP profile with another tls-crypt keyconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 10.4 s
The server did not answer.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer.
ovpn-udp-closed-portUDP profile whose remote line names port 1199 (nothing listens); Port 1199connect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 10.3 s
The server did not answer.
VERIFIED — TESTED SUCCESSFULLY
The server did not answer.
ovpn-tcp-refusedTCP profile whose remote line names port 1199 (nothing listens); Port 1199connect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 2.4 s
The server refused the connection: no OpenVPN server answers on that port.
VERIFIED — TESTED SUCCESSFULLY
The server refused the connection: no OpenVPN server answers on that port.
ovpn-unknown-hostUDP profile whose remote line names a host that does not exist; Server is a name that does not existconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 2.4 s
The server name no-such-host.srp.invalid could not be resolved.
VERIFIED — TESTED SUCCESSFULLY
The server name no-such-host.srp.invalid could not be resolved.
ovpn-garbage-profilea file with remote and dev lines but no profileconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.3 s
Invalid OpenVPN profile: ERR_INVALID_OPTION_VAL: option_error: option 'remote' must have at least 1 arguments
VERIFIED — TESTED SUCCESSFULLY
Invalid OpenVPN profile: ERR_INVALID_OPTION_VAL: option_error: option 'remote' must have at least 1 arguments
ovpn-encrypted-keyUDP profile whose private key has a passphraseconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.3 s
The profile's private key is protected with a passphrase, which this app cannot enter. Export the key without a passphrase (for example: openssl pkey -in client.key -out client-plain.key) and import the profile again.
VERIFIED — TESTED SUCCESSFULLY
The profile's private key is protected with a passphrase, which this app cannot enter. Export the key without a passphrase (for example: openssl pkey -in client.key -out client-plain.key) and import the profile again.
ovpn-static-key-profilea static-key (secret) profileconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
ended after 0.3 s
This profile uses an OpenVPN static key (secret), which OpenVPN 3 does not support. Ask for a profile with certificates (TLS mode).
VERIFIED — TESTED SUCCESSFULLY
This profile uses an OpenVPN static key (secret), which OpenVPN 3 does not support. Ask for a profile with certificates (TLS mode).

Older servers

CaseSettingsTrafficExpectediPhoneAndroid
ovpn-net30-topologyUDP profile, certificate login; server: no topology line (net30)download, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
123.68 Mbit/s
the server's log: data channel AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 6.1 s
the server's log: data channel AES-256-GCM
ovpn-cbc-tls-authUDP profile with tls-auth, auth SHA256, cipher AES-256-CBC; server: data-ciphers AES-256-CBC, auth SHA256, tls-auth instead of tls-cryptdownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
107.98 Mbit/s
the server's log: data channel AES-256-CBC with SHA256
VERIFIED — TESTED SUCCESSFULLY
transfer 6.0 s
the server's log: data channel AES-256-GCM
ovpn-pushed-compressionUDP profile, certificate login; server: allow-compression yes, compress lz4-v2 pushedconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
ended after 2.4 s
The server pushes compression (lz4-v2), which this app does not take: compression inside a VPN can leak data (VORACLE). Turn it off on the server (remove compress/comp-lzo from its configuration).
VERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
The server pushes compression (lz4-v2), which this app does not take: compression inside a VPN can leak data (VORACLE). Turn it off on the server (remove compress/comp-lzo from its configuration).

Log levels

CaseSettingsTrafficExpectediPhoneAndroid
ovpn-log-normalUDP profile, password login; Log Level Normaldownload, 10 sconnectVERIFIED — TESTED SUCCESSFULLY
112.69 Mbit/s
the server's log: data channel AES-256-GCM
in the log: the session line
not in the log: the password, the private key, the tls-crypt key, a key passphrase
VERIFIED — TESTED SUCCESSFULLY
transfer 6.0 s
the server's log: data channel AES-256-GCM
in the log: the session line
not in the log: the password, the private key, the tls-crypt key, a key passphrase
ovpn-log-expertUDP profile, password login; Log Level Expertdownload, 10 sconnectVERIFIED — TESTED SUCCESSFULLY
124.56 Mbit/s
the server's log: data channel AES-256-GCM
in the log: the session line, OpenVPN's own lines
not in the log: the password, the private key, the tls-crypt key, a key passphrase
VERIFIED — TESTED SUCCESSFULLY
transfer 5.9 s
the server's log: data channel AES-256-GCM
in the log: the session line, OpenVPN's own lines
not in the log: the password, the private key, the tls-crypt key, a key passphrase
ovpn-log-debugUDP profile, password login; Log Level Debugdownload, 4 sconnectVERIFIED — TESTED SUCCESSFULLY
120.37 Mbit/s
the server's log: data channel AES-256-GCM
in the log: the session line, OpenVPN's own lines, packet lines (Debug build)
not in the log: the password, the private key, the tls-crypt key, a key passphrase
VERIFIED — TESTED SUCCESSFULLY
transfer 6.0 s
the server's log: data channel AES-256-GCM
in the log: the session line, OpenVPN's own lines
not in the log: the password, the private key, the tls-crypt key, a key passphrase
ovpn-release-log-normalUDP profile, password login; Log Level Normaldownload, 10 sconnectVERIFIED — TESTED SUCCESSFULLY
80.77 Mbit/s
Release build
the server's log: data channel AES-256-GCM
in the log: the session line
not in the log: the password, the private key, the tls-crypt key, a key passphrase
NOT VERIFIED
ovpn-release-log-expertUDP profile, password login; Log Level Expertdownload, 10 sconnectVERIFIED — TESTED SUCCESSFULLY
133.61 Mbit/s
Release build
the server's log: data channel AES-256-GCM
in the log: the session line, OpenVPN's own lines
not in the log: the password, the private key, the tls-crypt key, a key passphrase
NOT VERIFIED
ovpn-release-log-debugUDP profile, password login; Log Level Debugdownload, 4 sconnectVERIFIED — TESTED SUCCESSFULLY
125.44 Mbit/s
Release build
the server's log: data channel AES-256-GCM
in the log: the session line, OpenVPN's own lines
not in the log: the password, the private key, the tls-crypt key, a key passphrase
NOT VERIFIED
ovpn-release-stunnel-private-no-castunnel profile (TCP to port 443), certificate login; stunnel on; stunnel Port 9443; Log Level Expertconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
Release build
in the log: the app's OpenVPN lines
not in the log: the password, the private key, the tls-crypt key
ended after 0.4 s
The stunnel server's certificate is not trusted for SERVER_HOST (another name, expired, or not from a public certificate authority; import its CA Certificate if the server has its own CA).
NOT VERIFIED
ovpn-release-udp-downloada profile of the serverdownload, 60 sconnectVERIFIED — TESTED SUCCESSFULLY
138.97 Mbit/s
Release build
the server listed the client ovpn-cert2 directly, tunnel address 10.8.0.3, cipher AES-256-GCM
the server's log: VERIFY ERROR: certificate revoked
in the log: the app's OpenVPN lines
not in the log: the password, the private key, the tls-crypt key
NOT VERIFIED

Sleep, lost connections, network switch and Retry Times

CaseSettingsTrafficExpectediPhoneAndroid
ovpn-life-sleep-modes-udpUDP profile, certificate login; On Sleep Stay, Pause and Off, and Off with Auto Reconnect offconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
On Sleep Stay, Auto Reconnect on: connected again after 3.2 s
On Sleep Pause, Auto Reconnect off: connected again after 3.3 s
On Sleep Off, Auto Reconnect on: connected again after 3.4 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.
ovpn-life-sleep-modes-stunnelstunnel profile (TCP to port 443), certificate login; stunnel on; On Sleep Stay, Pause and Off, and Off with Auto Reconnect offconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
On Sleep Stay, Auto Reconnect on: connected again after 3.3 s
On Sleep Pause, Auto Reconnect off: connected again after 3.4 s
On Sleep Off, Auto Reconnect on: connected again after 3.5 s
On Sleep Off, Auto Reconnect off: ended after 3.4 s with: The connection was closed while the device slept.
NOT VERIFIED
ovpn-life-kick-udpUDP profile, certificate login; the server restarts the session (client-kill); Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
connected again after 5.8 s
VERIFIED — TESTED SUCCESSFULLY
connected again 5.2 s after the restart; transfer passed
ovpn-life-kick-udp-no-reconnectUDP profile, certificate login; the server restarts the session (client-kill); Auto Reconnect offconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
ended after 5.0 s with: The server restarted the session (auto reconnect is off).
VERIFIED — TESTED SUCCESSFULLY
ended with: The server restarted the session (auto reconnect is off).
ovpn-life-kick-tcpTCP profile, certificate login; the server restarts the session (client-kill); Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
connected again after 6.1 s
NOT VERIFIED
ovpn-life-stunnel-restartstunnel profile (TCP to port 443), certificate login; stunnel on; stunnel restarts; Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
connected again after 5.8 s
VERIFIED — TESTED SUCCESSFULLY
connected again 6.3 s after stunnel restarted; transfer passed
ovpn-life-stunnel-restart-no-reconnectstunnel profile (TCP to port 443), certificate login; stunnel on; stunnel restarts; Auto Reconnect offconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
ended after 5.0 s with: The stunnel server closed the connection (auto reconnect is off).
VERIFIED — TESTED SUCCESSFULLY
ended with: The stunnel server closed the connection (auto reconnect is off).
ovpn-life-haltUDP profile, certificate login; the server halts the session (client-kill HALT); Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
ended after 5.0 s with: The server ended the session.
VERIFIED — TESTED SUCCESSFULLY
ended with: The server ended the session.
ovpn-life-retry-exhausted-udpUDP profile, certificate login; the server stops for 120 s; Auto Reconnect on; Retry Times 2connect onlyconnectVERIFIED — TESTED SUCCESSFULLY
ended after 25.9 s with: Could not reconnect after 2 attempts. (The server did not answer)
VERIFIED — TESTED SUCCESSFULLY
ended with: Could not reconnect after 2 attempts. (The server did not answer)
ovpn-life-retry-exhausted-stunnelstunnel profile (TCP to port 443), certificate login; stunnel on; the TCP server behind stunnel stops for 120 s; Auto Reconnect on; Retry Times 2connect onlyconnectVERIFIED — TESTED SUCCESSFULLY
ended after 11.0 s with: Could not reconnect after 2 attempts. (The stunnel connection broke)
NOT VERIFIED
ovpn-life-outage-reconnectUDP profile, certificate login; the server stops for 8 s; Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
connected again after 11.8 s
VERIFIED — TESTED SUCCESSFULLY
connected again 9.9 s after the server stopped, after 1 attempt; transfer passed
ovpn-life-dead-path-reconnectsUDP profile, certificate login; every packet of the session dropped for 45 s; Auto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
connected again after 46.1 s
VERIFIED — TESTED SUCCESSFULLY
noticed the dead path after 60.9 s, connected again 79.3 s after the drop began; transfer passed
ovpn-life-dead-path-no-reconnectUDP profile, certificate login; every packet of the session dropped for 150 s; Auto Reconnect offconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
ended after 62.6 s with: The server stopped answering (keepalive timeout) (auto reconnect is off).
NOT VERIFIED
ovpn-life-path-switch-udpUDP profile, certificate login; Auto Reconnect on; the connection moved to a new network pathconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
connected again after 1.3 s
VERIFIED — TESTED SUCCESSFULLY
moved back to Wi-Fi: 2 connections in all; transfer passed
ovpn-life-path-switch-stunnelstunnel profile (TCP to port 443), certificate login; stunnel on; Auto Reconnect on; the connection moved to a new network pathconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
connected again after 0.4 s
NOT VERIFIED
ovpn-life-path-switch-no-reconnectUDP profile, certificate login; Auto Reconnect off; the connection moved to a new network pathconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server's log: data channel AES-256-GCM
connected again after 0.4 s
NOT VERIFIED

The server as the guide sets it up

CaseSettingsTrafficExpectediPhoneAndroid
ovpn-guide-udpthe guide's phone1-udp.ovpndownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
130.77 Mbit/s
the server's log: phone1 connected directly, tunnel address 10.8.0.2, cipher AES-256-GCM
the server's log: data channel AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 6.2 s
the server's log: phone1 connected directly, tunnel address 10.8.0.2, cipher AES-256-GCM
the server's log: data channel AES-256-GCM
ovpn-guide-status-filethe guide's phone1-udp.ovpnconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
70 s after connecting, the status file listed phone1
the server's log: data channel AES-256-GCM
held for 80 s while the server listed the client
VERIFIED — TESTED SUCCESSFULLY
70 s after connecting, the status file listed phone1
the server's log: data channel AES-256-GCM
held for 80 s while the server listed the client
ovpn-guide-stunnelthe guide's phone1-stunnel.ovpn; stunnel ondownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
72.13 Mbit/s
the server's log: phone1 connected through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
the server's log: data channel AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 9.4 s
the server's log: phone1 connected through stunnel (127.0.0.1), tunnel address 10.8.1.2, cipher AES-256-GCM
the server's log: data channel AES-256-GCM
ovpn-guide-pass-udpthe guide's vpnuser-udp-pass.ovpndownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
127.33 Mbit/s
the server's log: vpnuser connected directly, tunnel address 10.8.2.2, cipher AES-256-GCM
the server's log: data channel AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 6.0 s
the server's log: vpnuser connected directly, tunnel address 10.8.2.2, cipher AES-256-GCM
the server's log: data channel AES-256-GCM
ovpn-guide-pass-tcpthe guide's vpnuser-tcp-pass.ovpndownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
92.0 Mbit/s
the server's log: vpnuser connected directly, tunnel address 10.8.3.2, cipher AES-256-GCM
the server's log: data channel AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
the server's log: vpnuser connected directly, tunnel address 10.8.3.2, cipher AES-256-GCM
the server's log: data channel AES-256-GCM
ovpn-guide-pass-stunnelthe guide's vpnuser-stunnel-pass.ovpn; stunnel on; stunnel Port 8443download, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
70.93 Mbit/s
the server's log: vpnuser connected through stunnel (127.0.0.1), tunnel address 10.8.3.2, cipher AES-256-GCM
the server's log: data channel AES-256-GCM
VERIFIED — TESTED SUCCESSFULLY
transfer 9.5 s
the server's log: vpnuser connected through stunnel (127.0.0.1), tunnel address 10.8.3.2, cipher AES-256-GCM
the server's log: data channel AES-256-GCM
ovpn-guide-revokedthe guide's phone2-udp.ovpn, phone2 revoked as part 9 saysconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
the server's log: VERIFY ERROR: certificate revoked
ended after 42.4 s
The server stopped answering after the TLS handshake. It may have refused the client certificate (revoked, from another CA or expired); the server's log names the reason.
VERIFIED — TESTED SUCCESSFULLY
the server's log: VERIFY ERROR: certificate revoked
The server stopped answering after the TLS handshake. It may have refused the client certificate (revoked, from another CA or expired); the server's log names the reason.