WireGuard
A WireGuard profile connects to a WireGuard server over UDP with the phone's own keys, from a .conf file the server makes or from keys entered by hand. SRP VPN Connect does this with the same engine on iPhone and Android: wireguard-go, the version of 6 October 2026 (2631ce99a06f).
How a WireGuard connection works
- The keys. The server and each phone have a key pair. The server has each phone's public key as a peer, with the phone's address in the tunnel; the phone's file has its own private key, the server's public key and the server's address. A preshared key per phone can add a second secret.
- The handshake. The phone sends a handshake to the server over UDP. The server answers only a key it has as a peer, with the right preshared key; to anything else it says nothing at all, so a stranger cannot even tell that a server is there. The app counts as connected once the answer has come.
- The tunnel. The phone's traffic for the file's
AllowedIPs, usually all of its IPv4 traffic, goes through the tunnel, and the server passes it on to the internet with its own address. - Keeping it up. WireGuard renews the handshake every 2 minutes while traffic flows, and moves with the phone from network to network. When nothing comes back for 30 seconds while the phone sends, the app counts the server as gone: Auto Reconnect starts new handshakes, or the VPN ends with the reason.
Where to start
- Set up the server: WireGuard server sets up WireGuard on Ubuntu 24.04 with forwarding and NAT, and a file for each phone.
- Install the app: on iPhone from TestFlight, on Android by building it from the source; see Installation. Our tests ran the code of commit
3731b356on the iPhone and ofc1410582, which follows it, on Android; on iPhone use TestFlight build 40 (commit17233158) or later, the first with this code. - Add a WireGuard profile: Setting up the app.
- The server settings and the lines of a phone's file that matter to the app: Configuration Reference.
- If it does not connect: Troubleshooting.
What was tested
Test results lists every case we ran against our WireGuard server, with its result on an iPhone and on an Android phone: transfers in both directions and 16 connections at once, UDP through the tunnel, a split tunnel, files with and without a preshared key and keepalive, keys entered by hand, the Server and Port fields, wrong keys and other refusals with their messages, sleep, a server that restarts, goes away or stops answering, Retry Times, network changes and the log levels, and the server as WireGuard server sets it up.