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
I can connect to PIA via Wireguard and get a forwarded port. All my other containers (aar, Webtop, etc.) can connect to the internet and are getting the PIA IP. When I add in the PIA forwarded port into qBittorrrent all of the trackers are listed as unreachable/not working. qBittorrent did work previously with glueton and OpenVPN. Docker composer for PIA and qBittorrent are as follows.
Is qBittorrent bound to the wireguard interface wg0? That's one thing that comes to mind that I vaguely recall being an issue in the past. IIRC it uses all network interfaces by default, and outgoing internet connections (eg. tracker/peers) on the non-wireguard interface/s would likely fail.
I can connect to PIA via Wireguard and get a forwarded port. All my other containers (aar, Webtop, etc.) can connect to the internet and are getting the PIA IP. When I add in the PIA forwarded port into qBittorrrent all of the trackers are listed as unreachable/not working. qBittorrent did work previously with glueton and OpenVPN. Docker composer for PIA and qBittorrent are as follows.
Thoughts?
The text was updated successfully, but these errors were encountered: