Dodgexander

Running round in circles here. Does anyone have any advice on how to reliably test port forwarding? I've been used to testing via websites like (yougetsignal.com) but the tests are never successful on my Windows machine. On the box running qbitorrentvpn the client also is not indicating a correctly fowarded port. I use wevpn and their support are claiming port forwarding is working fine for them when testing, but all my clients I've tested it doesn't work. I even tried a port foward outside the VPN to check if it was the router, but that works fine.

My bad with my previous query btw. It's now fixed in the latest version. I had assumed the container was auto updating on a restart. It turns out the only way to update for me was defining the newest version number. To pull the newest image I had to define the actual version :number tag though. Any reason why the tag for :latest isn't pulling the latest image?

I seem to have this problem now even though it was previously found and fixed. It started by privoxy falling only fetching manual search results in Sonarr. Now after attempting to fix it privoxy isn't working at all despite the logs saying it started. I've tried using privoxy on a different port which didn't help, I've also deleted the privoxy config folder and even recreated the container from scratch. One thing I did notice was beforehand the last entry in my log always indicated privoxy was running. Now it's no longer the last entry.. Perhaps it's being started too soon?