I use this , really great software, great dev too. Loads of support and features. I keep all my *arr stuff behind gluetun
I just set it up this weekend, really enjoying it so far, really good documentation in general as well. Only thing that gave me some pause was how to get port forwarding working with it, but I was able to set up a script & cron job to automatically grab the current port with the Gluetun API.
I was also struggling a bit with that, but didnt need a script or chron job. Maybe Im missing something, but I used this
That integration with Proton VPN is what I’m using as well. However, to automate the updates of my service’s port to match the currently forwarded port is what I wanted a script and cron job for. In this manner, the service will always have the latest forwarded port even after docker service restarts, machine reboots, etc. (since Proton uses a dynamic port allocation that changes quite quickly when disconnected).
I only have qbittorrent behind it, is it important to have sonarr and such behind it as well?
I do it anyways just to prevent any leaks. What's more important than those two is your source aggregator, like Jackett
Do people still use Jackett when NZBHydra2 and Prowlarr exist?
I guess I'm just old school
I switched to Prowlarr recently and while the autoconfiguration of the other *arrs and the consistent UI is great, Jackett works just fine and achieves the same goal.
I use this , really great software, great dev too. Loads of support and features. I keep all my *arr stuff behind gluetun
I just set it up this weekend, really enjoying it so far, really good documentation in general as well. Only thing that gave me some pause was how to get port forwarding working with it, but I was able to set up a script & cron job to automatically grab the current port with the Gluetun API.
I was also struggling a bit with that, but didnt need a script or chron job. Maybe Im missing something, but I used this
That integration with Proton VPN is what I’m using as well. However, to automate the updates of my service’s port to match the currently forwarded port is what I wanted a script and cron job for. In this manner, the service will always have the latest forwarded port even after docker service restarts, machine reboots, etc. (since Proton uses a dynamic port allocation that changes quite quickly when disconnected).
I only have qbittorrent behind it, is it important to have sonarr and such behind it as well?
I do it anyways just to prevent any leaks. What's more important than those two is your source aggregator, like Jackett
Do people still use Jackett when NZBHydra2 and Prowlarr exist?
I guess I'm just old school
I switched to Prowlarr recently and while the autoconfiguration of the other *arrs and the consistent UI is great, Jackett works just fine and achieves the same goal.
Okay, thanks!
Same! It’s been awesome
Same awesomenest here