Selfhosted

I got tailscale cert to work but I feel kind of bad about learning tailscale instead of headscale

I've been deploying Gitea (or Forgejo, still can't decide), but I've fallen into the Ansible rabbit hole and can't get out. Also learned Terraform in the last week and I'm still on the fence about using it in my homelab. It's nice for the cloud but I don't think it's as useful on-prem.

Set up Zipline to share bigger files with my friends.

almost done re setting everything up after a catastrophic failure (ended up replacing multiple drives, the CPU, the motherboard, the psu, and the ram).

now I'm just running long command after long command, waiting for drives to zero, ensuring extended smart checks pass on new drives, cloning to my backup drives...

this things been down for a few weeks and I'm so excited to have it back up soon!

anyways, moral of the story is, the 3-2-1 strategy is a good strategy for a lot of reasons. just do it, it may save your ass down the line.

So, serious question, should I self-host my servers in AWS?

Updated to OpenSuSE Leap 16.0 with the autotool and it broke some things, but nothing terrible. Had to fix network config and add back Packman for ffmpeg for Jellyfin to work but that was about it

I've been trying to convince a VPS to run two instances of mariadb - one for local databases, one to replicate the homelab. Got mariadb@server and mariadb@replica sorted out through systemd, but now stuck on replication from mysql to mariadb. Looks like I'll be ripping out mariadb and putting everything on mysql.

Finally finished setting up and testing a Peertube instance. The video stuff and object storage related things certainly make it more involved than other fediverse software, but overall it is working quite nicely. Just need to find some workable solution to using GPU acceleration in containers, but I think I mostly figured it out (might work after a server restart, but my sweet, sweet uptime makes me procrastinate on that 😅 ).

I migrated iptimr-kuma to the new v2.0 release. The DB migration took a long time. I learned I probably should have run the vacuum command before the migration, but I never noticed the button in the settings before.

Also preparing Jellyfin for its new 10.11.0 which comes with another long running DB migration.

At this point my whole setup is mostly in maintenance mode - I've got everything I need up and running, making some minor changes here and there (like swapping out StirlingPDF for Bento), and keeping things up to date. I only started this hobby about 6 months ago or so, and I'm really satisfied with where things are at. We'll see when the next Big New Thing arrives.

I have noticed that Microsoft and google are trying to scan my domain for /php-myadmin and similar links that I thankfully do not have.

I had already fail2ban running but it failed to ban a single IP. I did setup custom filters that would ban admin panel scanning attempts but somehow now it also bans my home IP and my phone 5G ip sometimes. No idea how to fix it so far. Also, this filter/jail doesnt necessarily jail everyone attempting to reach these links, just sometimes it does.

I threw a thinkcenter in my laundry room and did the bare minimum to securely SSH into it (fail2ban, nonstandard port, root login disabled, can't login with password, etc), to be used as a testing platform for building my workplace a new website.

Just gotta relearn HTML/CSS and figure out what platform to use.

Also set up traefik/Authelia/maybe Anubis for the new domain and block any access outside of my home or workplace.