vpn-egress-setuplisted
Install: claude install-skill THEROCKSSS/vpn-egress
# VPN Egress — Setup
Provisioning and repair. If the stack already runs, you want
`vpn-egress-testing` instead.
Repo: `projects/vpn-egress/`. Long-form: `docs/SETUP.md`,
`docs/TROUBLESHOOTING.md`.
## Is setup even needed?
Check before building anything:
```bash
cd projects/vpn-egress && bash tools/stack.sh health
```
Exit 0 with `"mullvad_exit_ip":true` — the stack is fine. Stop here and use
`vpn-egress-testing`.
Non-zero, or the container doesn't exist — continue.
## First-time provisioning
### 1. Prerequisites
- Docker with Compose v2 (`docker compose`, not `docker-compose`).
- **WSL2 backend on Windows.** The Hyper-V backend doesn't expose
`/dev/net/tun` and gluetun cannot start. No workaround.
- A Mullvad account with time on it.
- **~10 GB of disk and a few minutes for the first build.** The GUI browser
image is built here rather than pulled (it adds Brave and Firefox to the
LinuxServer Chromium base) and lands around 5.6 GB. Tell the user this
before starting — an unexplained multi-minute build reads like a hang.
### 2. Mullvad key
This step needs the user — it requires their Mullvad login. Ask them to
generate a WireGuard config at <https://mullvad.net/en/account> → **WireGuard
configuration** and hand over two values from the `[Interface]` block:
- `PrivateKey`
- `Address`
Tell them the server they pick doesn't matter — the key authenticates to the
*account*, so gluetun works with any `SERVER_CITIES` value. That question
otherwise stalls the hand