I have setup RDT-client, Prowlarr and integrated it into Sonarr to download to my unraid server.

It works, but slowly and I cannot figure out why.

If I download using RDT-client to my UNRAID server, I am getting ≈ 10MB/s, but if I download directly from Real-debrid to the same location on my unraid server I get 100MB/s and I cannot think why one is do much slower that the other.

Any ideas?

I haven't really tried RDT, but like with all torrent clients, it needs an open incoming port to be able to get full speed potential. If you don't have an open incoming port, downloads will be slow. Also, make sure your downloads go to an ssd pool.

24 minutes ago, strike said:

I haven't really tried RDT, but like with all torrent clients, it needs an open incoming port to be able to get full speed potential. If you don't have an open incoming port, downloads will be slow. Also, make sure your downloads go to an ssd pool.

Is it really downloading a torrent though? You're downloading directly from real debrid servers, they download the torrent, you download directly from their server.

Or at least that's the way I understand it.

Besides, if I download from real debrid website I get 100MB/s and RDT gives me 10/MB/s and it is presumably downloading directly from real debrid as well.

9 minutes ago, ridley said:

Is it really downloading a torrent though?

The "T" in RDT stands for Torrent. At least that's what it says here: http://github.com/rogerfar/rdt-client, and like I said, when torrenting, you need an open incoming port to get the most speed. But I haven't tried it, so it might be different, but I doubt it. If it uses the torrent protocol, it should be the same as any other torrent client.

Looks like I was wrong regarding the open port. But it's an open issue here, might have something to do with docker? https://github.com/rogerfar/rdt-client/issues/296