


I have enabled the port to go through the firewall in the Google Cloud console aswell. I have opened a port on the Mullvad page which is the same port as the Wireguard server (triple checked this) and I am using the IP of the Mullvad server as endpoint to connect to.

If you’re using the Mullvad VPN app, follow our guide on how to turn on WireGuard in the app. However, when I connect to Mullvad through the CLI, I lose all access to the VM (which I expected), but I can't connect to the Wireguard server anymore. This Windows guide explains how to connect to Mullvad’s WireGuard® servers. Everything works and traffic goes through smoothly. I can connect to the Wireguard server just fine once the interface is up. Hit save so you don’t accidentally lose the keys 3. Click Generate and take a copy the Public key into temporary notepad c. But you can use port forwarding function, but I dont recommend. I do this so I can install a Pi-Hole instance aswell as an Unbound instance. Go to VPN -> Wireguard -> Add Tunnel Configure the tunnel a. Mullvads wireguard server does not connect/route between clients. I plan to host a Wireguard server on a Google Cloud VM (Ubuntu), which is then connected to my VPN provider (In this case, Mullvad).
