![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.dbzer0.com/pictrs/image/a18b0c69-23c9-4b2a-b8e0-3aca0172390d.png)
Trash guides say you shouldn’t run the *arr’s through a VPN because you’re likely to get blocked by metadata servers. I only run my download client through the VPN + also use gluetun’s HTTP proxy for Prowlarr’s indexers
Trash guides say you shouldn’t run the *arr’s through a VPN because you’re likely to get blocked by metadata servers. I only run my download client through the VPN + also use gluetun’s HTTP proxy for Prowlarr’s indexers
Use gluetun, look up how to configure for your provider. Run a 2nd container for your torrent client, using network_mode: “service:gluetun”
to run all your traffic though the vpn. Note that if you’re forwarding ports from your client to e.g. access the web UI, you’ll need to forward them from the gluetun container instead.
You still have to have indexers, so you need to deal with them indirectly, but the UI is sooo much nicer. Sonarr/Radarr are pretty easy too. If you know your way around docker you can get it up and running pretty quick.
I also wanted too know so I looked it up:
Usenet “Block Accounts” are accounts where Usenet access is purchased by the gigabyte (GB). For example, a 100 GB block account will allow you to download up to 100 GB of data from a Usenet feed. Most block accounts have no expiration date so you can use them for years. Many people use block accounts as backup accounts to fill in files missing from their main Usenet feed.
I came here to comment this. It feels really esoteric but great selection!
Sure, the docs are pretty minimal though: https://wiki.servarr.com/prowlarr/settings (just click on Proxy)
Basically you can configure a proxy (from your VPN provider for example) for each indexer (or font add a tag to apply it to all of them), and queries to indexers will run through there. This avoids Sonarr making calls to TVDB or whatever through the VPN and getting blocked.