Open the macOS App Store and find the WireGuard app.Using the Mullvad app Option 2: use the WireGuard appĬurrently, the WireGuard app requires macOS version 12.0 (Monterey) or newer.

The Mullvad VPN app for macOS uses the WireGuard protocol by default, so all you need to do is connect. Image: lscr.This guide for macOS users explains how to connect to Mullvad’s WireGuard® servers.Ĭhoose one of the two following options. In a nutshell, I only had to change the network_mode from the previous deployment. No change here as I’m still using the same container. If you look at the ports on top, you’ll see 8080 I’ve added it for qBittorrent, as we can’t use port commands over there. The port you opened goes into FIREWALL_VPN_INPUT_PORTS, and you’ll want to add your local subnet to FIREWALL_OUTBOUND_SUBNETS so you can reach the attached containers. The file will provide the WIREGUARD_PRIVATE_KEY, WIREGUARD_ADDRESS, VPN_ENDPOINT_PORT, and DNS. Remember or take a screenshot of your port, and open the configuration file you downloaded in the previous step. Move on to the port creation page, choose a city, select the Wireguard configuration as your device, and then click Add port. The first step is to generate a Wireguard configuration file over at Mullvad.įor Docker, switch to Linux as the platform, generate a key, and select your exit point in my example, Frankfurt server 4 translates to de4-wireguard. The original documentation to use Mullvad is here. And the best is that it is appropriately documented! It supports various VPN services out of the box and works with both OpenVPN and Wireguard. While shopping around, I discovered Gluetun, and I’m wondering why it took me so long, as it seems to be an all-in-one solution for containerized VPN. I moved from OpenVPN to Wireguard, so I needed a new way of connecting. So I kept looking, and I’m now using Mullvad Wireguard qBittorrent Docker. Two weeks ago, I changed my VPN provider and how I use VPN, but I wasn’t happy with the performance.

Mullvad wireguard setup