Pangolin how to bypass auth when client is connected
from PeriodicallyPedantic@lemmy.ca to selfhosted@lemmy.world on 05 Apr 11:23
https://lemmy.ca/post/62893686

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 resource, 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?

#selfhosted

threaded - newest

irotsoma@piefed.blahaj.zone on 05 Apr 12:56 next collapse

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.ca on 05 Apr 15:53 collapse

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.

irotsoma@piefed.blahaj.zone on 05 Apr 21:10 collapse

Yeah get that. I do it because my pangolin is segregated so that if that internet facing layer is penetrated, there’s not much else they’ll have access to. Similarly, if my WiFi is penetrated, there’s just a few devices. And many of my services run on Kubernetes distributed and load balanced across a bunch of cheap devices, so it needs reverse proxying at the ingress anyway. And there are a few other reasons for keeping traffic off of the pangolin server or even the router when it’s internal to internal, but still be able to use the single domain name for the service, especially with IPv6 not having static IP addresses quite the same way as IPv4, so not wanting to hard code IP addresses or even port assignments in services that back other services like the database server which originally was just running on the NAS, but switching it over to another system only required changing the internal reverse proxy, not every service that used it. I like abstraction like that.

PeriodicallyPedantic@lemmy.ca on 05 Apr 21:49 collapse

I may end up doing extra reverse proxies just because complicated configuration is better than complicated use. It kinda feels like there should be a way to do it right in pangolin, it seems like it’s right there lol.

prenatal_confusion@feddit.org on 05 Apr 13:30 next collapse

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.

PeriodicallyPedantic@lemmy.ca on 05 Apr 15:44 collapse

Idk why people are downvoting you.

irmadlad@lemmy.world on 06 Apr 13:05 collapse

Nobody ever knows. There’s never an explanation if the commenter gave inaccurate information, which would be super helpful. It’s just ‘here, have some down votes.’

Decronym@lemmy.decronym.xyz on 05 Apr 21:20 next collapse

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

Fewer Letters More Letters
DNS Domain Name Service/System
IP Internet Protocol
IoT Internet of Things for device controllers
NAS Network-Attached Storage

[Thread #216 for this comm, first seen 6th Apr 2026, 04:20] [FAQ] [Full list] [Contact] [Source code]

mhzawadi@lemmy.horwood.cloud on 06 Apr 01:15 next collapse

Just tested my pangolin client and can see my home IPs fine, but you will need to make sure your pangolin has private resources setup as well as public

PeriodicallyPedantic@lemmy.ca on 06 Apr 05:06 collapse

How do you set up private resources to reverse proxy like public resources? I don’t want to have to change URL when I turn on my pangolin client

mhzawadi@lemmy.horwood.cloud on 06 Apr 09:43 next collapse

Oh, that is a question. Will have a look at how DNS works over pangolin

Waggle6312@lemmy.ml on 08 Apr 17:22 collapse

They are adding this feature soon™. Here is their current roadmap: github.com/orgs/fosrl/projects/3

Though once they implement the reverse proxy for private resources, I’m not sure if you will be able to overlap them with the same subdomains as public resources.

Konraddo@lemmy.world on 06 Apr 19:55 collapse

I don’t think Pangolin can do that. I recently migrated to Netbird but I used to do this:

Set up a reverse proxy in your local homelab, say Nginx Proxy Manager, for internal-use only domains. Then also a DNS server, say Technitium or Pi-hole, to resolve those domains. When connected to Pangolin, you open the whole subnet as a private resource.