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, which share the SoftEther client core and show the same messages, except where a row names the phone. The cases named next to a message produced it 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 SoftEther: closing with reason: names the reason. For more detail, set Log Level to Expert or Debug in the profile and connect again: Expert adds the states the connection goes through and the virtual adapter's DHCP and ARP lines, and Debug adds the SoftEther core's own lines, such as each TCP connection it opens.
  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 does not, check the server's firewall and that SoftEther VPN Server runs (ListenerList in vpncmd).
  3. Does the name match the certificate? The app checks the certificate against Hostname, or against Server when Hostname is empty.
  4. Does the method match the user? The login method in the profile must match the user's kind on the server; see Users for each login method.
  5. What does the server say? The hub's log in /opt/vpnserver/security_log/<HUB>/ names each login and why it failed.

Messages

Before the connection starts

MessageWhat happenedWhat to do
DANGEROUS! with the server's certificatesWith TLS Server Verification on, the certificate does not chain to a root the phone trusts, or it is not valid for the name the app checks. Our case sev-verify-ip-declined, a profile with the server's IP address, brings it.Use the name the certificate is for, or put it in Hostname. Continue and Save and Continue skip the check; see the certificate warning.
Certificate authentication requires a client certificate in the profile. (iPhone) or The client certificate could not be read. Re-import it in the profile.Method Certificate without a certificate the app can read.Import the .p12 or .pfx file again in the profile.

Reaching the server

MessageWhat happenedWhat to do
Cannot reach the server (DNS lookup or TCP connection failed). Check the Server field for typos and the network connection.The name did not resolve, or no connection came up. Our cases sev-natt-off-closed-tcp-port, a port nothing listens on, and sev-natt-hint-wrong, NAT-T with a hint no server has, end this way.Check Server, Port and the phone's network. With NAT-T, check NAT-T Hint. A server whose TCP port cannot be reached at all may still be reached with Enable NAT Traversal (sev-natt-closed-tcp-port).
The TLS handshake with the server failed. Check the Server and Port fields.Another service answered at that address and port, so no TLS connection came up. Our case sev-port-other-service, the server's SSH port, ends this way.Use a port of the server's ListenerList (443, 992 or 5555 by default).
The server did not answer as a SoftEther VPN server. Check the Server and Port fields.Something answered at that address and port, but not as SoftEther VPN Server, for example a web server, or the connection closed during the TLS handshake.Check Server and Port.
The server and the app have no TLS version in common. or … no TLS cipher in common.The server offers only TLS versions or ciphers the app does not use.Check the TLS versions and ciphers the server allows. Our server's defaults worked on both phones, with TLS 1.3.
Connection timed out. The server did not respond.The connection did not come up within 30 seconds.Check that the server is up and that its port is reachable from the phone's network.
The connection to the server was closed.The connection ended before the login finished.Check the server, and the proxy if the profile uses one.

Proxies

MessageWhat happenedWhat to do
Proxy authentication failed.The proxy refused the proxy username or password (sev-proxy-http-wrong-auth, sev-proxy-socks5-wrong-auth).Check Username and Password in the proxy section, and the proxy's Type.
Cannot connect to the proxy server.The proxy did not take the connection (sev-proxy-unreachable, a proxy port nothing listens on).Check the proxy's address and port.
Unable to download PAC configurationThe PAC URL did not answer with a file (sev-pac-missing).Open the PAC URL in a browser; it must answer over http or https.
No usable proxy returned by PACThe PAC file's FindProxyForURL returned no entry the app can use.Return PROXY host:port, SOCKS host:port, SOCKS5 host:port or DIRECT.

Login and certificate

MessageWhat happenedWhat to do
Authentication failed. Check the username, password and authentication method.The hub refused the login: a wrong password (sev-wrong-password, sev-radius-wrong-password), a method that does not match the user's kind (sev-radius-user-standard-method, sev-anon-on-password-user), or a client certificate the hub does not accept (sev-cert-rogue-ca). The app does not retry it.Check the username and password, the Method, and for certificates the hub's CAList or the user's certificate. The hub's security log says which user failed.
Virtual Hub not found. Check the Virtual Hub field.The server has no hub of that name (sev-wrong-hub).Use a name from HubList in vpncmd; empty means DEFAULT.
The server certificate name does not match the server. Check the Hostname field.The certificate is trusted but not for the name the app checks (sev-hostname-override-wrong on iPhone; on Android the certificate warning comes first).Put the name the certificate is for in Hostname, or empty it.
The server certificate is not trusted. Enable verification only with a valid certificate, or check the Hostname field.The certificate does not chain to a root the phone trusts.Install a certificate from a public authority on the server (Certificate), or turn TLS Server Verification off.
The server certificate has expired.The server's certificate is past its end date.Renew it on the server and load it with ServerCertSet.

After the connection was up

MessageWhat happenedWhat to do
Connection lost (auto reconnect is off).The session ended, for example because the server disconnected it, and Auto Reconnect is off (sev-life-peer-drop-no-reconnect).Connect again, or turn Auto Reconnect on.
Could not reconnect after N attempts. (…)Auto Reconnect tried as often as Retry Times allows and the server stayed away (sev-life-retry-exhausted). The reason of the last attempt follows in brackets.Check the server. Empty Retry Times keeps trying while the server is away (sev-life-outage-reconnect).
The connection was closed while the device slept.On Sleep is Off and Auto Reconnect is off, so the connection closed when the device slept and did not come back on wake.Choose On Sleep Stay or Pause, or turn Auto Reconnect on.
SoftEther error N: …Another error of the SoftEther core, by its number and name.Look the number up in SoftEther's error list, and check the server's log at the same time.

Limits