Axelfony

Thanks @MisterLas - downgrade worked. Also the suggestion of Binhex did the trick for 4.6! You can also give it a try. @binhex Thanks for the hint! Process started again and the initial credentials were working.

That is correct! Both are set to 8080, as you can see from the docker screen, here also the container config: From my logs when it worked, I got the message that the process has started listening on port 8080: 2023-05-21 04:41:48,976 DEBG 'watchdog-script' stdout output: [info] qBittorrent process started [info] Waiting for qBittorrent process to start listening on port 8080... 2023-05-21 04:41:49,198 DEBG 'watchdog-script' stdout output: [info] qBittorrent process listening on port 8080 2023-05-21 04:41:49,201 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2023-05-21 04:41:50,209 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2023-05-21 04:41:50,214 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 But this does not happen now, he is somehow stuck at: [info] Waiting for qBittorrent process to start listening on port 8080... Do you know of any additional possibilities/options to check, why the process does not start listening besides enabling debug function?

That is correct Sir. Machine is reachable via 192.168.178.2 and according to my understanding 192.168.178.2:8080 should be Bittorrent. Container is configured using bridge network:

Thanks for getting back. See attached. I just compared to when it was working and it seems it is an issue with the port forwarding configuration? With VPN Port being different than qBittorrent incoming port 6881? supervisord_new.log

Hi there, thank you for providing this docker - worked for me flawlessly... until now 😀 Somehow since 2 days I am not able to reach the WebUI anymore and Jackett is also not able to reach privoxy. What I have tried so far: Completely removed the container and re-deployed without VPN and Privoxy - did not fix it Had ProtonVPN with Wireguar set up previously, configured it with the the new option. VPN is able to connect and is able to map ports, but instance still not coming up. Deactivated all other Dockers to avoid a port issue - did not help Important to note is that I did not change the network configuration or the environment. Network should be configured correctly (because it worked before(?)) The instance is stuck here: 2023-10-24 11:22:57,961 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38236' 2023-10-24 11:23:13,687 DEBG 'watchdog-script' stdout output: [info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.2.0.2 different, marking for reconfigure 2023-10-24 11:23:13,691 DEBG 'watchdog-script' stdout output: [info] qBittorrent not running 2023-10-24 11:23:13,691 DEBG 'watchdog-script' stdout output: [info] qBittorrent incoming port 6881 and VPN incoming port 38236 different, marking for reconfigure [info] Removing session lock file (if it exists)... 2023-10-24 11:23:13,708 DEBG 'watchdog-script' stdout output: [info] Attempting to start qBittorrent... 2023-10-24 11:23:13,735 DEBG 'watchdog-script' stdout output: [info] qBittorrent process started [info] Waiting for qBittorrent process to start listening on port 8080...