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.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Updated several Syncthing Server and one of them that comes as Yunohost Package got an new ID.
So that little thingy flooded all my other Syncthing Servers with Sharing requests... Its pretty anoying and surely its that one that serves the outside Backup...
I got tailscale cert to work but I feel kind of bad about learning tailscale instead of headscale
I was going to read into these. What benefits do you see in headscale?
Have you looked into netbird? I have been thinking of setting that up over tailscale
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?
Why would you?
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.
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.
Have you checked if statement-based replication works from mysql to mariadb?
I'm hung up on unrecognized charset #255. Tried rolling everything back to utfmb3; suppose I could go all the way to Latin1. I imagine there's a lot of depth I could learn, but dropping mariadb for mysql seems like the path of least resistance right now.
eta: got the character set sorted. Had to make a new dump, confirm that everything in the dump was utf8mb3, then re-prime the replica with that data. Wasn't enough just to change the character sets internally.
So it works now! Good job
Interesting using systemd for that, I'd probably have chosen containers for that.
What's the reason for replication vs. dumps? Does the client failover to the replica?
I'm not a systemd guru, but it turned out pretty easy. https://dev.mysql.com/doc/refman/5.7/en/using-systemd.html#systemd-multiple-mysql-instances Basically just make [mysqld@copy] sections in my.cnf then systemd start mysqld@copy and systemd is smart enough to pass copy into mysql.
I did it slightly different, using systemctl edit mysql@.service to define different default files for each instance, then [mysqld@copy] sections in each of those files. Seems like the port option for each has to go in a [mysqld] section, but otherwise ok.
Replication because I want to put some live data, read-only, on the VPS, exposed to the world while the 'real' database stays safely hidden in my intranet. SSH tunnel so the replica can talk to the real database.
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 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'll have to look at my fail2ban logs and see if I'm having similar issues.
It should be possible to mod your jail to whitelist an IP range on your local Network.
I'm doing that on one of my jails.