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. ;)
To follow up on this:
I now use a combination of caddy as reverse proxy and authelia for authentication.
In my opinion caddy is the best reverse proxy, it’s super lightweight and the caddyfiles are super easy to read.
Authelia is surprisingly easy to get setup. I was a bit hesitant because it looked a little overwhelming in the beginning. When you sit down for half a day and dig into it, it’s really surprisingly straightforward.
I found that before and it’s really interesting. I didn’t really find it easy to understand, though.
Maybe I’ll look into it again. As I understand it, you wouldn’t even need caddy, oauth2-proxy itself can act as reverse proxy, right?
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.
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.
You mentioned NPM. Not sure if you mean the UI version since you mention config files. Id recommend it heavy. Very noob friendly and provides certs for you.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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).
To follow up on this: I now use a combination of caddy as reverse proxy and authelia for authentication. In my opinion caddy is the best reverse proxy, it’s super lightweight and the caddyfiles are super easy to read. Authelia is surprisingly easy to get setup. I was a bit hesitant because it looked a little overwhelming in the beginning. When you sit down for half a day and dig into it, it’s really surprisingly straightforward.
https://github.com/azukaar/Cosmos-Server
It really does look cool. It can be deployed using Docker. I’ll have a look at it.
Put https://github.com/oauth2-proxy/oauth2-proxy in front of caddy.
I found that before and it’s really interesting. I didn’t really find it easy to understand, though. Maybe I’ll look into it again. As I understand it, you wouldn’t even need caddy, oauth2-proxy itself can act as reverse proxy, right?
upstream services > oauth2-proxy > caddy
Not sure what kind of services you want to run. But I guess you want auto https etc. so probably you want to stick to caddy.
I’ve always used Nginx for my reverse proxy and their
basic_authdirective for password protection. For a homelab setup, I’m not sure why you’d need anything heavier.Well yeah, basic auth is surely the easiest method … though I rather like to go the oauth2/OIDC route.
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_authworks 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.
You mentioned NPM. Not sure if you mean the UI version since you mention config files. Id recommend it heavy. Very noob friendly and provides certs for you.
Image: jc21/nginx-proxy-manager
Docs: https://nginxproxymanager.com/guide/#quick-setup
I’m not sure how to do auth with this setup so I’m missing that info for you though.