Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
WE
Self-host wg-easy
updated Sep 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Sep 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
The easiest way to run your own WireGuard VPN server, with a clean web UI for adding and managing clients — a self-hosted alternative to Tailscale and commercial VPNs for private access to your network from anywhere.
Pick wg-easy when you want one WireGuard server with a web UI and nothing else to learn: add a client, scan the QR code, done. The v15 line (a full rewrite; v15.4.0 as of September 2026) lists one-time links, client expiry, 2FA, OIDC login, Prometheus metrics, IPv6 and per-client firewall rules among its features, all in one AGPL-3.0 container, and the documented requirements are just a host you manage, a domain or public IP, `curl`, and x86_64 or arm64. It is a hub-and-spoke VPN, not a mesh — every client routes through this one box — which is exactly why it is the simplest pick here.
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# wg-easy — official docker run (docs → Examples → Docker Run); web UI on 51821/tcp, tunnel on 51820/udp# 1. One-time IPv6-enabled bridge network the container gets fixed addresses ondocker network create -d bridge --ipv6 --subnet 10.42.42.0/24 --subnet fdcc:ad94:bacf:61a3::/64 wg# 2. The container. The /lib/modules mount is required — without it wg0 never comes up.docker run -d --net wg -e INSECURE=true --name wg-easy \ --ip6 fdcc:ad94:bacf:61a3::2a --ip 10.42.42.42 \ -v ~/.wg-easy:/etc/wireguard \ -v /lib/modules:/lib/modules:ro \ -p 51820:51820/udp -p 51821:51821/tcp \ --cap-add NET_ADMIN --cap-add SYS_MODULE \ --sysctl net.ipv4.ip_forward=1 --sysctl net.ipv4.conf.all.src_valid_mark=1 \ --sysctl net.ipv6.conf.all.disable_ipv6=0 --sysctl net.ipv6.conf.all.forwarding=1 --sysctl net.ipv6.conf.default.forwarding=1 \ --restart unless-stopped ghcr.io/wg-easy/wg-easy:15# → http://SERVER_IP:51821 — the first-run wizard creates the admin account. INSECURE=true allows plain HTTP;# for HTTPS put Caddy or Traefik in front (docs → Examples) and drop it.
wg-easy's defaults are safe, which means a few of them will stop you until you read the docs:
non-negotiableThe web UI refuses plain HTTP unless INSECURE=true. The docs' position is that "This is insecure. You should use a reverse proxy to secure the connection.", and the no-proxy page adds "Make sure that the Web UI is not accessible from outside your local network." Our snippet publishes 51821/tcp directly and does not set INSECURE — put Caddy or Traefik in front for the first login, or set it deliberately for LAN-only access.
non-negotiablev15 is "a complete rewrite": configuration files and environment variables changed, most settings moved into the Admin Panel, and armv6/armv7 hosts "won't be able to migrate to v15". Moving from v14 means backing up wg0.json from the old UI and uploading it in the new setup wizard; old environment variables are not migrated.
non-negotiableIt needs the host kernel's WireGuard: upstream mounts /lib/modules:ro with NET_ADMIN and SYS_MODULE (Podman also wants NET_RAW), and both its compose file and its docker run example set net.ipv4.ip_forward=1, net.ipv4.conf.all.src_valid_mark=1 and the IPv6 forwarding sysctls. Our snippet has the mount and capabilities; add the sysctls if clients connect but cannot reach anything.
non-negotiableINIT_* variables "will only be used during the first start of the container. After that, the setup will be disabled" — later changes go through the UI, not the environment. They also come in groups: "If variables are in the same group, you have to set all of them", and skipping the setup wizard needs all of group 1 (INIT_USERNAME, INIT_PASSWORD, INIT_HOST, INIT_PORT). Our snippet sets only INIT_ENABLED and INIT_HOST, so expect the wizard on first visit unless you add the other three.
non-negotiableOnly UDP 51820 needs to be open on the firewall for clients; the 256 MB floor is our estimate — the docs publish no RAM figure.
wg-easy used 172 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.8.1 (first boot, measured Sep 2026). We list a minimum of 256 MB.
Is the wg-easy install snippet verified?
The wg-easy install snippet is marked verified on Ubuntu 26.04 (Sep 2026).