Fl4shBack

It's because the iptables packages changed names recently in arch and the new push from binhex "merged" those changes in the docker image https://archlinux.org/news/iptables-now-defaults-to-the-nft-backend/ iptables-nft became iptables iptables became iptables-legacy

Had to make a script that does this on my QNAP: #!/bin/bash yes|pacman -S iptables-legacy mv /usr/bin/nft /usr/bin/nft.disabled 2>/dev/null || trueBut also had to change the container command in docker-compose to this because the ENABLE_STARTUP_SCRIPTS hook runs after the VPN/iptables setup: command: ["/bin/bash", "-c", "/config/scripts/iptables-legacy.sh && init.sh"]

I started experiencing this last week. If you're using pihole and hagezi's DoH/VPN/TOR/Proxy Bypass lists, they recently pushed an update that blocked a whole lot of VPN domains. Whitelisting them solved the issue for me.

Awesome ! Thanks a lot ! Didn't think it was possible, I should have tried

Hi binhex ! First I'd like to thank you for your awesome container. Seriously, I've been using it for almost 2 years and it never failed me ! I'd like to ask you if it is possible to add a second "lan" network in the iptables via the environment variables or something. When I'm home I don't have any issues connecting to deluge web or the gui. To connect remotely when I'm not home, I have a VPN set up on a my NAS but the ip it gives to my client is not in the range of my "normal lan" and I have no way to change that. So of course I'm unable to access deluge. Do you have any idea on how I could alter the setup to make It work ? Ideally I'd like to add the ip range of my local vpn to the container but I don't think I can add 2 "lan" networks with the env. vars. Thank you again, for the container and for your time !

@raf7913 I’m having the exact same issue with my qnap for a month or so. I suspect it has to do with the latest qnap firmware updates (2 or 3 last versions). Haven’t been able to fix it yet. Seems to go temporarily when restarting the nas though.

Hi erveryone ! I have been running this container for a few months without any issue. But since last week, I have a lot of python errors in my log files and the VPN tunnel seems highly instable (it seems like it fails to connect about 90% of the time). OpenSSH seems to be crashing non stop and the python errors seems to happen when updating deluge ip/ports. Tried to recreate the container, the image is up to date and tried to change vpn endpoint without any success. Does anyone have any idea of what could be happening there ? Thank you very much for your time and assistance in this matter Fl4shBack supervisord.log [EDIT] Python and curl errors seems to be gone after rebooting the NAS but they come back after some time...