How to connect Sonarr to Rutorrent

LSIO Discussion Container Support
,
1

I cannot seem to be able to connect a Sonarr LSIO container to a Rutorrent LSIO container.
I have switched rtorrent/rutorrent from the socket file to the classic localhost:5000 configuration, and have created a bridged network in my docker-compose:

---
version: "2.1"
services:

  rutorrent:
    image: linuxserver/rutorrent
    container_name: rutorrent
    environment:
      - PUID=1000
      - PGID=1000
    volumes:
      - /home/test/docker/rutorrent:/config
      - /home/test/docker/downloads:/downloads
    networks:
      - virtual-lan
    ports:
      - 80:80
      - 5000:5000
      - 51413:51413
      - 6881:6881/udp
    restart: unless-stopped

  sonarr:
    image: linuxserver/sonarr
    container_name: sonarr
    environment:
      - PUID=1000
      - PGID=1000
    networks:
      - virtual-lan
    volumes:
      - /home/test/docker/sonarr:/config
      - /home/test/docker/tv:/tv
      - /home/test/docker/downloads:/downloads
    ports:
      - 8989:8989
    restart: unless-stopped

networks:
   virtual-lan:
     driver: bridge

I cannot seem to be able to connect Sonarr to Rutorrent.
any suggestion?

2

in sonarr, when you add rutorrent and it asks for the host, type rutorrent
not sure why you’re messing with sockets and localhost… this is pretty simple in docker networking

3

that’s what I did.

the issue is that, by default, the docker rutorrent container as packaged by LSIO is configured to exploit a socket file, not the localhost:5000 xmlrpc host/port.
so you cannot just tinker with sonarr without changing the config of both rtorrent/rutorrent first.

then, after having changed the port, I cannot get it to work.
I have networking enabled in my docker-compose application.
(I thought that it was supposed to be working by default, that is, there should be a default network created automatically by docker-compose through which all sub-containers can talk, but I’m not sure it was working without my explicit virtuallan anyhow.)
I specify the name of my container as host, thus rutorrent, I have tried specifying both port 80 (which is the webui for rutorrent) and 5000 (which is the XMLRPC port for rtorrent) and nothing happens.
I have left RPC2 as URL path, but maybe I should change that?

yeah, it’s supposed to be smooth, but, well, it’s not.

4

i dont know what to tell you aside from if this is hard, you’re doing it wrong. :slight_smile:

maybe you should visit us on discord. I have used rutorrent and sonarr without ANY of what you described so i know, for a fact, it works just as i stated :slight_smile:

5

so you are keeping the default rutorrent container configuration?

and then you specify rutorrent as hostname in sonarr, with what port? also, same url path RPC2?

6

you need to set the port to 80 since that is what is used in the container (as shown on github/dockerhub readme), If you change the port (inside the container) you would put that port.

I think you’re just thinking too much on this, our containers are built to be used by people who have no clue what linux is, so they are very plug and play.

for example - fresh install
https://hastebin.com/oqedoxehof.bash

Imgur
Imgur

nothing to it; took me about 10 minutes, i change no configs aside from adding this into sonarr.

7

I might have understood what the problem is. :confused:

I thought I was supposed to be teaching Sonarr to talk to rtorrent (not rutorrent) through its XMLRPC capabilities, thus as I was saying using either the socket file (which is the default config, also, I can’t export it as a volume -> How to export rtorrent socket from container) or as a classic localhost:5000 host/port combo.

instead, your default vanilla configuration is teaching Sonarr to talk to rutorrent through the same localhost:80 host/port combo that the user would type in to get to the WebUI!

in any case, I still cannot get it to work so I guess my docker-compose is wrong.
does my network configuration seem reasonable to you?

8

I’ve recreated from scratch the rutorrent container and it worked.
therefore, for others getting here:

  1. fresh rtorrent/rutorrent container:
    • don’t change the socket/scgi configs;
  2. fresh sonarr container, default values:
    • host: rutorrent
    • port: 80
    • path: RPC2

I think the documentation regarding how to link the two containers should be elaborated a bit better, because I was confused by the way in which I know rutorrent talks to rtorrent.

thank you for your help, @driz.

9

hopefully you don’t take offense, but as you’re the only person I’ve ever seen with an issue here, i imagine our docs are good to go. That said, if you would like to submit a PR adjusting the documentation, readme-vars.yml is where you would do so.

My pleasure, glad you got it sorted out.

10

of course! speak your mind. :jack_o_lantern:

a simple web search for “docker sonarr rutorrent” would show that plenty of people have issues, including while using LSIO images.
maybe the crucial word in your sentence is the word here?
indeed, this forum seems deserted and lots of people ask for help elsewhere, like reddit, sonarr forums, etc. :man_shrugging:

I’m still learning but still, the documentation is supposed to be helping noobs more than power users, isn’t it? :laughing:

anyway, if and when someone wants to, that area could be improved.
thanks :raised_hand_with_fingers_splayed:

11

Most of our support is actually handled via discord, which is why i suggested you pop in there. It’s just… generally much quicker.

I suppose you have a fair point, so like i said, if you can think of a way to make the instructions more clear, please submit a PR.

12

thanks for the suggestion, I know, I tried! but it wants my phone number, and that’s a no-no. :frowning_face:

fair enough. I need more experience, but I’ll definitely try and participate in the communal effort!

13

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.