The_Zen_Cow_Says_Mu

I have option #1 set up for my hp printer using its mac address on opnsense. it’s worked for several years to prevent phoning home, updates breaking 3rd party ink, etc.

i used authentik for a couple years, but it really is a little much for a home server, and very fragile on major version upgrades.

i tried voidauth, but didn’t like it, mostly its visual design

pocket id has been fine. I combine it with tinyauth (uses pocket id for authentication) for services that i use forward-auth with instead of oidc logins. So far so good, and it’s convenient that bitwarden handles passkeys so it’s easy to login from multiple devices.

If you want to expose plex to the open Internet (not a VPN) Don’t open the plex port to the internet. Turn off the “remote access” setting and run it behind a reverse proxy instead.

wow, setting up vaultwarden quadlet to work with my selfhosted OIDC sso was stupid easy. Migrating my bitwarden setup to it took no time at all. The extra step was setting up some extra pocketid passkeys to be stored on non-vaultwarden hosted systems (ie. google) to prevent myself from being locked out in case vaultwarden crashes (which probably was a good idea to do regardless). Just need to add the data volume to my regular backup.

Self-Hoster 🏡

• Fleet: 2–3 devices · 5–10 TB
• Motivation: Privacy & data ownership, Independence from Big Tech & subscriptions, Fun / the hobby itself
• My MVPs: Mythtv, PocketID, Plex, Immich, Home Assistant

i’ve been running fedora server for my home stuff for several years. it version upgrades well without issues. The main drawback is the speed of updates, frequent kernel/nvidia reboots required, and having to upgrade the whole system to a new release every 6 months.

Inasmuch as I’ve migrated my entire hosting to rootless podman, I’m seriously planning on installing debian so I can just leave it alone.