

Yeah, I just wish there was a way to automatically update the port whenever it changes. It doesn’t change often since my server tends to stay on 24/7. But when it does change, it would be nice to have it automatically update.
Back before my current server, I was just messing around with it in Windows. I discovered that qBit actually stores the forwarded port in the registry, and PIA has a terminal command that can print the currently forwarded port. I tried to write a quick .bat script to automatically run when the PIA network adapter connected. The goal was to grab the port number and update the registry for qBit any time the internet went out or my server was rebooted.
And it seemed to work fine. It launched when PIA connected, and pushed the new value to the registry. But that forwarded port was also apparently being stored somewhere else as well, because just updating the registry wasn’t enough; When qBit launched it still showed the old port number, even though all of the documentation I found said it was simply a registry value. At that point I just gave up and manually updated it every time I turned my computer on.
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.
The benefit is that I can see my total up/down speeds, ratios, etc very easily without needing to change to an entirely different instance. I can filter by category, or see everything at the same time.