temelj
commented
2 years ago before you ask - I set VPN_ENABLED: false and it starts up and I can get to the web ui :)
Open temelj opened 2 years ago
temelj
commented
2 years ago before you ask - I set VPN_ENABLED: false and it starts up and I can get to the web ui :)
DyonR
commented
2 years ago Sorry for the late reply.
I think this may be caused that your wg0.conf has some IPv6 config in it.
If I look at this section of the log;
qbittorrent_1 | 2021-11-25 05:44:49.074876 [INFO] Starting WireGuard...
qbittorrent_1 | Warning: `/config/wireguard/wg0.conf' is world accessible
qbittorrent_1 | [#] ip link add wg0 type wireguard
qbittorrent_1 | [#] wg setconf wg0 /dev/fd/63
qbittorrent_1 | [#] ip -4 address add 10.34.42.31/16 dev wg0
qbittorrent_1 | [#] ip link set mtu 1420 up dev wg0
qbittorrent_1 | [#] resolvconf -a wg0 -m 0 -x
qbittorrent_1 | [#] wg set wg0 fwmark 51820
qbittorrent_1 | [#] ip -6 route add ::/0 dev wg0 table 51820
qbittorrent_1 | Error: IPv6 is disabled on nexthop device.
qbittorrent_1 | [#] resolvconf -d wg0 -f
qbittorrent_1 | [#] ip link delete dev wg0It throws the error qbittorrent_1 | Error: IPv6 is disabled on nexthop device..
I did share my wg0.conf here; https://github.com/DyonR/docker-qbittorrentvpn/issues/78#issuecomment-988023106
Could you maybe remove all IPv6 related stuff from your wg0.conf to see if that fixes your problem, if you still need to get this working.
Gartonious
commented
2 years ago I am also getting the same warning error where it is saying "work accessible". I don't have the ipv6 issue but it does say the following - please can you help?
2022-01-03 03:26:26.983095 [INFO] VPN_ENABLED defined as 'yes'
2022-01-03 03:26:27.059942 [INFO] The container is currently running iptables v1.8.7 (nf_tables).
2022-01-03 03:26:27.131550 [INFO] LEGACY_IPTABLES is set to ''
2022-01-03 03:26:27.207662 [INFO] Not making any changes to iptables version
2022-01-03 03:26:27.282396 [INFO] VPN_TYPE defined as 'wireguard'
2022-01-03 03:26:27.365436 [INFO] WireGuard config file is found at /config/wireguard/wg0.conf
dos2unix: converting file /config/wireguard/wg0.conf to Unix format...
2022-01-03 03:26:27.449508 [INFO] VPN remote line defined as 'VPNIP:51820'
2022-01-03 03:26:27.525270 [INFO] VPN_REMOTE defined as 'VPNIP'
2022-01-03 03:26:27.602280 [INFO] VPN_PORT defined as '51820'
2022-01-03 03:26:27.674544 [INFO] VPN_PROTOCOL set as 'udp', since WireGuard is always udp.
2022-01-03 03:26:27.747982 [INFO] VPN_DEVICE_TYPE set as 'wg0', since WireGuard will always be wg0.
2022-01-03 03:26:27.825230 [INFO] LAN_NETWORK defined as '192.168.0.100'
2022-01-03 03:26:27.900896 [INFO] NAME_SERVERS defined as '1.1.1.1,1.0.0.1'
2022-01-03 03:26:27.977833 [INFO] Adding 1.1.1.1 to resolv.conf
2022-01-03 03:26:28.054458 [INFO] Adding 1.0.0.1 to resolv.conf
2022-01-03 03:26:28.127709 [INFO] Starting WireGuard...
Warning: `/config/wireguard/wg0.conf' is world accessible
[#] ip link add wg0 type wireguard
RTNETLINK answers: Operation not supported
Unable to access interface: Protocol not supported
[#] ip link delete dev wg0Are you running the container privilleged?
And 'world accessible' is just a warning about the permissions on the file, which doesn't matter really
Gartonious
commented
2 years ago Are you running the container privilleged? And 'world accessible' is just a warning about the permissions on the file, which doesn't matter really
Yes I am running as privileged - this is my settings (example, not showing real MAC / IPs)
docker run --privileged -d \
--name=qBittorrent-VPN \
-v /volume1/docker/qbittorrent-vpn:/config \
-v /volume1/Downloads:/downloads \
-e "VPN_ENABLED=yes" \
-e "VPN_TYPE=wireguard" \
-e "WEBUI_PORT_ENV=8080" \
-e "INCOMING_PORT_ENV=8999" \
-e "LAN_NETWORK=192.168.0.100" \
-e "NAME_SERVERS=1.1.1.1,1.0.0.1" \
-e PUID=1000 \
-e PGID=100 \
-e UMASK=100 \
-e TZ=Europe/London \
-p 8080:8080 \
-p 8999:8999 \
-p 8999:8999/udp \
--network LAN2 \
--ip "192.168.0.100" \
--hostname "qbittorrent" \
--mac-address "00:00:00:00:00:00" \
--restart unless-stopped \
dyonr/qbittorrentvpn:latest@Gartonious does the kernel of your host support WireGuard? What system do you use? What is your kernel version?
Gartonious
commented
2 years ago @Gartonious does the kernel of your host support WireGuard? What system do you use? What is your kernel version?
Yeah so i've installed Docker on my Synology NAS - within docker I have GlueTun running in there too which I have managed to get the WireGuard Connection working perfectly in there without any issues - with theirs you have to define the WireGuard in your ENV's like below:
Edit - just to add too, with or without GlueTun running, qbittorrentvpn does not work
-e VPNSP=custom -e VPN_TYPE=wireguard \
-e WIREGUARD_ENDPOINT_IP=[VPNIP] \
-e WIREGUARD_ENDPOINT_PORT=51820 \
-e WIREGUARD_PUBLIC_KEY=[Public Key] \
-e WIREGUARD_PRIVATE_KEY=[Private Key] \
-e WIREGUARD_PRESHARED_KEY=[Pre Key] \
-e WIREGUARD_ADDRESS="10.10.10.10/32" \But the data is basically the same in the wg0.conf file, except it has a couple more things in there from the provider. Even with taking them out it does not work. My Config file (wg0.conf) is below:
[Interface]
PrivateKey = [KEY]
ListenPort = 51820
Address = [IP Address]/32
DNS = [IP Address]
[Peer]
PublicKey = [KEY]
PresharedKey = [KEY]
AllowedIPs = 0.0.0.0/0
Endpoint = [IP Address]:51820
PersistentKeepalive = 25Version Details: DSM - 7.0.1-42218 Docker - 20.10.3-1239 VPN Providers - vpn unlimited and fastest vpn (could try either but its vpn unlimited i'm trying to get working with WireGuard)
The reason behind using WireGuard is because OpenVPN would not work either with my provider but I am not sure if this is because they use certificates. qmcgaw/GlueTun has native support for my providers though I have only managed to get vpnunlimited working via the build in VPN. After I discovered WireGuard is the newer VPN type which is taking over from OpenVPN / more stable connection, I connected via that just fine on GlueTun using the custom lines above and was hoping this would just work on dyonr/qbittorrentvpn too using the config file but it did not.
Also what is strange, I have just changed the access rights of the wg0.conf file to Octal 0600 (as suggested to get rid of that error on another forum) and when I start the container back up, it seems to reset it back to 0775. (also gives the same is world accessible error message in the logs).
I have also set my PUID to my local administrator account on the NAS and also the PGID and UMASK id is both for admin so it should have full rights there too.
I am running out of ideas but ideally I want to get rid of GlueTun and use your dyonr/qbittorrentvpn instead. I did try getting the standard version of qbittorrent working with GlueTun - managed to get to the web interface and everything but just can't download anything - seems the listening port is not forwarding to the VPN using the sharing the GlueTun container method but just want to have the one container ideally like yours. Once ive got this working, I would like to get Jacket working too but one thing at a time.
To be honest with you what would be good in a future build would be to have all the GlueTun supported VPN providers imported into your build (sure they imported theirs from somewhere else too) so you can just select the provider, enter your username and password for OpenVPN or select to use WireGuard where it asks for the same details like theirs uses as that seems to work? - I would love to try help you merge theses together but I would not know where to start as I am only just getting my head around docker :(
EDIT - JackettVPN is also doing the same thing - says
2022-01-03 19:18:03.799241 [INFO] Starting WireGuard...
Warning: `/config/wireguard/wg0.conf' is world accessible
[#] ip link add wg0 type wireguard
RTNETLINK answers: Operation not supported
Unable to access interface: Protocol not supported
[#] ip link delete dev wg0
Cannot find device "wg0"Does it not have access to the NICS? Has it not created it maybe?
Gartonious
commented
2 years ago Don't suppose there is any update to this is there? I don't mind providing my VPN config if you would like to test it yourself? :)
vcfxb
commented
2 years ago https://www.ivpn.net/knowledgebase/linux/linux-wireguard-rtnetlink-answers-operation-not-supported/
looks like your host device may not have wireguard drivers
Gartonious
commented
2 years ago https://www.ivpn.net/knowledgebase/linux/linux-wireguard-rtnetlink-answers-operation-not-supported/
looks like your host device may not have wireguard drivers
would have thought this container would have already contained wireguard?
Using docker-compose
output