Leaderboard

Its been 10 years and still going strong.

I'm close behind... JOINED 05/03/2015

Fight me. Actually, now that I think about it, I wanted to write something titled 10 years of AirVPN – A humble review a year ago going into all the experiences I've had with AirVPN in all those years but, wow, talk about a colossal task. It's a massive undertaking at this point and I am not sure whether it'll ever see the light of day.

Hello! Problem solved. The reason of the problem and why your method works perfectly can be inferred from GlueTun behavior described here: https://airvpn.org/forums/topic/63708-gluetun-port-forwarding-works-for-an-hour/?do=findComment&comment=239350 By changing port you force a new socket on the rebuilt tunnel. Re-starting qBittorrent from scratch or the whole container should fix the issue as well. Please note that you have an additional option for mitigation described in the linked thread that does not require the workaround you implemented, worth a try. Side note, please insert the proper port for qBittorrent on your compose file ports: section and if necessary set properly the FIREWALL_VPN_INPUT_PORTS variable. Ref. https://github.com/qdm12/gluetun-wiki/blob/main/setup/options/firewall.md Kind regards