ELI5 Wireguard setup?

General
1

I know this is long shot, but could someone ELI5 how to setup Wiregard LSIO container?

2

it will help if you clearly explain what part of the readme you did not understand.

1 Like
3

I am noob, so I am wondering if I install Wiregard, I can access my server like I am home, right?

Second, I already have several containers installed behind ngix like airsonic.mydomain.duckdns.org. Will I loose them, i.d. did Wiregard conflict with swag

I shell try it anyway, but I am scared to destroy something in already working containers.

Noob as I said :slight_smile:

4

wireguard is just a vpn, nothing special to it. it won’t prevent access to anything unless you configure it to do so. by default, barring host issues, it will give you access to your home server as if you were at home. iirc the default config will make all your connections appear as if you were at home (including the internet)

1 Like
5

Thanks. I am just installing it.

6

I can’t open WG interface locally

192.168.100.150:51820 Can’t connect

My docker-compose.yml

---
services:
  wireguard:
    image: lscr.io/linuxserver/wireguard:latest
    container_name: wireguard
    cap_add:
      - NET_ADMIN
      - SYS_MODULE #optional
    environment:
      - PUID=1001
      - PGID=1001
      - TZ=Berlin
      - SERVERURL=auto #optional
      - SERVERPORT=51820 #optional
      - PEERS=3 #optional
      - PEERDNS=auto #optional
      - INTERNAL_SUBNET=10.13.13.0 #optional
      - ALLOWEDIPS=0.0.0.0/0 #optional
      - PERSISTENTKEEPALIVE_PEERS=all #optional
      - LOG_CONFS=true #optional
    volumes:
      - /srv/appdata/wireguard/config:/config
      - /lib/modules:/lib/modules #optional
    ports:
      - 51820:51820/udp
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
    restart: unless-stopped
7

provide container logs, ensure you are off wifi when you test, ensure you dnat 51820 from your router to your docker host (and specify udp)

8 
[migrations] started
[migrations] no migrations found
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support the app dev(s) visit:
WireGuard: https://www.wireguard.com/donations/

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1001
User GID:    1001
───────────────────────────────────────

Uname info: Linux 7d81e09ba3e2 4.19.0-26-amd64 #1 SMP Debian 4.19.304-1 (2024-01-09) x86_64 GNU/Linux
RTNETLINK answers: Not supported
**** The wireguard module is not active. If you believe that your kernel should have wireguard support already, make sure that it is activated via modprobe! ****
****  If you have an old kernel without wireguard support built-in, you can try using the legacy tag for this image to compile the modules from scratch.   ****

Debian GNU/Linux 10 (buster)