WireGuard

This is an automated archive.

The original was posted on /r/wireguard by /u/Mr_Viper on 2024-01-11 04:22:10+00:00.

Original Title: Wireguard is running in a docker container on a VM in Proxmox. I'm able to connect to Wireguard on my phone using the QR code, but can't load webpages / internal IP addresses / etc. Issue with Port Forwarding in Proxmox?

Running Proxmox 8.1.3 on a Mini PC. One of the VMs is designated for Wireguard. Here is the docker-compose file for the container I'm running:

services:
  wireguard:
    container_name: wireguard
    image: lscr.io/linuxserver/wireguard:legacy
    restart: unless-stopped
    ports:
      - "51820:51820/udp"
    environment:
      - PUID=222
      - PGID=222
      - UMASK=002
      - TZ=America/New_York
      - SERVERURL=192.168.123.56 #optional 
      - SERVERPORT=51820 #optional
      - PEERS=phone,surfacego,macbook #optional 
      - PEERDNS=auto #optional
      - INTERNAL_SUBNET=10.13.13.0 #optional
      - ALLOWEDIPS=0.0.0.0/0, ::0/0 #optional
      - PERSISTENTKEEPALIVE_PEERS= #optional
      - LOG_CONFS=true #optional
    volumes:
      - wireguard-config:/config
      - /lib/modules:/lib/modules
    cap_add:
      - SYS_MODULE 
      - NET_ADMIN
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1

I have port forwarding set up on my Google Home app, UDP, pointing to my mini PC's IP, with the default 51820 port.

I can scan the QR code with my phone and connect to Wireguard, but I'm unable to even navigate to a website, let alone access any internal network IPs.

Is there some additional port forwarding settings I need to change in Proxmox so that the 51820 port specifically points to my Wireguard VM, then into the Wireguard docker container?

I'm just about at the edge of my experience with this stuff 😓 so any advice would be appreciated. I'll answer any questions about the stuff I clunkily explained above.