dumbaspl / deluge-windscribe-ephemeral-port Goto Github PK

Would it be possible to add support for transmission to set peer-port?
Either using transmission-remote by installing transmission-cli package and passing the proper command line something like: $ transmission-remote $TRANSMISSION_HOST:$TRANSMISSION_PORT --auth=$TRANSMISSION_USERNAME:$TRANSMISSION_PASSWORD -p $WINDSCRIBE_PORT

You would need to export the Windscribe port found as an environment variable but it would make it easier to add support for other BT clients.

Or another option is through an rpc call to http://host:9091/transmission/rpc

RPC would not require a client but may be a little more to configure than using the transmission-remote client.

Some references: https://www.reddit.com/r/selfhosted/comments/rzzn3q/cronjob_for_updating_transmissions_peerport_to/
https://linux.die.net/man/1/transmission-remote

Thanks!

Hey! I'm currently running Transmission using Haugene's Docker-Transmission container. Since you're redeveloping the entire application according to #7 I was thinking about the handling of port assignments. If the new port is the same one as before, everything should work without further hassle. However if the account is assigned a different port than before, the entire Docker/VPN container has to be restarted (at least from my experience). How do you handle this in your case?

If the reassignment happens before the 7 days the ephemeral port is valid for this will probably be no real problem. If the scheduled time is longer than 7 days it should be possible to mount /var/run/docker.sock and restart the VPN container (possibly even multiple containers, e.g. sonarr,prowlarr,... since docker doesn't restart depending containers) so that the VPN container can pick up the freshly assigned port.

Currently, it seems like logging in with an account that has been set up with 2FA is not possible. Can this be supported or entered manually or through a variable somehow?