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
{{ message }}
This repository has been archived by the owner on Jul 16, 2023. It is now read-only.
I want to switch over to this from Transmission (to support indexer specific seeding times) but I have one hesitation:
Does this support changing the listening port in preferences to whatever port your VPN uses? I use PIA, and can have a random port that is forwarded to me, so I want to know if this will support a changing port.
Thanks
The text was updated successfully, but these errors were encountered:
Austin-2
changed the title
Does this Container support switching VPN port to Qbittorrent
Does this Container support switching listening port to VPN forwarded port?
May 1, 2023
Hi. I’m in the exact same situation as OP. Also considering the switch. Is this feature of switching to the open port automatic? Or does this need to be manually defined at each reconnection to the VPN?
How does this work for you now in Transmission? I would imagine you'd need some custom scripting to get the port via PIA's API if they give you a different one each re-connect. If you have that set up in Transmission you can likely use their script to get the port and place it in the Qbittorrent config file whenever the container restarts.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I want to switch over to this from Transmission (to support indexer specific seeding times) but I have one hesitation:
Does this support changing the listening port in preferences to whatever port your VPN uses? I use PIA, and can have a random port that is forwarded to me, so I want to know if this will support a changing port.
Thanks
The text was updated successfully, but these errors were encountered: