transmission - torrent and download widget problems
I have transmission(the openvpn version) running in a container. I have homarr running as a container on the same server and uses the same docker network as transmission. I have added the transmission integration with the login credentials in homarr.
I am unable to get the torrent and download speed widgets working. I tried adding the WHITELIST env as well to transmission's docker-compose.yml as described in https://discord.com/channels/972958686051962910/1164678043760078909/1167802214383886396. But this has had no affect.
The logs in homarr only show
Error communicating with your download client 'Transmission' (024aa851-8de8-4824-9c0b-00e41df02b53): HTTPError: Response code 405 (Method Not Allowed), which I think is related to the ping.
Any ideas?Discord
Discord - A New Way to Chat with Friends & Communities
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
18 Replies
Do you have pings activated? If you do then you can check if the ping code is the same as the error by hovering the green/red bubble.
If you don't then it can't be related to pings.
I do have them active
It shows
Online 401Then the code is different, which means the error purely regards the integration part
Now I have to admit, 405 is a new one for me
WARN 1 download clients failed. Please check your configuration and the above log
ERROR Error communicating with your download client 'Transmission' (024aa851-8de8-4824-9c0b-00e41df02b53): HTTPError: Response code 405 (Method Not Allowed)
These message keep repeating the docker logs for homarrAre you using https instead of http?
Nope, http. The services are not exposed externally.
Great the only one with that error straight up abandoned transmission so no info on that x)
🙂
Just to confirm, homarr and transmission run on the same machine right?
Yea, same machine and are on the same docker network
have you done the docker integration?
Yea, I have
And adding transmission from the docker integration page doesn't work?
The internal address has a high chance to be different from the external one, and the docker integration facilitates making sure you're using the right IP
Solution
Ok, I add it again via the docker integration and now it works
Not sure what happend
lol
ok, it works now. Looks good.
Thanks
Great :)