Connection/authentication problems with Transmission

[coaperator]

Client:

• µTorrent
• qBittorrent
• Transmission
• rTorrent
• Deluge

Client Version:
3.00 latest
Operating System:
win x64
Application Version:
2.7.1 latest
Description:

I'm trying to connect to the transmission in the router via the network
how to fix?

[tympanix]

This is most likely due to the fact that Transmission 3 changes the API. We will have to update the Electorrent implementation for this to work.

[ghost]

Same problem with Transmission: 2.94

Doesn't establish a connection. Transmission Remote GUI connects without problems.

[tympanix]

You are right. I tested this with newest Transmission (using linuxserver/transmission docker) without problems. That doesn't explain your scenario though. Can you double check port number, hostname/ip, username, password.

Can you debug this is any way - developer console?

[ghost]

You are right. I tested this with newest Transmission (using linuxserver/transmission docker) without problems. That doesn't explain your scenario though. Can you double check port number, hostname/ip, username, password.

Can you debug this is any way - developer console?

I describe the situation in detail.

Transmission 2.94 is installed on a Zyxel router.
I am currently connecting via Transmission Remote GUI 5.18.0.
I wanted to try Electorrent, downloaded the Windows version (Windows 10, 64).

Connection to Transmission Remote GUI:

Electorrent connection:

I'm not a programmer, so I don't even know what a developer console is, I'm afraid I won't be able to help. Sorry. I just inform you that I could not connect.

[coaperator]

You are right. I tested this with newest Transmission (using linuxserver/transmission docker) without problems. That doesn't explain your scenario though. Can you double check port number, hostname/ip, username, password.

Can you debug this is any way - developer console?

[coaperator]

In the config, for some reason, the address is /gui instead of /transmission/rpc
saving doesn't help, comes back again / gui

[tympanix]

Thanks for debugging @coaperator. You mention /gui but I don't see that in your screenshot. Can you elaborate what you mean?

[coaperator]

Thanks for debugging @coaperator. You mention /gui but I don't see that in your screenshot. Can you elaborate what you mean?

not at all )

I managed with great difficulty, by workarounds, to go into the settings management, after adding the settings of the first connection
during the first setup I specified /transmission/rpc
but after that if you open the settings, then we are in the path field - /gui is written, and updating this setting does not help fix the problem
if I understand correctly, there should be /transmission/rpc ?

[tympanix]

The issue with /gui is odd but actually due to the fact that you have µTorrent selected in your screenshot and not Transmission.

I've been able to solve the problem by looking at your previous screenshot of the developer console 🥳

[coaperator]

The issue with /gui is odd but actually due to the fact that you have µTorrent selected in your screenshot and not Transmission.

I've been able to solve the problem by looking at your previous screenshot of the developer console 🥳

where can I download a test version for verification?

Transmission also has /gui

[tympanix]

I am currently working on a new release which will include a couple of fixes. You'll see the commit linked in this thread when published