WebUI not accessable if VPN is enabled

[squeaky369]

Howdy, before you get out the pitchforks for this issue, it's not what you think it is (at least I hope).

Running instance on docker.

Everything was working great (could access UI, downloads were working just fine, etc), until this morning, I got a notification from Radarr that it couldn't reach qBittorrent. I went to log into the webui, and it timed out. I can still ping it though from the network and docker.

I restarted it, same result. No real errors in the logs. If I change the config and change VPN to 'no', it works just fine. I can log in and see the UI just fine.

I replaced the openvpn file with a new one (generated from PIA), booted back up with the flag for VPN set to 'yes', and same thing. Can't access the UI.

Sat Sep 10 21:40:02 2022 Initialization Sequence Completed

2022-09-10 21:40:06.688817 [info] WebUI port defined as 

2022-09-10 21:40:06.713994 [info] LAN Network defined as 192.168.1.0/24

2022-09-10 21:40:06.738463 [info] Default gateway defined as 172.18.0.1

2022-09-10 21:40:06.763186 [info] ip route defined as follows...

--------------------

0.0.0.0/1 via 10.35.110.1 dev tun0 

default via 172.18.0.1 dev eth0 

10.35.110.0/24 dev tun0 proto kernel scope link src 10.35.110.26 

128.0.0.0/1 via 10.35.110.1 dev tun0 

172.18.0.0/16 dev eth0 proto kernel scope link src 172.18.0.4 

181.214.165.133 via 172.18.0.1 dev eth0 

192.168.1.0/24 via 172.18.0.1 dev eth0 

--------------------

2022-09-10 21:40:06.810143 [info] Docker network defined as 172.18.0.0/16

2022-09-10 21:40:06.860156 [info] iptables defined as follows...

--------------------

-P INPUT DROP

-P FORWARD ACCEPT

-P OUTPUT DROP

-A INPUT -i tun0 -j ACCEPT

-A INPUT -s 172.18.0.0/16 -d 172.18.0.0/16 -j ACCEPT

-A INPUT -i eth0 -p udp -m udp --sport 1197 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --sport 8080 -j ACCEPT

-A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 8999 -j ACCEPT

-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT

-A INPUT -i lo -j ACCEPT

-A OUTPUT -o tun0 -j ACCEPT

-A OUTPUT -s 172.18.0.0/16 -d 172.18.0.0/16 -j ACCEPT

-A OUTPUT -o eth0 -p udp -m udp --dport 1197 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT

-A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 8999 -j ACCEPT

-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT

-A OUTPUT -o lo -j ACCEPT

--------------------

Adding 1000 group

groupadd: group 'qbittorent' already exists

Adding 1000 user

useradd: user 'qbittorent' already exists

2022-09-10 21:40:06.987011 [warn] UMASK not defined (via -e UMASK), defaulting to '002'

2022-09-10 21:40:07.008247 [info] Starting qBittorrent daemon...

Logging to /config/qBittorrent/data/logs/qbittorrent-daemon.log.

2022-09-10 21:40:08.045056 [info] Started qBittorrent daemon successfully...

2022-09-10 21:40:08.103847 [info] qBittorrent PID: 181

Sat Sep 10 21:40:31 2022 AEAD Decrypt error: bad packet ID (may be a replay): [ #8390 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings`

If I don't stop the container right away, I do get about 100,000 of those 'Decrypt Errors', but I checked that out and I had read that that wasn't really an issue.

After looking at the log, I do know that it says WebUI port defined as and it's blank, but the configuration file is showing that it's there.

Config File - https://pastebin.com/WQTZS6FN

The only thing I haven't tried is to re-deploy the container from scratch. I'll probably do that while I'm waiting for someone to tell me I did something wrong.

[2ndwonder]

I have the same issue.. very annoying

[william1509]

Same issue here

[wiltified]

Also having this issue with NordVPN

[pulpocaminante]

Same issue

[ozdeadmeat]

Same issue here with PureVPN

Out of curiousity what is everyones LAN_NETWORK set to? I have my container machine in a DMZ which is a different IP address range to the PC I am trying to connect to it.

[Kylar514]

ever find a solution to this issue?

[dobage]

Same issue here