Test Results

Every SoftEther VPN case we ran on 7 November 2026, with its result on an iPhone and on an Android phone: 60 of 60 cases passed on the iPhone and 60 of 60 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 app built from commit 013f04fb, as a Debug build on the iPhone and a debug APK on Android; the iPhone's rows of the log cases and sev-wrong-password come from a Release build of commit 7708f7a3, the kind TestFlight ships. The server was SoftEther VPN Server 4.44 Build 9807 on Ubuntu 24.04, set up as SoftEther VPN Server describes, with the users of each login method in the hubs DEFAULT and TEST-HUB.

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

Logins and hubs

CaseSettingsTrafficExpectediPhoneAndroid
sev-pass-downloaddefaultsdownload, 60 sconnectVERIFIED — TESTED SUCCESSFULLY
126.06 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-pass-full-duplexdefaultsdownload and upload at once, 90 sconnectVERIFIED — TESTED SUCCESSFULLY
down 5.25 / up 56.39 Mbit/s
2 TCP connections
VERIFIED — TESTED SUCCESSFULLY
transfer 15.0 s
2 TCP connections
sev-pass-uploaddefaultsupload, 60 sconnectVERIFIED — TESTED SUCCESSFULLY
down 0.0 / up 61.38 Mbit/s
2 TCP connections
VERIFIED — TESTED SUCCESSFULLY
transfer 8.3 s
2 TCP connections
sev-radius-downloadMethod RADIUS / NT Domaindownload, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
130.31 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-anon-downloadMethod Anonymousdownload, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
123.32 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 8.4 s
2 TCP connections
sev-cert-signed-downloadMethod Certificate (signed certificate user)download, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
117.91 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-cert-individual-downloadMethod Certificate (individual certificate user)download, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
122.61 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.3 s
2 TCP connections
sev-hub-test-hubVirtual Hub TEST-HUBdownload, 30 sconnectVERIFIED — TESTED SUCCESSFULLY
121.87 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.3 s
2 TCP connections
sev-wrong-passwordwrong passwordconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
in the log: the connect line, the reason the app closed the connection
not in the log: TLS secrets
Authentication failed. Check the username, password and authentication method.
VERIFIED — TESTED SUCCESSFULLY
in the log: the connect line, the reason the app closed the connection
not in the log: TLS secrets
Authentication failed. Check the username, password and authentication method.
sev-wrong-hubVirtual Hub NO-SUCH-HUBconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
Virtual Hub not found. Check the Virtual Hub field.
VERIFIED — TESTED SUCCESSFULLY
Virtual Hub not found. Check the Virtual Hub field.
sev-radius-user-standard-methodRADIUS userconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
Authentication failed. Check the username, password and authentication method.
VERIFIED — TESTED SUCCESSFULLY
Authentication failed. Check the username, password and authentication method.
sev-radius-wrong-passwordMethod RADIUS / NT Domain; wrong passwordconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
Authentication failed. Check the username, password and authentication method.
VERIFIED — TESTED SUCCESSFULLY
Authentication failed. Check the username, password and authentication method.
sev-anon-on-password-userMethod Anonymous; password userconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
Authentication failed. Check the username, password and authentication method.
VERIFIED — TESTED SUCCESSFULLY
Authentication failed. Check the username, password and authentication method.
sev-cert-rogue-caMethod Certificate (a certificate from another authority)connect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
Authentication failed. Check the username, password and authentication method.
VERIFIED — TESTED SUCCESSFULLY
Authentication failed. Check the username, password and authentication method.
sev-cert-missingMethod Certificate without a certificateconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
Certificate authentication requires a client certificate in the profile.
VERIFIED — TESTED SUCCESSFULLY
The client certificate could not be read. Re-import it in the profile.

Certificate check, Hostname and ports

