this post was submitted on 30 Oct 2023
16 points (90.0% liked)

Selfhosted

40394 readers
379 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] anzo@programming.dev 4 points 1 year ago* (last edited 1 year ago) (5 children)

Containers sharing the same network (e.g. gluetun) should be able to see each other's by their hostnames, yet the VPN blocks that by its very nature, so... Check out https://github.com/qdm12/gluetun-wiki/blob/main/setup/inter-containers-networking.md

[–] Elkenders@feddit.uk 1 points 1 year ago (3 children)

The trash guides say to avoid putting the arrs through VPN so I only put the torrent client through. Is that what you do?

[–] iluap@lemmy.world 1 points 1 year ago (1 children)

I am in the UK TOO, I use docker on a nas and I only have gluetun and qbittorrent using vpn, all my other containers (sonarr, radarr, bazarr, prowlarr) are kt behind vpn. What do you mean prowlarr cannot access the indexers? If you use the setting for the indexer you should be able to try different URLs for it, check if any of them works.

[–] Elkenders@feddit.uk 1 points 1 year ago* (last edited 1 year ago) (1 children)

Sorry don't quite follow. Are the arrs behind VPN on your setup? If I use Gluetun for Prowlarr then I can connect fine to the public trackers, but the information doesn't pass to Sonarr etc. Which makes sense to me, but I don't know how to work around it.

Edit: I've tried all of the alt URLs and still nada also unless it's behind VPN.

[–] iluap@lemmy.world 1 points 1 year ago

In my setup, only qbittorrent container is using the gluetun network, all other "arrs" are using bridge non-VPN connection (my ISP uses CGNAT and I have no need to access them from outside anyway). It may be my ISP does not block those indexers alternative URL's, my previous one didn't either though.

load more comments (1 replies)
load more comments (2 replies)