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.

  • jafea7@lemmy.worldEnglish
    2·
    8 months ago

    If it’s anything like Australia, it’s just a matter of not using the ISP’s DNS servers. eg. Use Quad9, CF, NextDNS, etc.

    • Snowplow8861@lemmus.orgEnglish
      1·
      8 months ago

      There have been a few cases where ports are blocked. For example on many residential port 25 is blocked. If you pay and get a static ip this often gets unblocked. Same with port 10443 on a few residential services. There’s probably more but these are issues I’ve seen.

      If you think about how trivial these are to bypass, but also that often aligns to fixing the problem for why they’re blocked. Iirc port 10443 was abused by malicious actors when home routers accepted Nat- pnp from say an unpatched qnap. Automatically forwarding inbound traffic on 10443 to the nas which has terrible security flaws and was part of a wide spread botnet. If you changed the Web port, you probably also are maintaining the qnap maybe. Also port 25 can be bypassed by using start-tls authenticated mail on 587 or 465 and therefore aren’t relaying outbound mail spam from infected local computers.

      Overall fair enough.

    • ElkendersOPEnglish
      1·
      8 months ago

      I did try a custom DNS in the Prowlarr compose stack in Portainer but it didn’t help unfortunately. Do you do it a different way?

      • ElkendersOPEnglish
        2·
        8 months ago

        Omg I was doing DNS wrong in the compose. Totally works now, thank you!

        Edit oh no, I thought I’d cracked it but still unable to connect.

      • jafea7@lemmy.worldEnglish
        1·
        8 months ago

        I set the computers DNS, not the container … so everything on the computer will use Quad9, etc.