search

DyonR / docker-Jackettvpn

Docker container which runs a headless Jackett Server with an optional WireGuard or OpenVPN connection
https://hub.docker.com/r/dyonr/jackettvpn/
GNU General Public License v3.0
68 stars 32 forks source link

Failed to initialize nft: Protocol not supported #57

Open StormPooper opened 2 years ago

StormPooper commented 2 years ago

I've started getting iptables/1.8.7 Failed to initialize nft: Protocol not supported on startup, with very little else in the logs. Here's a sample from my latest restart:

2021-09-06 08:00:20.811036 [INFO] VPN_ENABLED defined as 'yes'
,iptables/1.8.7 Failed to initialize nft: Protocol not supported
,2021-09-06 08:00:25.624520 [INFO] VPN_ENABLED defined as 'yes'
,iptables/1.8.7 Failed to initialize nft: Protocol not supported
,2021-09-06 08:00:29.238846 [INFO] VPN_ENABLED defined as 'yes'
,iptables/1.8.7 Failed to initialize nft: Protocol not supported
,2021-09-06 08:00:33.125253 [INFO] VPN_ENABLED defined as 'yes'
,iptables/1.8.7 Failed to initialize nft: Protocol not supported
,2021-09-06 08:00:37.100198 [INFO] VPN_ENABLED defined as 'yes'
,iptables/1.8.7 Failed to initialize nft: Protocol not supported
,2021-09-06 08:00:41.715256 [INFO] VPN_ENABLED defined as 'yes'
,iptables/1.8.7 Failed to initialize nft: Protocol not supported
,2021-09-06 08:00:47.897188 [INFO] VPN_ENABLED defined as 'yes'
,iptables/1.8.7 Failed to initialize nft: Protocol not supported

I've tried setting LEGACY_IPTABLES and using buster but it has made no difference. I'm running it on Synology 6.2 and have had no issues until Watchtower updated the image last night.

StormPooper commented 2 years ago

Just tested alex171's image from https://github.com/DyonR/docker-Jackettvpn/issues/52#issuecomment-901952287 and that is working for me.

sorcierwax commented 2 years ago

Exactly the same here. Synology 6.2, tried LEGACY_IPTABLES and the buster tag with no success. alex171 image works well, thx for the tip StormPooper.

StormPooper commented 2 years ago

Updated to Synology DSM v7 and I was able to switch back to latest (though I had to use the workaround in https://github.com/haugene/docker-transmission-openvpn/issues/1839#issuecomment-876932700) as per #55.

sorcierwax commented 2 years ago

Good for you ! And too bad for me, my synology does not support DSM 7. I'm still on alex171 v0.18.636 (the last one give the same error)

theyogendraDanwar commented 2 years ago

@StormPooper are you using alex171 latest branch or this repo latest ??

StormPooper commented 2 years ago

@theyogendraDanwar on 6.2 I was using axex171's latest image, I was able to switch back to DyonR's latest on 7.

theyogendraDanwar commented 2 years ago

@StormPooper webui is not reachable when tried with latest image. Can you tell me setup which you did to get it working

sorcierwax commented 2 years ago

For those who can't update their NAS to DSM7, I too have created a repo with an image that is working on 6.2. I'll try to update it as frequently as I can. https://hub.docker.com/r/waxou/jackettvpn

raz0rbl4de commented 2 years ago

Had the same problem on Synology DSM.

Changing the command of the docker-compose.yml from "/bin/bash /etc/openvpn/start.sh'" to "bash -c 'apt-get -y update && apt-get -y install iptables arptables ebtables && update-alternatives --set iptables /usr/sbin/iptables-legacy && update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy && update-alternatives --set arptables /usr/sbin/arptables-legacy && update-alternatives --set ebtables /usr/sbin/ebtables-legacy && /bin/bash /etc/openvpn/start.sh'" fixed it.

This forces the container to use the legacy iptables instead of nftables. Don't know if this is the most elegant way of fixing this, but it does the trick!