Been having a frustrating but rewarding time setting up my first server with some advice from you all. Learned a lot and feel like I’m almost there with a lot of it. One thing I’ve really been struggling with is public indexers on Prowlarr. In the UK I can only access them behind a VPN but Prowlarr can’t access the rest of the suite if it goes behind Gluetun.
I feel like I’ve tried everything, it seems that I likely want to use the indexer proxy built into Prowlarr but I must be doing something wrong as it’s always refused or never resolves. I did read something about privoxy which I did try and look into but no success. Considered just leaving the whole thing for usenet but I’d just love to get some public trackers working successfully in the UK. Does anyone have any advice to someone still learning please?
Thanks all!
Edit: Thanks all for your input! I got it workihg by adding httpproxy=on to Gluetun then adding the http proxy deets into the Prowlarr http proxy page.
FWIW, all of my *arr, and VPN containers use the same network bridge. Prowlarr and torrent use the VPN service, though having Prowlarr on there is maybe overkill. They’re all able to access one another using the bridge gateway + port as the host, e.g.: 172.20.0.1:5050
I mostly used this guide, where he suggests:
I have split out Prowlarr as you may want this running on a VPN connection if your ISP blocks certain indexers. If not copy this section into your compose as well. See my Gluetun guides for more information on adding to a VPN.
One thing I had to make sure of was that the ports for Prowlarr were included in the VPN container setup, rather than the Prowlarr section (b/c it’s just connecting to the VPN service):
ports: - 8888:8888/tcp # HTTP proxy - 8388:8388/tcp # Shadowsocks - 8388:8388/udp # Shadowsocks - 8090:8090 # port for qbittorrent - 9696:9696 # For ProwlarrI wonder if I need to use a proper compose instead of the Portainer stacks function, so they’re all on the same network withing docker.
I have VPN, BitTorrent and prowlarr in one “stack” (a project in Synology Container Manager). Everything else is bundled into a separate project. Not sure how portainer would make this work differently. I don’t have much experience with that.
Yeah that makes sense. That’s helpful thank you. I finally got it working pretty simply last night. Thanks for the help!