Issue with other applications connecting to qbittorrent

[apotenza92]

Hi, thanks for making this it's helped me (a noobie) figure a lot out!

I'm at the stage of trying to get sonarr to connect to qbittorrent as a download client but i keep getting an error.

I presume this is because qbittorrent is accessing the vpn (I'm using the vpn only config) while sonarr is not on the vpn network so the two cannot see each other?

Is this a flaw in your config file or am I doing something wrong.

[apotenza92]

OMG I think I just figured it out. I needed to put in the name of the container under 'Host' in sonarr as the name of the VPN container and it worked.

[Morzomb]

Hello, @apotenza92

For my part, I did this simply by entering the IP that hosts my qbittorrent.

Example:

I recommend you do the same.

I will set up documentation for configuring the different Docker containers soon, if you think that would be helpful.

[apotenza92]

Thank you for the very fast response! Yeh I think that might be helpful for newbies like me.
One question I had for you was what do you think is the recommended way to sync my settings using the repo? At the moment I'm basically syncing my configs folder to github (and ignoring the database files because they get too big) is there a better way to do it I'm unaware of?

[Morzomb]

Hi,

To be honest with you, I didn't fully understand the problem you're facing with the sync. But i can show you how my system is structured:

1. Content of "COMMON_PATH": Once Docker Compose is launched, the COMMON_PATH folder contains various subfolders for services like Jellyfin, Radarr, Sonarr, etc. This helps organize files and configurations properly (see section 1 of the image).

2. Download folder: All movies and series are initially downloaded to the qbittorrent/downloads directory (see section 2 of the image). This centralizes the initial download process.

3. Movies destination: After downloading, movies are automatically moved to the radarr/movies folder (see section 3 of the image). This helps keep media well-organized.

4. Series destination: Similarly, downloaded series are moved to the sonarr/tv folder (see section 4 of the image), allowing for consistent management like with movies.

Most of the configurations for these services can be accessed and adjusted through their respective web interfaces, making it easier to manage and fine-tune their settings.

Feel free to provide more details about your issue so I can assist you.

[Morzomb]

Hello @apotenza92,

Hope you’re doing well! Just wanted to let you know that I’ve updated the installation documentation and added a new configuration section. I hope this will help with any issues you’re facing. Let me know if you have any questions or need further assistance!

[akelshareif]

@Morzomb just chiming in here as another noob. What OS do you recommend using? Would this work with something like TruNas or should I go with linux like Ubuntu/Ubuntu Server/Debian?

[apotenza92]

@akelshareif I've been playing around with things for the last few weeks. For what it's worth, running off docker is relatively OS agnostic. Doesn't really matter too much what your OS is as long as it supports docker. I believe TruNAS has weird docker support with some upcoming releases supporting it?

I'm considering CasaOS to run on a small Nas https://casaos.zimaspace.com/.

I may even delve into Proxmox as a base OS and run a Debian/Ubuntu VM on top of that instead.

[Morzomb]

Hi @akelshareif,

TruNAS could be a good option since, if I remember correctly, it already includes Docker. That said, there's not necessarily one OS that's definitively better than another. My advice would be to choose an OS based on how easy it is to install and update NVIDIA drivers. Ultimately, go with what works best for you, but I’d recommend Ubuntu over Debian, even though my tutorial works on both.