Error when using with Transmission that has user authentication setup

[Baenwort]

So I get an error while trying to bind the port forwarding.

I think this is due to using a user and password for authentication on my transmission setup.

With the old port-forward.sh I would add a:
transUser="username" and transPass="password"

as a variable and then append --auth "${transUser}":"${transPass}" after any call of the transmission-remote.

Will this work with your script if I put them in the refresh_pia_port.sh? This seems like the logical place considering how you explain your binding process.

[Baenwort]

So I did as I mentioned and the transmission GUI is showing the right port in the settings but I get the following error that terminates your script:

[Baenwort]

Found the reason for the bind failing. I had missed converting a /pia/ into a /manual-connections in the refresh_pia_port.sh so if someone else runs into this problem that is the solution.

It might be useful to include in your instructions the changes to be made if one is using password authentication for transmission.

[glorious1]

I know it's been a long time, but I didn't get notice of these messages. Could you help me understand what changes had to be made so that password authentication will work?

I only see one reference to /pia/ in refresh_pia_port.sh. I changed the script directory to that name because it's easier.

[Baenwort]

So I added a pair of variables that I hardcoded my transmission local login information. It would likely be better to pass it as a file similar to how the PIA authentication details are passed into the script.

Once I had the Transmission credentials I was able to add --auth "${transUser}":"${transPass}" to any use of transmission-remote in the script and it would enable this script to work with a transmission instance that was password controlled.

When I have time again in September to swing around to this project I'll try developing such a patch if you haven't done so before then.

[glorious1]

Baenwort, Actually, you are WAY better at this stuff than I am. I was just struggling to port the scripts to FreeBSD. When you get back to it, maybe you want to consider taking over this repository? Best wishes, Jim

…

On Jun 1, 2021, at 6:20 PM, Baenwort ***@***.***> wrote: So I added a pair of variables that I hardcoded my transmission local login information. It would likely be better to pass it as a file similar to how the PIA authentication details are passed into the script. Once I had the Transmission credentials I was able to add --auth "${transUser}":"${transPass}" to any use of transmission-remote in the script and it would enable this script to work with a transmission instance that was password controlled. When I have time again in September to swing around to this project I'll try developing such a patch if you haven't done so before then. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABNZ5QNAK2YXAF2JCK4IKZTTQWBMNANCNFSM4T6JJB7A>.