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?
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]
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
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
They are adding this feature soon™. Here is their current roadmap: https://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.
