Configuration Reference
The server settings that change what the app's SSTP profiles do, what each field of a profile does on the wire, and the settings the app always uses. Windows Server, MikroTik RouterOS, SoftEther VPN Server and FreeRADIUS build the servers this page refers to; Test results has the case behind each server setting.
Every server setting below is one our test servers had on 6 November 2026, set up as their guides describe: Windows Server 2019, 2022 and 2025 with Routing and Remote Access, MikroTik RouterOS 7.25, SoftEther VPN Server 4.44 and FreeRADIUS 3.2.5. An iPhone and an Android phone ran the cases against them; the cases named mt-srv-… changed one router setting each. The case names in the tables are the rows of Test results. Settings this page describes without a case were left as the guide or the server sets them. The profile fields and the settings the app always uses come from the source code of both apps, as on Setting up the app, and from the cases.
Server settings
One table per server product, with the settings that change what the app does. Our Windows Server 2019 and 2022 check logins against local Windows accounts. Our Windows Server 2025 sends every login to FreeRADIUS, and our MikroTik router and SoftEther server send it the logins of their RADIUS users; FreeRADIUS's own settings are in the last table.
Windows Server
Routing and Remote Access (RRAS), set up from PowerShell as Windows Server describes.
| Setting | What it does for the app | Cases |
|---|---|---|
Set-VpnAuthProtocol -UserAuthProtocolAccepted MsChapv2, EAP | RRAS accepts MS-CHAPv2 and EAP; PAP, CHAP and MS-CHAPv1 stay off. MS-CHAPv2, the app's default, connects, and so does EAP-MSCHAPv2 with MS-CHAPv2 off. | win2019-base-download, win2022-base-download, win2025-base-download, win2019-eap-mschapv2, win2022-eap-mschapv2, win2025-eap-mschapv2 |
Local accounts with the dial-in permission Allow access (netsh ras set user name=vpnuser dialin=permit), on 2019 and 2022 | The users the profile's Username and Password log in as. A wrong password ends with Authentication failed. The server rejected the username or password. RRAS with local accounts refuses the outer identity anonymous of Identity Privacy: Authentication failed. The server rejected the username or password, or the anonymous outer identity of Identity Privacy; if it checks the outer identity, turn Identity Privacy off. | win2019-wrong-password, win2022-wrong-password, win2019-peap-identity-privacy, win2022-peap-identity-privacy |
| Network Policy Server, policy Connections to Microsoft Routing and Remote Access server, Authentication Methods: Microsoft: Protected EAP (PEAP) and Microsoft: Secured password (EAP-MSCHAP v2) | The EAP types RRAS accepts: with both in the policy, EAP-MSCHAPv2 and PEAP connect. Our Network Policy Servers refused EAP-TTLS and TEAP; a profile that offers only one of them ends with Authentication failed. The server rejected the username or password. | win2022-eap-mschapv2, win2022-peap, win2019-ttls-expect-fail, win2022-ttls-expect-fail, win2019-teap-expect-fail, win2022-teap-expect-fail |
| PEAP: Certificate issued to the certificate SSTP uses, EAP type Secured password (EAP-MSCHAP v2) | PEAP runs a TLS session with this certificate inside the VPN login, and the app checks it too. Our Network Policy Servers have no TLS 1.3 inside EAP: when the app offers it, as it does by default, the server ends the exchange and the app tries again with TLS 1.2 by itself. PEAP connects with Enable TLS 1.3 on or off. | win2019-peap, win2022-peap, win2019-peap-tls13, win2022-peap-tls13, win2019-peap-tls12-legacy, win2022-peap-tls12-legacy |
| PEAP: Disconnect Clients without Cryptobinding off | Network Policy Server sends PEAP's crypto binding anyway, so a profile with Require Crypto Binding on connects. | win2019-peap-crypto-binding, win2022-peap-crypto-binding |
Set-VpnAuthType -Type ExternalRadius -RadiusServer <RADIUS_IP> -SharedSecret <RADIUS_SECRET>, on 2025 | RRAS sends the logins to FreeRADIUS and passes EAP to it unchanged, so the users and the EAP methods are those of FreeRADIUS: MS-CHAPv2, EAP-MSCHAPv2, PEAP, EAP-TTLS and certificate login connect. A wrong password ends with Authentication failed. The server rejected the username or password. | win2025-radius-mschapv2, win2025-radius-eap-mschapv2, win2025-radius-peap, win2025-ttls-pap, win2025-d-cert, win2025-radius-wrong-password |
Set-RemoteAccess -SslCertificate $cert, with a Let's Encrypt certificate for the server's name | The certificate SSTP presents. With the profile's defaults the app connects when it is valid for Host and chains to a root the phone trusts. With the server's IP address in Host, Custom SNI with the server's name connects; a Custom SNI the certificate is not for does not. | win2019-base-download, win2022-base-download, win2025-base-download, win2019-m-sni-ip, win2022-m-sni-ip, win2025-m-sni-ip, win2019-m-sni-wrong, win2022-m-sni-wrong, win2025-m-sni-wrong |
| Firewall rule Secure Socket Tunneling Protocol (SSTP-In) | RRAS turns it on. It allows TCP 443, where SSTP listens and where the app connects when Port is empty. | win2019-base-download, win2022-base-download, win2025-base-download |
Install-RemoteAccess -VpnType Vpn -IPAddressRange "10.79.0.1", "10.79.0.254" | The phone's tunnel address. RRAS keeps the first address for itself: on our server the phone got 10.79.0.2 and the server was 10.79.0.1. As DNS servers RRAS gives the phone those of the server's own network adapter. Our Windows Server 2025 has the range 10.80.0.1 to 10.80.0.254. | win2019-base-download, win2022-base-download, win2025-base-download |
netsh routing ip nat add interface name="<PUBLIC_ADAPTER>" mode=fullnetsh routing ip nat add interface name="Internal" mode=private | The phones' traffic leaves the server with the server's own address; our test server on the internet saw each case's traffic arrive from it. | win2019-base-download, win2022-base-download, win2025-base-download |
| SSTP ports: 128 | One for each connected phone. Left as RRAS sets it. |
MikroTik RouterOS
RouterOS 7.25, set up from its command line as MikroTik RouterOS describes. The value marked (ours) is our router's.
| Setting | What it does for the app | Cases |
|---|---|---|
authentication: mschap2 (ours), pap, chap, pap,chap,mschap1,mschap2, mschap1 | MS-CHAPv2, the app's default, connects with mschap2 and with all four allowed. For pap or chap, turn on Enable PAP / CHAP (Less Secure). A profile without a method the router allows ends with The server closed the connection during PPP negotiation. Check that it accepts one of the authentication methods enabled in this profile. The app has no MS-CHAPv1, so a router with mschap1 alone refuses it the same way. RouterOS's SSTP server has no EAP, so PEAP, EAP-TTLS, TEAP and certificate login do not apply to it; a profile with EAP-MSCHAPv2 on as well as MS-CHAPv2 connects. | sstp-base-download, mt-srv-all-auth-client-mschapv2, mt-srv-pap, mt-srv-chap, mt-srv-pap-client-mschapv2-only, sstp-papchap-only, sstp-no-auth-method, mt-srv-mschap1-only, sstp-eap-mschapv2-plus-mschapv2 |
/ppp secret add name=vpnuser password=<PASSWORD> profile=sstp-profile service=sstp | The user the profile's Username and Password log in as. A wrong password ends with Authentication failed. The server rejected the username or password. | sstp-base-download, sstp-wrong-password |
/radius add address=<RADIUS_IP> secret=<RADIUS_SECRET> service=ppp timeout=3s/ppp aaa set use-radius=yes | The router also checks SSTP logins against FreeRADIUS. A RADIUS user logs in with MS-CHAPv2 and, with authentication=pap and Enable PAP / CHAP, with PAP. A wrong password ends with Authentication failed. The server rejected the username or password. | mt-radius-mschapv2, mt-radius-pap, mt-radius-wrong-password, mt-radius-wrong-password-debug |
certificate=sstp-le, a Let's Encrypt certificate from /certificate add-acme | The certificate SSTP presents. With the profile's defaults the app connects when it is valid for Host and chains to a root the phone trusts. With the router's IP address in Host, Custom SNI with the router's name connects; a Custom SNI the certificate is not for does not. | sstp-base-download, sstp-ip-custom-sni, mt-m-sni-ip, sstp-sni-wrong, mt-m-sni-wrong |
tls-version: any (ours), only-1.2 | Both connect. RouterOS's SSTP server offers TLS 1.0 to 1.2, not TLS 1.3, so the app uses TLS 1.2 with it. A profile with Disable TLS 1.0 & 1.1 connects too. | sstp-base-download, mt-srv-tls12-only, sstp-disable-legacy-tls |
ciphers: both (ours), aes256-gcm-sha384, aes256-shapfs: yes (ours), requiredmax-mtu, max-mru: 1500 (ours), 1400mrru: disabled (ours), 1600 | Every value tested connects with the profile's defaults. | sstp-base-download, mt-srv-cipher-gcm, mt-srv-cipher-cbc, mt-srv-pfs-required, mt-srv-mtu-1400, mt-srv-mrru |
port: 443 | Where SSTP listens, and where the app connects when Port is empty. A profile with another port (4443 in our case) ends with Cannot reach the server (DNS/TCP/TLS failed). Check the host, port and certificate settings. Left as RouterOS 7.25 sets it. | sstp-base-download, sstp-wrong-port |
/ip pool add name=sstp-pool ranges=10.77.0.10-10.77.0.250/ppp profile add name=sstp-profile local-address=10.77.0.1 remote-address=sstp-pool dns-server=1.1.1.1,8.8.8.8 … use-ipv6=no | The phone's tunnel address comes from the pool, and the PPP profile hands out the DNS servers of dns-server. The app asks for IPv4 only, so the profile hands out no IPv6. | sstp-base-download |
change-tcp-mss=yes in the PPP profile | Lets the router lower the TCP segment size of connections through the tunnel to fit the tunnel. Left as the guide sets it. | |
/ip firewall nat add chain=srcnat action=masquerade | The phones' traffic leaves the router with the router's own address; our test server on the internet saw each case's traffic arrive from it. | sstp-base-download |
| A session the router drops | With Auto Reconnect on, the app connects again within seconds; with it off, the VPN ends with Connection lost (auto reconnect is off). | mt-life-peer-drop-reconnect, mt-life-peer-drop-no-reconnect, android-life-peer-drop-reconnect, android-life-peer-drop-no-reconnect |
| The SSTP server turned off while a phone is connected | Auto Reconnect tries again; with Retry Times 2 the VPN ends after two attempts with Could not reconnect after 2 attempts. Giving up. | mt-life-retry-exhausted, android-life-retry-exhausted |
SoftEther VPN Server
Version 4.44 on Ubuntu, set up with vpncmd as SoftEther VPN Server describes.
| Setting | What it does for the app | Cases |
|---|---|---|
SstpEnable yes | SoftEther answers SSTP clients next to its own protocol. Of the TCP ports it listens on, 443, 992, 1194 and 5555, SSTP uses 443, where the app connects when Port is empty. The profile's defaults connect. | se-verified-download, se-verified-upload |
UserCreate vpnuser …UserPasswordSet vpnuser /PASSWORD:<PASSWORD>in the hub DEFAULT | SSTP clients log in to the Virtual Hub DEFAULT. SoftEther's PPP for SSTP accepts PAP, CHAP and MS-CHAPv2, but no EAP: MS-CHAPv2, the app's default, connects, and so does Enable PAP / CHAP with MS-CHAPv2 off. A profile that offers only EAP methods ends with The server closed the connection during PPP negotiation. Check that it accepts one of the authentication methods enabled in this profile. A wrong password ends with Authentication failed. The server rejected the username or password. | se-verified-download, se-papchap-only, se-eap-mschapv2, se-d-eap-only, se-wrong-password |
RadiusServerSet 127.0.0.1:1812 /SECRET:<RADIUS_SECRET> /RETRY_INTERVAL:500UserRadiusSet radiususer /ALIAS:none | A user marked for RADIUS is checked by FreeRADIUS. A RADIUS user logs in with MS-CHAPv2, and with Enable PAP / CHAP when MS-CHAPv2 is off. A wrong password ends with Authentication failed. The server rejected the username or password. | se-radius-mschapv2, se-radius-pap, se-radius-wrong-password |
ServerCertSet /LOADCERT:… /LOADKEY:…, with a Let's Encrypt certificate | SoftEther keeps its own copy of the certificate and presents it for SSTP. With the profile's defaults the app connects when it is valid for Host and chains to a root the phone trusts. With the server's IP address in Host, Custom SNI with the server's name connects; a Custom SNI the certificate is not for does not. SoftEther offers TLS 1.3, which the app uses with it. | se-verified-download, se-ip-custom-sni, se-m-sni-ip, se-m-sni-wrong |
BridgeCreate DEFAULT /DEVICE:soft /TAP:yes, with dnsmasq and NAT on Linux | The phone gets its tunnel address (192.168.30.10 to 192.168.30.250) and DNS servers (1.1.1.1 and 8.8.8.8) from dnsmasq on tap_soft, and Linux NATs the phones' traffic with the server's address; our test server on the internet saw each case's traffic arrive from it. Our SoftEther cases ran this way, except the two SecureNAT ones. | se-verified-download, se-heavy-soak |
SecureNatEnable | SoftEther's own NAT and DHCP, with no Linux network settings: the phone gets an address from 192.168.30.10 to 192.168.30.200 with the gateway 192.168.30.1. On our server SoftEther's kernel-mode NAT starts about 10 seconds after SecureNAT; the cases ran with it running. With downloads and uploads at once, the Local Bridge kept more download speed. | se-securenat-download, se-securenat-heavy-soak, se-heavy-soak |
FreeRADIUS
FreeRADIUS 3.2.5 from the Ubuntu 24.04 packages, with its files in /etc/freeradius/3.0/, set up as FreeRADIUS describes. MikroTik and SoftEther have no EAP of their own, so the EAP rows were tested through Windows Server 2025.
| Setting | What it does for the app | Cases |
|---|---|---|
clients.conf: one client per SSTP server, with its secretmods-config/files/authorize: vpnuser Cleartext-Password := "<PASSWORD>" | One user list for all three servers. MS-CHAPv2 needs the password in a form the server can compute with, so it is stored as Cleartext-Password. A wrong password ends with Authentication failed. The server rejected the username or password. | mt-radius-mschapv2, se-radius-mschapv2, win2025-radius-mschapv2, mt-radius-wrong-password, se-radius-wrong-password, win2025-radius-wrong-password |
private_key_file, certificate_file in the tls-config tls-common section of mods-available/eap, with a Let's Encrypt certificate | With PEAP, EAP-TTLS and EAP-TLS, FreeRADIUS opens its own TLS session to the phone inside PPP, with this certificate. The app checks it: it must chain to a root the phone trusts, unless Allow Untrusted Certificate is on. | win2025-peap, win2025-ttls-pap, win2025-d-cert |
tls_min_version = "1.2"tls_max_version = "1.2" | The app offers TLS 1.3 for EAP by default and FreeRADIUS answers with TLS 1.2, which the app accepts; PEAP connects with Enable TLS 1.3 on or off. Left as the package sets it. | win2025-peap-tls13, win2025-peap-tls12-legacy |
ca_file: the CA that issued our client certificates | Certificate login (EAP-TLS): a client certificate from this CA logs in. One from another CA ends with Authentication failed. The server rejected the client certificate; check that the server trusts its issuer and that it is still valid. | win2025-d-cert, win2025-d-cert-rogue |
The eap module as the package has it | EAP-MSCHAPv2 connects, and so does PEAP with EAP-MSCHAPv2 inside, also with the outer identity anonymous of Identity Privacy. PEAP from FreeRADIUS sends no crypto binding, so a profile with Require Crypto Binding on ends with Authentication failed. The server rejected the username or password. | win2025-eap-mschapv2, win2025-peap, win2025-peap-identity-privacy, win2025-peap-crypto-binding |
default_eap_type = md5 in the ttls section | EAP-TTLS with PAP, CHAP or EAP-MSCHAPv2 inside connects. For EAP inside EAP-TTLS, FreeRADIUS first offers EAP-MD5; the app never answers EAP-MD5 and asks for EAP-MSCHAPv2 instead, which FreeRADIUS then uses. | win2025-ttls-pap, win2025-ttls-expect-fail, win2025-ttls-mschapv2, win2025-ttls-eap |
TEAP, commented out in this version's eap file | A profile that offers only TEAP ends with Authentication failed. The server rejected the username or password. | win2025-teap-expect-fail |
What each profile field does
The fields of Setting up the app, in the editor's order.
| Field | On the wire |
|---|---|
| Host, Port | The app opens a TCP connection to Host on Port, directly or through the proxy, starts TLS and sends one HTTP request inside it, SSTP_DUPLEX_POST. An empty Port is 443. Unless Custom SNI is on, the app checks the certificate against Host, so the server's IP address in Host usually brings the certificate warning: the certificate names the server, not its address. When the name does not resolve, nothing answers on the port or the TLS handshake fails, the app says Cannot reach the server (DNS/TCP/TLS failed). Check the host, port and certificate settings. |
| Allow Untrusted Certificate | Off (default): before connecting, the app checks the server's certificate the way the tunnel will. It must chain to a root the phone trusts and be valid for Host, or for SNI Hostname when Custom SNI is on; otherwise the app shows DANGEROUS!, where Continue connects once without the check, Save and Continue turns this switch on, and Cancel does not connect. On: no check, also for the EAP server's certificate. |
| Method, Username, Password, Certificate | Password (default): PPP logs in with Username and Password by one of the methods below. Certificate: EAP-TLS with the client certificate imported from a .p12 or .pfx file that holds it and its private key; Username is optional and is sent as the identity. |
| Enable MS-CHAPv2, Enable PAP / CHAP (Less Secure) | The PPP login methods the app offers, with the EAP methods below; the server picks one. MS-CHAPv2 is on by default, PAP / CHAP off. PAP sends the password inside the TLS tunnel without hashing it. When the server accepts none of the methods that are on: The server closed the connection during PPP negotiation. Check that it accepts one of the authentication methods enabled in this profile. |
| EAP Configuration: Enable EAP-MSCHAPv2 | MS-CHAPv2 inside EAP, without a TLS tunnel of its own. |
| Enable PEAP, Require Crypto Binding | A TLS tunnel to the EAP server with EAP-MSCHAPv2 inside. The app checks the EAP server's certificate; one that does not chain to a root the phone trusts ends with The EAP server's certificate is not trusted: … With Require Crypto Binding, the connection fails unless the server proves with PEAP's crypto binding that the inner and outer sessions belong together; Windows NPS sends it, FreeRADIUS does not. |
| EAP-TTLS Method | Disabled (default), or EAP-TTLS with PAP or CHAP inside, or with EAP-MSCHAPv2 inside, which both EAP and MSCHAPv2 choose. |
| Enable TEAP | TEAP without a secondary method. |
| Enable Identity Privacy, Identity | Before the TLS tunnel is up, the app sends Identity (default anonymous) instead of the username. |
| Enable TLS 1.3, Disable TLS 1.0 & 1.1 (EAP) | The TLS versions of the EAP tunnel, both on by default: TLS 1.2 or later, with TLS 1.3 offered. When the server ends the exchange on a TLS 1.3 offer, as Windows NPS does, the app tries once more with TLS 1.2. |
| Proxy: None, Manual (Address, Port, Username, Password), Auto (PAC URL) | The proxy carries only the connection to the server; the traffic inside the VPN does not use it. None (default) connects directly. Manual tries SOCKS5 first and, when the proxy does not answer as SOCKS5, HTTP CONNECT on a new connection; the username and password go to the proxy when it asks for them. Auto fetches the PAC file over http or https, runs its FindProxyForURL for the server and tries the proxies it returns in order; the username and password go to the proxy the script picks. |
| Disable TLS 1.0 & 1.1 (Options) | The TLS connection to the server uses TLS 1.2 or later. It applies to that connection only; each of our test servers connected with it on. |
| Auto Reconnect, Retry Times | Auto Reconnect (on by default) connects again 2 seconds after a connection that was up is lost; with it off the VPN ends with Connection lost (auto reconnect is off). Retry Times limits the attempts in a row, and empty means no limit; then the VPN ends with Could not reconnect after N attempts. Giving up., or, when the server cannot be reached, Cannot reach the server after N attempts. … A login the server refused is never retried. |
| Switch to Wi-Fi When Available | On by default: when Wi-Fi appears while the VPN is up, the app moves the connection to it. No test changed the network under a connected tunnel. |
| On Sleep | Stay (default) keeps the connection while the device sleeps. Pause closes it and connects again on wake. Off closes it; on wake the app connects again only with Auto Reconnect on, otherwise the VPN ends with The connection was closed while the device slept. |
| Log Level | Normal: the milestones, such as the server the app connects to, the SSTP and PPP states, the addresses the server gave, and errors. Expert adds the TLS name the app checks, each PPP phase and the login methods the profile offered. Debug adds the SSTP client's and PPP's own lines. No level writes the password or TLS session secrets. When the app gives up on a connection, a line starting with SSTP: closing with reason: names the reason. |
| Enable Custom SNI, SNI Hostname | Sends SNI Hostname in the TLS ClientHello and checks the certificate against it, while the connection still goes to Host. It must be a bare hostname. With Custom SNI off, a name left in SNI Hostname is not used. |
| TLS Fragmentation, First Chunk, Following Chunks | Splits the outgoing bytes of the TLS handshake into small TCP writes; the TLS data itself is unchanged. Auto sends the first 43 bytes on their own, so that the server name lands in a later write, then 256 bytes per write (128 on cellular) with a few milliseconds between writes. Manual: First Chunk (1 to 4096 bytes, default 32), then Following Chunks (1 to 16384, default 256). A larger size stops the connection before it starts: Invalid TLS fragmentation settings: chunk sizes out of bounds |
Settings the app always uses
- SSTP runs inside TLS on one TCP connection: after one HTTP request,
SSTP_DUPLEX_POST, and the server's answer, the connection carries SSTP packets both ways, and they carry PPP. - After the login, the app sends the server a crypto binding value computed from the login's keys and the server certificate it saw. A server that checks it, as Windows does, can tell that nobody in the middle replaced the TLS connection.
- It asks the server for IPv4 only. PPP gives the phone an IPv4 address and DNS servers, and all of the phone's IPv4 traffic then goes through the tunnel.
- It never answers EAP-MD5, even when a server offers it first, because MD5 gives no key for the SSTP crypto binding and no proof of the server.
- A connection that is not up 30 seconds after the start ends with Connection timed out. The server did not respond.
- When the server stops answering PPP's keepalive messages, the VPN ends with Server stopped responding.
- The iPhone and the Android app use the same SSTP and PPP code and show the same messages.