WireGuard interface failed to come 'up', exit code is '1'

TestUserPlsIgnore commented 1 year ago

I'm trying to setup arch-qbittorrentvpn as part of a docker-compose on my Synology NAS, and am receiving this error:

2023-01-19 16:00:24,279 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2023-01-19 16:00:24,297 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2023-01-19 16:00:24,304 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2023-01-19 16:00:24,307 DEBG 'start-script' stderr output:
RTNETLINK answers: Operation not supported

2023-01-19 16:00:24,311 DEBG 'start-script' stderr output:
Unable to access interface: Protocol not supported

2023-01-19 16:00:24,312 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0

2023-01-19 16:00:24,316 DEBG 'start-script' stderr output:
Cannot find device "wg0"

2023-01-19 16:00:24,316 DEBG 'start-script' stdout output:
[warn] WireGuard interface failed to come 'up', exit code is '1'

According to the FAQs:

This indicates that you are not running the container with 'Privileged' mode enabled and/or sysctl for src_valid_mark (both of which are requirements for wireguard).

However, I have confirmed that the container meets both of these requirements.

qbittorrent-vpn:
    image: binhex/arch-qbittorrentvpn
    container_name: qbittorrent-vpn
    privileged: true
    restart: unless-stopped
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - VPN_ENABLED=yes
      - VPN_USER=${PIA_USER}
      - VPN_PASS=${PIA_PASS}
      - VPN_PROV=pia
      - VPN_CLIENT=wireguard
      - LAN_NETWORK=${LAN_NETWORK}
      - WEBUI_PORT=8080
      - STRICT_PORT_FORWARD=no
      - DEBUG=true
    volumes:
      - ${DOCKER_APPDATA_DIR}/qbittorrent-vpn:/config
      - ${DOCKER_STORAGE_DIR}/Downloads:/data
    ports:
      - 8080:8080
      - 6881:6881
      - 6881:6881/udp
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1

Any suggestions?

Floki-78 commented 1 year ago

Same problem.

binhex commented 1 year ago

most probably missing kernel headers:- https://stackoverflow.com/questions/62356581/wireguard-vpn-how-to-fix-operation-not-supported-if-it-worked-before

Bmartin3k commented 1 year ago

I don't know if there is another link to the missing kernel headers, but I'm running into this same issue

binhex / arch-qbittorrentvpn

WireGuard interface failed to come 'up', exit code is '1' #160