Mullvad wireguard freezing

[ForestHorns]

Im having issues setting up wireguard with Mullvad. It seems to get the ip just fine then the entire container freezes? Im new to docker/self host so I have no idea whats going on.

Fresh install of omv6
The compose file im using is :

version: "3"
services:
  gluetun:
    image: qmcgaw/gluetun
    cap_add:
      - NET_ADMIN
    environment:
      - VPN_SERVICE_PROVIDER=mullvad
      - VPN_TYPE=wireguard
      - WIREGUARD_PRIVATE_KEY= XXXX
      - WIREGUARD_ADDRESSES=10.xx/32
      - SERVER_CITIES=stockholm,gothenburg,amsterdam,oslo,zurich
      #- SERVER_HOSTNAMES=se13-wireguard,se14-wireguard,se26-wireguard,se28-wireguard,se2-wireguard,se6-wireguard,se7-wireguard,se8-wireguard
      - OWNED_ONLY=yes
      # Timezone for accurate log times
      - TZ=America/Chicago
    sysctls:
      - net.ipv6.conf.all.disable_ipv6=0

_vpn-gluetun-1_logs.txt
I've attatched logs.

Things I've tried: changing to openvpn mode, running it as a container, changing the citys, changing the settings pre-conf with mullvad. I also tried connecting via wireguard on another machine and it seemed to work.

[qdm12]

I'm happy to let you know everything works as expected 🎉!

Once the VPN connection is established, it tells you healthy and your VPN public ip address.
Also note gluetun doesn't allow any networking outside the VPN so usually as soon as some networking works, it means the VPN connection works.

You can then connect other containers to it or other machines through shadowsocks (see the wiki)

running it as a container

You should definitely run it as a container running in a non-host network (default is bridged network so don't worry). Running it as a binary or host network container would mess up your firewall/ip routing and thus possibly cut off connectivity completely.

[ForestHorns]

XD I've been bangin my head on this thinking it was hanging up at the [ip getter] screen because I couldn't test it in the same container.

Thanks so much for the quick reply!