Transmission 3.00 (Ubuntu 22.04.3) Connection Not Working
I have entered my username and password to configure multiple times. Same credentials work from the Arr apps. My logs show:
```
ERROR Error communicating with your download client 'Transmission' (673): HTTPError: Response code 403 (Forbidden)
WARN 1 download clients failed. Please check your configuration and the above log
ℹ Saving updated configuration of 'default' config.
ℹ Detected credential change of private secret. Value will be overwritten in configuration
ERROR Error communicating with your download client 'Transmission' (673): HTTPError: Response code 403 (Forbidden)
WARN 1 download clients failed. Please check your configuration and the above log
ERROR Error communicating with your download client 'Transmission' (673): HTTPError: Response code 403 (Forbidden)
WARN 1 download clients failed. Please check your configuration and the above log
```
I added 403 to the ping so thats green. But none of the widgets work such as showing speeds, etc.
Solution:Jump to solution
Yo, I'm the guy that posted that other Transmission question, and I found the solution. The problem is that the transmission daemon has a whitelist for IPs that are allowed to access the webUI. When you set up the daemon, you either whitelisted your IP, or you're running it on your local machine and so whitelisting wasn't needed to begin with. Either way, since Homarr runs in a Docker container, you need to whitelist it.
Here's how:
1: Kill the daemon with
sudo killall transmission-daemon...6 Replies
You are the second to post about transmission having this issue. There might be something going on.
https://discord.com/channels/972958686051962910/1163929081910415473
Since you're running v3.00 though, you shouldn't be having a problem that would be introduced in a new version so that's odd
Are you running transmission in docker or the linux package?
Hi, thanks for quick response. Its installed via apt in linux ubuntu jammy. Same as the *Arr apps (per their ubuntu instructions)
We might need to look into it, but it seems our api doesn't support the apt install, whereas the starr apps do
We do recommend to run everything in docker though, as it is more appropriate for homelab applications
I understand. I may just migrate toward everything in docker. Thanks for the quick response!
Solution
Yo, I'm the guy that posted that other Transmission question, and I found the solution. The problem is that the transmission daemon has a whitelist for IPs that are allowed to access the webUI. When you set up the daemon, you either whitelisted your IP, or you're running it on your local machine and so whitelisting wasn't needed to begin with. Either way, since Homarr runs in a Docker container, you need to whitelist it.
Here's how:
1: Kill the daemon with
sudo killall transmission-daemon
2: Find the docker container's ip address by running sudo docker container inspect homarr. It'll most likely be near the bottom under "Networks" -> "bridge" -> "IPAddress" assuming you're running Homarr on the bridge network. You can also easily find it in Portainer if you run that.
3: Open /var/lib/transmission-daemon/info/settings.json in your text editor of choice
4: Under "rpc-whitelist", add the ip address of the docker container in quotes.
5: Restart the transmission daemon with sudo systemctl start transmission-daemon.service and sudo systemctl enable transmission-daemon.service
I hope this helps. Note that the app still shows a 401 error in Homarr, but the torrent integration works perfectly fine.@walksonair You may have already switched to everything in docker but if you haven't