Transmission giving a 403 (forbidden) error
I'm trying to add the torrent widget, and set up an app with Transmission. I gave it http://IP:PORT in both the internal and external addresses, and gave it the proper credentials. The Transmission daemon is running on the same PC as Homarr (not in a Docker container), and other integrations like Jellyfin and Sonarr work correctly. The torrent widget does not work.
Solution:Jump to solution
I found the solution, I posted it here https://discord.com/channels/972958686051962910/1164678043760078909/1167802214383886396
26 Replies
The ping responding 403 doesn't mean it's not working, it means forbidden. This happens because the ping function doesn't use the credentials.
You can add 403 to your network tab on your app.
As long as the torrent widget and download speed widget work, you're all good.
Unfortunately, the torrent widget doesn't work
It says no suported Torrent clients found
Any errors in your logs?
That error is not from the ping but from the communication with credentials. That means there is something wrong with them
Also, what do you mean "not in a docker container"?
I'm running the native transmission package, not a docker container
Oh so you're running the app, ok
I don't think that should matter since Homarr can see Jellyfin and Sonarr despite those also being native packages, but mentioned it just in case
I'm not sure you can communicate with an app this way, it may be configured differently on the network side since it doesn't require a web interface
That's strange. Sonarr and Radarr don't ask for any more than Homarr does (address, username, password) and yet they work totally fine
With Transmission I mean
Sonarr and radarr also running in docker?
Only thing I can suggest, triple check credentials and make sure that internal address respects "http://ip:port", no trailing slashes or added paths
Nope, both native
Yeah that's a bit of a head scratcher, maybe the api we use to communicate with transmission is different that the one radarr and sonarr uses
Theirs can target the native app while ours can't maybe.
Maybe this is a sign from above to switch torrent clients
Qbit is nice but I think it's a sign to just make it all go on docker
Maybe, but I'd prefer to keep things native where I can tbh
Why?
I'm not judging btw, genuinely interested. Those are apps made for homelabs and containerization.
No problem, it's two main reasons
First, updating everything is much easier, a simple sudo apt update, sudo apt upgrade and it's all done
Second, it's much easier to see what services are running on the server. On Linux, I can easily manipulate running services, list listening ports, etc. But with docker, I need to have the added step of listing my docker containers to see what's running, what's listening etc
Watchtower does that for you. Not even a command to do.
I don't know much about docker as I use kubernetes myself, but I'm pretty sure you can easily do those too in docker
Didn't know this existed. I'll try this out
I'll admit I don't know the first thing about kubernetes.
Maybe I'll move my torrent client to docker. Just for reference, do you recommend a specific client? I liked transmission for its minimalism but maybe there's a better option.
Transmission and qbit are usually the top ones, but as long as you don't go for utorrent you're usually good
Didn't plan on using anything proprietary
Yeah it’s normal, it’s because you’d have to have the url like user @ pass.website.com or something for it to work. We don’t recommend it, instead just add 403 to the accepted codes
Solution
I found the solution, I posted it here https://discord.com/channels/972958686051962910/1164678043760078909/1167802214383886396
Glad you found the problem and thanks for the info, I'll know for the future