I have my pangolin server set up and working, providing forward auth and roll based access before reverse proxying my self hosted resources.

However when I have the pangolin zero-trust client connected, I want to skip the forward auth since I’m already authed via the client. I want to do this since some apps like Jellyfin don’t play nice with the forward auth.

I can’t find a way to achieve this - there is no rule for connected clients. When I set up as a private response, then I don’t get the reverse-proxy functionality, so when the client is connected my urls change (need to add ports), which isn’t really acceptable.

I can set up another reverse proxy behind pangolin, but pangolin already provides reverse proxying so that seems silly.

What am I missing? How can I achieve the goal of skipping forward auth when the pangolin client is connected?

  • prenatal_confusion@feddit.orgEnglish
    42·
    5 hours ago

    This! I couldn’t put it in words but this sums it up perfectly. I am using the Webinterface for jellyfin when on the road and I really would love to use the regular client.

  • Jul (they/she)@piefed.blahaj.zoneEnglish
    2·
    6 hours ago

    Yeah, I have caddy and traefik in front of most of my home-based services, except for a few web UIs like the router’s. Pangolin just receives incoming connections and routes them to the correct reverse proxy in the correct VLAN for that service.

    I have VLANs to separate services that are more public facing from very private ones that only certain devices should be able to connect to directly. Basically, I have one VLAN for IoT devices that need to connect to the internet often but only certain things should access directly, one for very private things like my NAS, database server, 3D printer, etc, that rarely if ever need access to the internet, one for my personal devices (laptop, desktop, phone, tv) which are behind a pihole for ad blocking, and one guest VLAN for guests, but mostly for my work computer which really likes to snoop.

    • PeriodicallyPedantic@lemmy.caOPEnglish
      1·
      3 hours ago

      Pangolin is built on traefik, and does all the reverse proxying I need (X sub-domain goes to Y port on Z home server).

      I don’t really like the idea of n metroyska reverse proxis, both because conceptually it bothers me, but also because my needs seem simple and doesn’t seem like it deserves the extra complexity. The public resource reverse proxy works for everything I have.

      I’m looking for a way to configure pangolin, which already routes property, to skip auth when the auth can be provided by the pangolin client.