CaseSettingsTrafficExpectediPhoneAndroid
sev-verify-ip-declinedServer is the server's IP addressconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
the certificate warning was declined
VERIFIED — TESTED SUCCESSFULLY
the certificate warning was declined
sev-verify-ip-acceptedServer is the server's IP addressdownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
125.21 Mbit/s
the certificate warning was accepted
VERIFIED — TESTED SUCCESSFULLY
transfer 7.3 s
2 TCP connections
sev-hostname-override-ipServer is the server's IP address; Hostname <SERVER_HOST>download, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
117.89 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.3 s
2 TCP connections
sev-hostname-override-wrongHostname a name the certificate is not forconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
The server certificate name does not match the server. Check the Hostname field.
VERIFIED — TESTED SUCCESSFULLY
the certificate warning was declined
sev-allow-untrusted-ipServer is the server's IP address; TLS Server Verification offdownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
118.93 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-port-992Port 992download, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
115.7 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-port-5555Port 5555download, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
113.19 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.1 s
2 TCP connections
sev-port-other-servicePort 22 (the server's SSH answers it)connect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
The TLS handshake with the server failed. Check the Server and Port fields.
VERIFIED — TESTED SUCCESSFULLY
The TLS handshake with the server failed. Check the Server and Port fields.

Connections and UDP acceleration

CaseSettingsTrafficExpectediPhoneAndroid
sev-conns-2Connections 2download and upload at once, 40 sconnectVERIFIED — TESTED SUCCESSFULLY
down 10.92 / up 54.6 Mbit/s
2 TCP connections
VERIFIED — TESTED SUCCESSFULLY
transfer 14.0 s
2 TCP connections
sev-conns-8Connections 8download and upload at once, 40 sconnectVERIFIED — TESTED SUCCESSFULLY
down 17.45 / up 49.86 Mbit/s
8 TCP connections
VERIFIED — TESTED SUCCESSFULLY
transfer 15.0 s
8 TCP connections
sev-conns-32Connections 32download and upload at once, 40 sconnectVERIFIED — TESTED SUCCESSFULLY
down 42.95 / up 40.27 Mbit/s
12 TCP connections
VERIFIED — TESTED SUCCESSFULLY
transfer 16.2 s
13 TCP connections
sev-udp-accelUDP acceleration ondownload and upload at once, 40 sconnectVERIFIED — TESTED SUCCESSFULLY
down 9.81 / up 49.04 Mbit/s
2 TCP connections
UDP acceleration active
VERIFIED — TESTED SUCCESSFULLY
transfer 13.9 s
2 TCP connections
UDP acceleration active
sev-udp-accel-conns-4Connections 4; UDP acceleration ondownload and upload at once, 40 sconnectVERIFIED — TESTED SUCCESSFULLY
down 10.29 / up 48.9 Mbit/s
4 TCP connections
UDP acceleration active
VERIFIED — TESTED SUCCESSFULLY
transfer 16.1 s
4 TCP connections
UDP acceleration active

NAT traversal

CaseSettingsTrafficExpectediPhoneAndroid
sev-natt-closed-tcp-portPort 5557 (nothing listens on it); NAT-T ondownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
84.51 Mbit/s
over NAT-T
VERIFIED — TESTED SUCCESSFULLY
transfer 8.3 s
2 TCP connections
over NAT-T
sev-natt-off-closed-tcp-portPort 5557 (nothing listens on it); NAT-T offconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
Cannot reach the server (DNS lookup or TCP connection failed). Check the Server field for typos and the network connection.
VERIFIED — TESTED SUCCESSFULLY
Cannot reach the server (DNS lookup or TCP connection failed). Check the Server field for typos and the network connection.
sev-natt-hint-serverNAT-T on, hint the server's own addressdownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
93.28 Mbit/s
over NAT-T
VERIFIED — TESTED SUCCESSFULLY
transfer 8.3 s
2 TCP connections
over NAT-T
sev-natt-hint-wrongNAT-T on, hint an address no server hasconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
Cannot reach the server (DNS lookup or TCP connection failed). Check the Server field for typos and the network connection.
VERIFIED — TESTED SUCCESSFULLY
Cannot reach the server (DNS lookup or TCP connection failed). Check the Server field for typos and the network connection.

Proxies and PAC files

CaseSettingsTrafficExpectediPhoneAndroid
sev-proxy-httpHTTP proxydownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
114.2 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 8.3 s
2 TCP connections
sev-proxy-http-authHTTP proxy with username and passworddownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
126.62 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-proxy-http-wrong-authHTTP proxy with a wrong passwordconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
Proxy authentication failed.
VERIFIED — TESTED SUCCESSFULLY
Proxy authentication failed.
sev-proxy-socks5SOCKS5 proxydownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
123.08 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-proxy-socks5-authSOCKS5 proxy with username and passworddownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
114.17 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-proxy-socks5-wrong-authSOCKS5 proxy with a wrong passwordconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
Proxy authentication failed.
VERIFIED — TESTED SUCCESSFULLY
Proxy authentication failed.
sev-proxy-unreachableproxy port nothing listens onconnect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
Cannot connect to the proxy server.
VERIFIED — TESTED SUCCESSFULLY
Cannot connect to the proxy server.
sev-pac-httpPAC file: PROXYdownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
108.43 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-pac-http-authPAC file: PROXY with username and passworddownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
123.59 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-pac-socks5PAC file: SOCKS5download, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
121.35 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-pac-socksPAC file: SOCKSdownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
109.21 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-pac-socks5-authPAC file: SOCKS5 with username and passworddownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
104.77 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-pac-directPAC file: DIRECTdownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
110.47 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-pac-fallbackPAC file: an unreachable PROXY, then a working onedownload, 20 sconnectVERIFIED — TESTED SUCCESSFULLY
103.96 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-pac-missingPAC file: a PAC URL that answers 404connect onlyrefusedVERIFIED — TESTED SUCCESSFULLY
Unable to download PAC configuration
VERIFIED — TESTED SUCCESSFULLY
Unable to download PAC configuration

TLS Fragmentation

CaseSettingsTrafficExpectediPhoneAndroid
sev-frag-off-captureTLS Server Verification off; TLS Fragmentation Offdownload, 15 sconnectVERIFIED — TESTED SUCCESSFULLY
116.78 Mbit/s
ClientHello sent as 324 bytes
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
ClientHello sent as 1440 + 111 bytes
sev-frag-auto-captureTLS Server Verification off; TLS Fragmentation Autodownload, 15 sconnectVERIFIED — TESTED SUCCESSFULLY
112.02 Mbit/s
ClientHello sent as 43 + 256 + 25 bytes
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
ClientHello sent as 43 + 256 + 256 + 256 + 256 + 256 + 228 bytes
sev-frag-manual-20-100-captureTLS Server Verification off; TLS Fragmentation Manual 20/100download, 15 sconnectVERIFIED — TESTED SUCCESSFULLY
112.32 Mbit/s
ClientHello sent as 20 + 100 + 100 + 100 + 4 bytes
VERIFIED — TESTED SUCCESSFULLY
transfer 6.1 s
2 TCP connections
ClientHello of 1551 bytes; its first 720 bytes sent as 20 + 100 + 100 + 100 + 100 + 100 + 100 + 100 (the server recorded the first 8 pieces)
sev-frag-auto-verifiedTLS Fragmentation Autodownload, 15 sconnectVERIFIED — TESTED SUCCESSFULLY
111.52 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.2 s
2 TCP connections
sev-frag-auto-proxyHTTP proxy; TLS Fragmentation Autodownload, 15 sconnectVERIFIED — TESTED SUCCESSFULLY
114.65 Mbit/s
VERIFIED — TESTED SUCCESSFULLY
transfer 7.3 s
2 TCP connections

Log levels

CaseSettingsTrafficExpectediPhoneAndroid
sev-log-normalLog Level Normalconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
in the log: the connect line, the session line
not in the log: the adapter's DHCP line, the core's own lines, TLS secrets
VERIFIED — TESTED SUCCESSFULLY
in the log: the connect line, the session line
not in the log: the adapter's DHCP line, the core's own lines, TLS secrets
sev-log-expertLog Level Expertconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
in the log: the connect line, the adapter's DHCP line
not in the log: the core's own lines, TLS secrets
VERIFIED — TESTED SUCCESSFULLY
in the log: the connect line, the adapter's DHCP line
not in the log: the core's own lines, TLS secrets
sev-log-debugLog Level Debugconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
in the log: the connect line, the adapter's DHCP line, the core's own lines
not in the log: TLS secrets
VERIFIED — TESTED SUCCESSFULLY
in the log: the connect line, the adapter's DHCP line, the core's own lines
not in the log: TLS secrets

Sleep, lost connections and Retry Times

CaseSettingsTrafficExpectediPhoneAndroid
sev-life-sleep-modesOn Sleep Stay, Pause and Off, and Off with Auto Reconnect offconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
On Sleep Stay, Auto Reconnect on: connected again after 3.1 s
On Sleep Pause, Auto Reconnect off: connected again after 4.4 s
On Sleep Off, Auto Reconnect on: connected again after 4.3 s
On Sleep Off, Auto Reconnect off: ended after 3.5 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.
sev-life-peer-drop-reconnectAuto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
connected again after 5.1 s
VERIFIED — TESTED SUCCESSFULLY
connected again 2.9 s after the drop; transfer passed
sev-life-peer-drop-no-reconnectAuto Reconnect offconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
ended after 5.0 s with: Connection lost (auto reconnect is off).
VERIFIED — TESTED SUCCESSFULLY
ended with: Connection lost (auto reconnect is off).
sev-life-retry-exhaustedAuto Reconnect on; Retry Times 2connect onlyconnectVERIFIED — TESTED SUCCESSFULLY
the server was stopped: ended after 27.7 s with: Could not reconnect after 2 attempts. (Cannot reach the server (DNS lookup or TCP connection failed). Check the Server field for typos and the network connection.)
VERIFIED — TESTED SUCCESSFULLY
ended after 2 retries with: Could not reconnect after 2 attempts. (Cannot reach the server (DNS lookup or TCP connection failed). Check the Server field for typos and the network connection.)
sev-life-outage-reconnectAuto Reconnect onconnect onlyconnectVERIFIED — TESTED SUCCESSFULLY
connected again after 23.0 s
VERIFIED — TESTED SUCCESSFULLY
connected again 3.9 s after the server came back, after 1 attempts; transfer passed