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
Hi, I have a vpn supporting port forwarding (purevpn) and I have a dockerized qbittorrent instance connecting to openvpn-aio thru socks5. The issue seems that I can get direct incoming connections only via UDP and nothing with TCP. I was using gluetunvpn docker before and after opening the firewall I got incoming connections fully working. With gluetunvpn not supporting socks5 I was connecting with --network=container:gluetunvpn docker option tho. I decided to switch to this because with socks5 updating the VPN container creates less hassles and be fully unattended. So are there some rules that could block incoming TCP connections from VPN to socks5 client? Thanks
The text was updated successfully, but these errors were encountered:
Hi, I have a vpn supporting port forwarding (purevpn) and I have a dockerized qbittorrent instance connecting to openvpn-aio thru socks5. The issue seems that I can get direct incoming connections only via UDP and nothing with TCP. I was using gluetunvpn docker before and after opening the firewall I got incoming connections fully working. With gluetunvpn not supporting socks5 I was connecting with --network=container:gluetunvpn docker option tho. I decided to switch to this because with socks5 updating the VPN container creates less hassles and be fully unattended. So are there some rules that could block incoming TCP connections from VPN to socks5 client? Thanks
The text was updated successfully, but these errors were encountered: