Just out of curiosity, why bother running 4 instances of qBit for the various *arrs? Why not just use automatic torrent management, and have the different categories download to different folders? My *arrs are all using a single instance of qBit, and each service simply uses a different category with a different download path.

I started to become frustrated with the queue on a single qbit instance, I would set the max total of active torrents to 15; 10 active downloads and 5 seeding and it starts out fine but eventually those 10 active downloads all became stalled.

The amount of times I have had to open qbit to just move stuff down the queue so other things could download was obnoxious so I made 3 other instances for each *arr and it’s felt easier to manage.

Proton VPN claims to offer Port-Forwarding for their Wireguard router configs however, when I attempt to do it they don’t display the active port anywhere on their website.

Asus WRT Routers are great however, it doesn’t support certain Registrars for DDNS like Cloudflare so I had to install Merlin Firmware, ssh into the router and then manually configure a cron-job so that my A records stay up to date with my WAN.

https://github.com/clayauld/asus-merlin-cloudflare-ddns

Thankfully somebody already been down this path a posted the documentation which made things 100x easier.

Asus WRT Router > Proton VPN

^

ProxMox EV

^

Debian 12 Headless VM

^

Docker Compose

^

Docker Engine

• Unbound
• Pihole
• Prowlarr (for indexers)
• Radarr
• Sonarr
• Lidarr
• Readarr
• 4 Instances of QBit for each ‘Arr
• Jellyfin
• Jellyseerr
• Traefik for SSL/TLS
• Homepage

Kind of a crude way of putting my setup but I think it gets the point across.

The Caindian ocean is a old time classic.