Selfhosted

58265 readers

424 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Pangolin how to bypass auth when client is connected (lemmy.ca)

submitted 12 hours ago* (last edited 11 hours ago) by PeriodicallyPedantic@lemmy.ca to c/selfhosted@lemmy.world

7 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] irotsoma@piefed.blahaj.zone 2 points 2 hours ago (1 children)

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 1 points 1 hour ago

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.