Getting cross-seed working with qpit & gluetun

[moppylinglong]

Hi all,
L:ove the project, have managed to do the basics so far, now installing cross-seed and notifiarr which I previously had setup on a Windows server. I'm having some issues trying to get cross-seed to talk to qbit. Cross-seed (for those who are unaware) scrapes your indexers for files you may have already downloaded from a different tracker to upload to other trackers to improve your ratio without downloading new files.

Part of the config file for cross-seed looks like this:

Code: Select all

torrentClients: ["qbittorrent:http://admin:password@localhost:8081/"]

I understand that I can't keep it as localhost (since I have qbit running behind a VPN via gluetun as per the YAMS installer) but how do I configure this so it can still speak to qbit?

I am very new to all of this, so please do let me know if I'm missing something very simple

[moppylinglong]

As an update I have:

Followed the advice here and added network_mode: "service:gluetun" to the cross-seed config. I have then followed the example here and added the ports used by cross-seed to the gluetun config file.

When I run the cross-seed daemon, I get the error: Attempt 1/6 failed, retrying in 60s: [qbittorrent@gluetun:8081] qBittorrent login failed: fetch failed

I assume the problem is that cross-seed is somehow not on the same network as the remaining containers? If I run

Code: Select all

docker network inspect yams_network

I can see sonarr, watchtower, lidarr, bazarr, gluetun, radarr, portainer & prowlarr there but not qbit or cross-seed (nor notifiarr which I am also trying to get up and running, but one thing at a time!)

[rogs]

Hey @moppylinglong!

Try keeping cross-seed out of the gluetun network, and using gluetun instead of localhost as hostname for connecting to qBittorrent.

Cheers!

Roger.