Servers@Home
patreon
TrueNAS Scale: Build an arr Stack with Dockge in One Easy Step
🕑 Added 2025-01-28 18:33:35 +0000 UTCThis video demonstrates deploying an *arr stack on TrueNAS Scale Electric Eel 24.10 using Dockge with a single docker compose file for the prowlarr, radarr, sonarr, jellyseerr, jellyfin, flaresolverr, and qbittorrent containers.
This video includes the specific instructions for the hotio qBit container using a VPN with a working example from AirVPN.
The Ubuntu test torrent I use can be found here: https://releases.ubuntu.com/24.04/ubuntu-24.04.1-live-server-amd64.iso.torrent
The link to the compose stack I used is here https://raw.githubusercontent.com/imjustleaving/trueNAS/refs/heads/main/dockge-arr-stack-compose.yaml
The env variable I used is MEDIA_PATH=/mnt/tank/media/
To get this to work you will need to change one thing in the .yaml file which the is VPN_LAN_NETWORK in the qBit section. Mine is 10.99.0.0/24 but yours must be changed to reflect your local LAN subnet. For example, if your TrueNAS Server IP is 192.168.1.25 your VPN_LAN_NETWORK=192.168.1.0/24.
For more info visit the wiki https://wiki.serversatho.me
If you want to signup with AirVPN, you can use my referral link, I get some free VPN time. I would appreciate it! https://airvpn.org/?referred_by=669318
Want to say thank you? https://buymeacoffee.com/serversathome
Comments
Nicolas Schoenfeld
I spent so long... Now I see this.. good God man!! Thank you!!
Servers@Home
This is correct. I will edit the video description to explain this
Alexander Viksten
I know the problem! because the same thing happened to me. We never got the instruction to change this row in the compose yaml text for qbittorrent: - VPN_LAN_NETWORK=10.99.0.0/24 Change to your own host network. In my case it was 192.168.1.0/24.
Servers@Home
Definitely post a support request on the discord server. We will be able to properly figure out what's going on there.
Wayne Mitchell
nice video man! I got all the way to where you opened qbit for the 1st time, then i got this... This site can’t be reached took too long to respond. any ideas?
