[ERR] Wireguard open failed, operation not supported

[w00dst0ck]

I try to start the container on a synology. But I get only the following looping messages.

/config/hideme.yaml exist /config/CA.pem exist /config/accessToken.txt exist Link: Generated a new wireguard private key Main: [ERR] Wireguard open failed, operation not supported

Any idea what could be meant by Wireguard open failed, operation not supported

[alturismo]

sorry, i dont use a synology so i cant test either.

can you post your docker run command here (without your credentials) to confirm correct setup

[w00dst0ck]

I've used the following docker run.

sudo docker run -d \ --name=wg_hideme_privoxy \ --net=bridge \ --log-opt max-size=10m \ --log-opt max-file=3 \ --privileged=true \ -e TZ="Europe/Berlin" \ -e LOCAL_NET=0.0.0.0/24 \ -e HIDEME_SERVER=pl.hideservers.net \ -e HIDEME_FILE=hideme.yaml \ -e HIDEME_USER=xxxxxxx \ -e HIDEME_PASS=xxxxxxxxxxx \ -p 8080:8080/tcp \ -p 1080:1080/tcp \ -v /volume1/docker/wg_hideme_privoxy/config/:/config:rw \ --cap-add=NET_ADMIN --device /dev/net/tun --dns=8.8.8.8 \ alturismo/wg_hideme_privoxy

If I start a bash in the container, I can request a token with "hide.client.linux token". But the connect results in the error message.

[alturismo]

may try disable the ipv6 just in case (even it should throw a error), thats how my personal extras look like

--cap-add=NET_ADMIN --device /dev/net/tun --sysctl net.ipv6.conf.all.disable_ipv6=0 --dns=1.1.1.1

[w00dst0ck]

Unfortunately this does not work.

Will then search the synology forums for possible causes.

[w00dst0ck]

Adding wireguard kernel modules for Synology fixed my problem. https://github.com/runfalk/synology-wireguard

[alturismo]

Thanks for the Info

[Alena47]

Getting this error:

Link: Generated a new wireguard private key
Main: [ERR] Wireguard open failed, operation not supported

You may forget to run the command as a root after generating access token

sudo ./hide.me connect server-somewhere-in-this-planet.

peace.

[w00dst0ck]

@Alena47 This issue has already been fixed by adding the kernel modules to the Synology. 😉

[w00dst0ck]

Found an updated guide for DSM 7.2 https://www.derekseaman.com/2022/12/using-wireguard-with-your-synology-docker-containers.html