WireGuard client setup: Windows, macOS, iOS, Android, Linux

Once you have a WireGuard server running, connecting a client is mostly the same flow on every platform: install the official app, import a config, toggle the tunnel. The details differ in places that matter — DNS, kill-switch behavior, auto-reconnect. Per-platform notes below.

Disclosure: contains an affiliate link to Inferno VPS.

Before you start

iOS

Install: "WireGuard" by WireGuard Development Team in the App Store.

Import:

  1. Open the app, tap "Add a tunnel."
  2. Pick "Create from QR code." Point the camera at the QR generated by wg-easy or by qrencode < client.conf.
  3. Name the tunnel ("Home VPS" or similar).
  4. iOS prompts to add a VPN configuration — confirm with Face/Touch ID.

Activate: toggle the switch next to the tunnel. The VPN indicator appears in the status bar.

Verify: open Safari, visit ifconfig.me. The IP shown should be the server's VPS IP, not your cellular IP.

iOS gotchas:

Android

Install: "WireGuard" by WireGuard Development Team in the Play Store, or via F-Droid.

Import:

  1. Tap the "+" button → "Scan from QR code."
  2. Or use "Import from file or archive" to load a .conf file from local storage.

Android-specific features:

Windows

Install: download the official MSI from wireguard.com/install/.

Import:

  1. Open WireGuard. Click "Add Tunnel → Import tunnel(s) from file."
  2. Pick your client.conf.
  3. Click "Activate."

Windows gotchas:

macOS

Install: "WireGuard" from the Mac App Store.

Import:

  1. Click "+ → Import tunnel(s) from file."
  2. Pick the .conf.
  3. Click the toggle in the menu bar icon to activate.

macOS gotchas:

Linux (CLI, systemd-based)

Install:

sudo apt install -y wireguard wireguard-tools   # Debian/Ubuntu
# or
sudo dnf install -y wireguard-tools             # Fedora

Import:

sudo cp client.conf /etc/wireguard/wg0.conf
sudo chmod 600 /etc/wireguard/wg0.conf
sudo wg-quick up wg0
sudo wg show                       # verify handshake
curl ifconfig.me                   # should report VPS IP

# Enable on boot
sudo systemctl enable wg-quick@wg0

Bring it down: sudo wg-quick down wg0.

Linux (GNOME / NetworkManager GUI)

  1. Install the NetworkManager plugin: sudo apt install network-manager-l2tp-gnome network-manager-openvpn-gnome — and on newer distros network-manager-openconnect-gnome handles WireGuard via the standard import dialog.
  2. Settings → Network → "+" → import the .conf.
  3. Toggle the connection on.

Verifying everything actually works

  1. IP test: visit ifconfig.me before and after activating. The IP should change to the server's VPS IP.
  2. DNS leak test: visit dnsleaktest.com (or any equivalent). The DNS resolvers shown should be the ones in your tunnel's DNS = line, not your ISP's.
  3. IPv6 leak test: if your tunnel only includes 0.0.0.0/0 (not ::/0), IPv6 traffic bypasses the VPN entirely. Either include both, or disable IPv6 on the client.
  4. WebRTC leak test: use any "WebRTC leak test" page; if it reveals your local IP, your browser is leaking — disable WebRTC or use a hardened browser.

Reconnect and roaming

WireGuard handles network changes silently — switching from Wi-Fi to cellular doesn't require a manual reconnect. The first few packets after a change may drop until the handshake re-establishes (typically < 2 seconds). The PersistentKeepalive = 25 line in the client config keeps the tunnel alive through NAT timeouts.

Common client-side issues

"Handshake never completes"

Public key on the client doesn't match what's registered on the server, or the server endpoint IP/port is wrong, or UDP 51820 is blocked between client and server (corporate firewalls, some captive-portal Wi-Fi).

"Tunnel active but no internet"

The server-side NAT (iptables MASQUERADE) didn't get applied. Re-run sudo wg-quick down wg0 && sudo wg-quick up wg0 on the server, or restart the wg-easy container.

"Some sites work, others timeout"

MTU mismatch. The default WireGuard MTU is 1420; if your client's network has unusual MTU (mobile carriers, satellite, some VPN-over-VPN setups), packets get dropped. Add MTU = 1280 to the [Interface] block of the client config and try again.

"Tunnel disconnects after 5-10 minutes of idle"

NAT timeout on the client's network. Set PersistentKeepalive = 25 in the client's [Peer] block.

"DNS works but very slow"

The DNS server in your config is geographically far from the VPS. Change to one closer to the VPS, e.g. 9.9.9.9 (Quad9 has many anycast nodes) or set the VPS itself as the resolver (if you run one).

Need a VPS for the server side?

If you haven't already provisioned the server, the $3.49 Inferno plan handles a single-user VPN comfortably. Pick a location close to where you spend most time — latency adds up across every connection.

View Inferno locations →

What to do next


Author: Hanna Wagner — Frankfurt. Last tested: 2026-05-22 on WireGuard iOS 1.0.16, macOS 1.0.16, Windows 0.5.3, Android 1.0.20231030, Ubuntu 22.04.