1

I am in self hosting for a bit now, have an unraid server and a bunch of services running. Now I want to expose some services through a reverse proxy, but with authentication, preferably google oauth2. I've tried a lot of things, Authentik, Authelia, NPM, and so on. I found everything way to complicated. What I liked the most until now is Caddy with the greenpau/caddy-security module. Very easy config through the caddyfile.... Though the module has to be manually installed after every update of the caddy docker container, thats kind of a turn of for me, since everything else on my server is almost maintainance-free.

You have any suggestions?

.... also this is my first post on lemmy, since I migrated from reddit. ;)

you are viewing a single comment's thread
view the rest of the comments
[-] DudeWithaTwist@lemmy.world 1 points 11 months ago

I've always used Nginx for my reverse proxy and their basic_auth directive for password protection. For a homelab setup, I'm not sure why you'd need anything heavier.

[-] momsi@lemmy.world 0 points 11 months ago

Well yeah, basic auth is surely the easiest method ... though I rather like to go the oauth2/OIDC route.

[-] DudeWithaTwist@lemmy.world 1 points 11 months ago

Just wondering why, because you need some justification to take the harder route. Oath2 is enterprise level, developed by Meta, Google, and others to be top-notch. basic_auth works to dissuade intruders.

Unless you have a stalker trying to infiltrate your network, I can only imagine this will cause more headaches than it's worth.

this post was submitted on 13 Jul 2023
1 points (100.0% liked)

Selfhosted

37809 readers
470 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS