You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
qBittorrent: 4.4.2 QT6 x64
Operating system: Windows 10 Enterprise LTSC N 1809 x64
What is the problem?
qB doesn't feel VPN connection on startup - plug is red in status bar no matter if you connect/reconnect the VPN afterwards. VPN connection type is IKEv2. The only method to fix that without restarting qB is to go to advanced settings and change interface to anything else, apply and then select VPN again. Then it will show yellow lightning in status bar and then green plug. Just for info, port forwarding is fine, if it has any effect here.
Steps to reproduce
There's no specific order. But I have automatic startup of qB and automatic VPN connection. VPN connection is started faster, qB needs about 5 minutes to load completely with whole set of torrents (over 20000). I use SQL db of jobs.
Additional context
No response
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered:
qBittorrent & operating system versions
qBittorrent: 4.4.2 QT6 x64
Operating system: Windows 10 Enterprise LTSC N 1809 x64
What is the problem?
qB doesn't feel VPN connection on startup - plug is red in status bar no matter if you connect/reconnect the VPN afterwards. VPN connection type is IKEv2. The only method to fix that without restarting qB is to go to advanced settings and change interface to anything else, apply and then select VPN again. Then it will show yellow lightning in status bar and then green plug. Just for info, port forwarding is fine, if it has any effect here.
Steps to reproduce
There's no specific order. But I have automatic startup of qB and automatic VPN connection. VPN connection is started faster, qB needs about 5 minutes to load completely with whole set of torrents (over 20000). I use SQL db of jobs.
Additional context
No response
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: