What’s happening on your servers? Any interesting news things you tried?
I didn’t do anyone other than updating Mastodon (native deployment) lately due to a lack of time. Reading so much about Immich caused me to consider trying it in parallel to Nextcloud but I’m not sure if I want to have everything twice.
Not quite homelab, but I’m about to install Linux Mint on my mom’s laptop and that had me thinking about creating an off-site backup in her place again since she has a fiber connection. I’m still not sure about the potential design though, but currently my only backup is in the same rack as the live stuff.
You must log in or register to comment.
I finally got my ISP to enable bridge mode on my modem.
I also learned that I didn’t lose port forwarding and related services because I had been moved behind CGNAT or transitioned to IPv6 – they simply no longer offer port forwarding to residential customers. Ruminate on the implications of that statement so I’m not the only one with blood pressure in the high hundreds.
Port forwarding is done at the router/firewall, so if ports can’t be transferred its a cgnat thing they are doing. Like a Non CGNAT IP on the internet can be sent a packet on any port.
No, I got it from the horse’s mouth: my WAN address was publicly routable all along, the ISP just disabled those NAT-related features remotely.
the implication of that is weird to me. I’m not saying that the horse is wrong, but thats such a non-standard solution. That’s implementing a CGNAT restriction without the benefits of CGNAT. They would need to only allow internal to external connections unless the connection was already established. How does standard communication still function if it was that way, I know that would break protocols like basic UDP, since that uses a fire and forget without internal prompting.
It’s perfectly reasonable from the perspective of corporate scum: take away a standard feature, then sell it back as an extra. As far as I know, the modem still had UPnP for applications that rely on it.
CLOUDFLARE IS NO MORE FOR MY NETWORK
Soon I’ll drop Cloudflare for my public services too
What are you moving to?
I have been looking for something new.
Last week was moving Immich up to the new release I was on an old version, which meant migrating to an intermediate version to allow a database rebuild. It worked well.
I was bored this week so just ran some wattage testing.
- 15w at idle (800MHz)
- 20w active (3.4GHz)
- 30w peak at boot
What kind of hardware is it running on?
It’s an Intel i5-7700 cpu in a Gigabyte Z270N mobo. Those were chosen as a form factor fit for the Monsterlabo fanless case. (Only a select set of boards, and in this case 1151 brackets, fit the case)
Working on getting bazarr to work with Plex, turns out it still requires radarr/sonarr even if I don’t sail the seven seas. Guess I’ll be learning the entire stack tonight :)
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.
Forgejo has everything Gitea has, with more and being more open
I’ve set up Kavita for my e-books. Nice UI, looks promising, and I’ve added some books. I haven’t really used it yet, because half of this was just an excuse to try podman (instead of docker). I wanted to set it up to run as unprivileged user, without the docker daemon running as root. That wasn’t too hard, but it was definitely a few extra steps.
But something about Kavita didn’t sit well with me. Maybe I don’t self-host enough stuff to know what’s normal, but there is a donate button, which I don’t mind, but its tooltip says: “You can remove this button by subscribing to Kavita+.”
I’m donating to a few software projects already, and I have developed a substantial amount of free software myself. There is nothing wrong with asking for money. But what I cannot stand is when software running on my own device is intentionally acting against my interests. And this tooltip was very clear about not letting me do something that I might want to do.
So I checked the source code for more. I found another anti-pattern: telemetry is opt-out instead of opt-in. But that seems to be it, I didn’t find anything worse than that. So… fair I guess, if the author wants it that way. It’s still free software. It looks like I could delete all the Kavita+ stuff myself and re-build. Which I’m going to do if I keep using it. But this is now an extra step that prevents me from just using it, because I need to feel in control of what I run. Kind of self-inflicted, I guess…
If you reach the point of looking for a different solution, check out Calibre Automated. I tried several different things and this was the best one for me.
I’ve been running Kavita for a year and a half +, and honestly cannot tell where the donate button is, other than going into the settings and clicking the “kavita+” selection. Maybe I’m oblivious. Can you share what you’re seeing? As well with the telemetry option?
Telemetry is in Server -> General -> Allow Anonymous Usage Collection. When you opt-out, it also send a final message to the server that you’ve opted out. The the telemetry itself looks reasonable, I don’t mind sending it. It’s really just the dark pattern of opt-out vs of opt-in that bothers me.
The donate button is the heart in the bottom left menu (not visible in the settings). It’s unobtrusive. I wouldn’t bother to remove it, except the tooltip says that I have to pay to remove it - now it has to go. Asking for donations is fine, but asking for money to remove a button is disgusting.
This looks cool, but I really wouldn’t like having the donate button right in front of me
So, serious question, should I self-host my servers in AWS?
Why would you?
I’ve learned a hard lesson this week. Jellyfin server OS partition run out of free space and corrupted the database. Nothing to do but reinstall. I guess this week I’ll be reviewing backups! 🤣🤣🤣
FYI from the newest release notes for 10.11.0
Jellyfin now actively checks the available free space for its configuration and data directories. If you have less than 2GB of free space in each data directory, Jellyfin now refuses to start to prevent data corruption. Additionally, checks are implemented to prevent certain path misconfigurations that are known to cause issues.oh this recently happened to me. but nothing much was lost, users were managed with SSO, files were unaffected, barely an inconvenience.
Watched status of the entire library was lost though right? Or no?
I don’t like the sound of that. Sounds like bad programming? Who’s at fault? Jellyfin or the database implementation? Why would a nospace error corrupt everything. Sounds absolutely volatile. 😱
They just made a blog post about the next version fixing a long standing issue with their database management. Should probably improve in the near future.
Yikes. Well that’s good, at least. Progress is good.
Building out ansible.
Now it’s creating roles and groups, adding a few items to the hardening playbook, and I’ve been playing with tuning the output as playbooks run.
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…
Set up Zipline to share bigger files with my friends.
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?
Mainly that they can’t enshittify because they’re already open. Tailscale is great right now, and free, but who knows in 5 years
Installed qbittorrent and downloaded a few seasons of Linux isos onto a vps. Discovered accessing those files over SSH to be too slow to play them without buffering so installed filebrowser to get them via http which worked well.
It’s been a long long time since I used bittorrent and wow it works so much better these days.
I’ve set up Uptime Kuma this weekend, monitoring everything from Docker containers, network devices (like IPcams, switches, printers, …), wireguard tunnels, etc etc. (I have 65 monitors set up so far) and a Signal rest api for notifications.
Furthermore, I integrated multiple new ESPHome switches into my Home Assistant setup for cable model reset, alarm system controller reset, etc.
Once I have Uptime Kuma finetuned I will automated som resets.
Uptime Kuma is amazing so far.
Love the post haha! Nothing much here things run rather stable and with low maintance right now.
