Troubleshooting

Start with the checks below, then look up the message the app showed.

Where this page comes from

The messages and what triggers them were read from the source code of both apps; both use the same SSTP and PPP code and show the same messages. The server limits were seen in the test runs listed in Test results.

First checks

  1. Open the log. Tap the status text under the power button. When the app gave up on a connection, the line starting with SSTP: closing with reason: names the reason. For more detail, set Log Level to Expert or Debug in the profile and connect again. Expert shows each PPP phase and the authentication methods the profile offered; Debug adds the SSTP client's and PPP's own lines.
  2. Is the server listening? From a computer, openssl s_client -connect <SERVER_HOST>:443 -servername <SERVER_HOST> must show the server's certificate. If it times out, check the server's firewall and that its SSTP service is on.
  3. Does the name match the certificate? The app checks the certificate against Host, or against the Custom SNI when that is on.
  4. Do the methods match? The server must accept one of the methods that are on in the profile; see the table for each server below.

Messages

Before the connection starts

MessageWhat happenedWhat to do
DANGEROUS! with the server's certificatesThe certificate does not chain to a root the phone trusts, or it is not valid for the name the app checks.Use the name the certificate is for, or install a trusted certificate on the server. Continue and Save and Continue skip the check; see the certificate warning.
Invalid TLS fragmentation settings: chunk sizes out of boundsA Manual chunk size is larger than 4096 (First Chunk) or 16384 (Following Chunks).Use smaller sizes, or Auto.
The client certificate could not be read. Re-import it in the profile.The imported certificate is gone or cannot be read.Import the .p12 or .pfx file again.

Reaching the server

MessageWhat happenedWhat to do
Cannot reach the server (DNS/TCP/TLS failed). Check the host, port and certificate settings.The name did not resolve, nothing answered on the port, or the TLS handshake failed.Host, Port, the server's firewall, and the certificate checks above.
Cannot reach the server after N attempts. …The same, after the retries that Retry Times allowed.The same.
The server certificate is not trusted: …The tunnel itself refused the certificate, which the check before connecting had let through or the user had accepted for an earlier connection.As for DANGEROUS! above.
TLS handshake failed: …The server and the app found no TLS version or cipher in common, or the server ended the handshake.Turn off Disable TLS 1.0 & 1.1 only if the server offers nothing newer; all our test servers offer TLS 1.2 or 1.3.
Connection timed out. The server did not respond.No connection was up 30 seconds after the start.The network, and whether the server answers at all.

Proxy

MessageWhat happened
Cannot reach the proxy ADDRESS:PORT (reason). Check the proxy address and port.Nothing answered at the proxy's address and port; the reason is the network's, for example Connection refused.
Proxy authentication required (HTTP 407), Proxy authentication failed (HTTP 407)The HTTP proxy wants a username and password, or refused the ones in the profile.
Proxy authentication required (SOCKS5), Proxy authentication failed (SOCKS5)The same for a SOCKS5 proxy.
HTTP CONNECT failed (status N), SOCKS5 negotiation failed (reply code N)The proxy refused the connection to the SSTP server.
Unsupported proxy protocol (neither SOCKS5 nor HTTP CONNECT answered)The address answers, but not as a proxy.
Unable to download PAC configuration, Invalid PAC configuration (…), PAC evaluation failed, No usable proxy returned by PACThe PAC file could not be fetched, is not a script with FindProxyForURL, failed when it ran, or returned no proxy the app can use.

Logging in

MessageWhat happenedWhat to do
Authentication failed. The server rejected the username or password.The server, or its RADIUS server, refused the login.The username and password, and that the user may use the VPN (on Windows, the user's dial-in permission or the network policy).
Authentication failed. The server rejected the username or password, or the anonymous outer identity of Identity Privacy; …As above, with Identity Privacy on.Windows RRAS with local accounts refuses the outer identity anonymous: turn Identity Privacy off for it.
Authentication failed. The server rejected the client certificate; …EAP-TLS: the server does not trust the client certificate's issuer, or the certificate expired.The CA the RADIUS server trusts for client certificates (FreeRADIUS).
The EAP server's certificate is not trusted: …With PEAP, EAP-TTLS or EAP-TLS, the RADIUS server's own certificate does not chain to a root the phone trusts.Give the RADIUS server a trusted certificate, as ours has; turning on Allow Untrusted Certificate also skips this check.
The server closed the connection during PPP negotiation. Check that it accepts one of the authentication methods enabled in this profile.The server accepts none of the methods that are on in the profile, for example a SoftEther server and a profile with only EAP methods, or a MikroTik router set to MS-CHAPv1 only.Turn on a method the server has; see the table below.
The server closed the connection during authentication. Check the username and password.The server ended the connection while the login was being checked.The username, password and the server's log.
The server closed the connection while assigning the tunnel address. Check the server's address pool.The login passed, but the server ended the connection before it gave the phone an address.The server's address pool (MikroTik's IP pool, Windows' static pool or DHCP, SoftEther's DHCP).

After the connection was up

MessageWhat happened
Connection lost (auto reconnect is off).The connection ended and Auto Reconnect is off.
Could not reconnect after N attempts. Giving up.Auto Reconnect used up Retry Times.
Server stopped responding.The server stopped answering PPP's keepalive messages.
The connection was closed while the device slept.On Sleep is Off and Auto Reconnect is off, so the VPN ended when the device slept.

What each server accepts

ServerMethods that workedLimits we met
MikroTik RouterOS 7.25MS-CHAPv2; PAP and CHAP with Enable PAP / CHAP.No EAP and no TLS 1.3 on its SSTP server; MS-CHAPv1 only is refused by the app.
Windows Server 2019, 2022 (RRAS with NPS or RRAS policies)MS-CHAPv2, EAP-MSCHAPv2, PEAP (with or without crypto binding).No EAP-TTLS or TEAP; no TLS 1.3 for EAP, which the app works around by retrying with TLS 1.2; local accounts refuse Identity Privacy; EAP-TLS with RRAS's own NPS needs an Active Directory domain.
Windows Server 2025 (RRAS with FreeRADIUS)MS-CHAPv2, EAP-MSCHAPv2, PEAP, EAP-TTLS, EAP-TLS.FreeRADIUS sends no PEAP crypto binding and has no TEAP in its default configuration.
SoftEther 4.44MS-CHAPv2; PAP and CHAP.No EAP in its SSTP server.

The Routing and Remote Access console shows no details

On our Windows servers the console listed the server as started but could not open it: no Ports, Remote Access Clients or IPv4 below it, only View, Delete, Refresh and Properties in its menu, and No properties are available on this object for Properties. The Remote Access Connection Manager service (RasMan), which the console talks to, was disabled on these servers, and it did not start when we tried: Windows logged event 7024 with the text {TDI Event Pending}, and sc queryex RasMan showed its own exit code 711, which Microsoft lists as RasMan initialization failure. RRAS and SSTP ran without it, because on these servers the RRAS service does not depend on RasMan (sc qc RemoteAccess lists Bfe, Http, RpcSS and SstpSvc). We left RasMan disabled and set RRAS up from PowerShell, as Windows Server shows.