Almost forgot before going to bed but I feel bi-weekly is a good rhythm for this.
Let us know what you set up lately, what kind of problems you currently think about or are running into, what new device you added to your homelab or what interesting service or article you found.
deleted by creator
I wonder why so many people had issues with the v6 pihole update.
I pulled the new docker container and it ran overtop the previous version just fine. The only issue I had was I had the admin password set to empty via an env variable and that variable name changed. Took like 10 min to find and fix. The rest migrated perfectly.
Now I’m just waiting on orbital-sync to add v6 support, but that’s just around the corner and not that critical.
deleted by creator
Hmm, I wonder if the failed updates are only direct installs vs docker.
I run two piholes, a primary on a rpi 3b running pios, and a secondary on my main server. Both are installed via docker and both updated without issue (besides the password thing).
I like having the primary DNS on a separate machine; it’s kind of important and I like to mess with the main server a lot…
deleted by creator
I definitely recommend it, particularly using docker compose. It’s made it incredibly easy to add, remove, and modify software installs; keeping everything independent and isolated from each other.
This also makes backups and rolling back updates to individual projects much easier when you do run into problems.
deleted by creator
I’m going through hell, trying to update from truenas scale 24.04 to 24.10
What’s not working? I just set up TrueNAS for the first time, went with 25.04 and figured I could just update my way out of potential bugs, but the updater is broken :D
Well, firstly I had this weird issue where the pools were giving me errors because some folder was missing, I fixed that but 24.10 has literally 0 compatibility with apps from 24.04 and it looks like I’m going to have to reset the whole pool in order to use their new apps ecosystem (because trying to install anything from 24.10 just errors out)… Which is extremely annoying as I have quite a lot of apps setup
You can use https://schedule.lemmings.world/ to automate the posts. Or, given the community we’re in, you can selfhost it!
This week I’ve been doing some work on my GOG Downloader to finally back up all my GOG stuff when I buy new disks, that’s pretty much it for my selfhost/homeserver stuff this week.
I’m the one who files the most bug reports on github under a different name. Our instance runs on LemmyScheduler, so thanks!
I didn’t know that, cool! Though I should probably talk to the mods before setting up such a thing.
Experimented with selfhosting a Woodpecker CI as a complement to my Forgejo.
Works quite nicely, I just need to set up a native ARM64 agent as the overhead of cross compilation on x86_64 is quite big.
Why not just use forgejo’s actions and runner?
Personally I’m mostly involved with my homelab migration so there’s not too much on the selfhosting page except os updates. I set up meshmini earlier to access my thin clients via vPro/AMT but I need to configure the clients before being able to actually using meshmini. Once I’m done with that I’ll finally be able to set up Lemmy and Pine pods.
My selfhosted stuff currently works fine without me doing much which feels good and lets me focus on hardware stuff currently.
Immich. Wanted to exclusively use the external libraries features in read only.
Set it up once in its own Proxmox LXC under Docker. Set it up all properly started scanning my entire library. And when I woke up again it had crashed and I couldn’t recover it.
Started over the following morning and only gave it access to 2024 instead of everything. And it filled up to 30gb/40gb I gave it with thumbnails and files and such. Guess it crashed the other day because it took up too much room.
Guess I’ll start over again, and ensure all the config files and thumbnails are stored on my NAS so they can take up the space they need to without overloading the main (small SSD) on my server.
Finally got my lemmy instance fully updated.
Been improving my backup scripts in advance of adding backup to a server.
Updated servers and other services.
Had a hard drive fail my main zfs array. First time I have experienced a disk failure so it was a bit worrying. Thankfully I had added an additional drive to expand the array so I was able to quickly rebuild to that drive. Currently shopping for a replacement. From now on I think I will keep a cold spare just in case this happens again. I just wish hard drives would stop increasing in price.
You save some money by buying recertified drives from Serverpartdeals.
Yea that is what I have been doing. Although it seems the smaller sizes are not a great deal anymore and I am hesitant to buy anything larger due to the long rebuild times
I’m setting up Seafile and trying to swap everything from docker to podman. The longer term goal is that once everything is on podman, I’ll get a new NVME drive and install MicroOS so I can retire my old SATA SSD (I’ve had it for 10 years or so, across 3 PCs).
I’m also considering setting up Forgejo and getting a worker to build my Rust projects.
I’m in the process of doing an initial restic sync of my primary storage to B2 as offsite backup and while I’m at it finally got around having a look at resticprofiles to simplify my restic backups on all my systems. Highly recommend it as it reduced my mental overhead of doing regular backups quite a bit!
I’m currently looking to connect an NVMe SSD to a Pi 4 I have in a differences location to finally have proper 3-2-1 backups. I’m trying to find a NVMe to USB adapter that will work though.
After having upgraded my Pi-Hole to v6, for some reason yesterday it started to not recognize any of the blocklists. So, I resetted it and now it works.
My pihole exploded yesterday, all my fault. A couple of years ago, I created a script called via cron to update pihole’s services every other week. This was great, until now when it updated to v6 at 4am. To make matters worse, I neglected to automate raspian updates, meaning it was very out of date, and was no longer compatible with pihole-FTL (thinking back, I thought I automated it too, but I guess not).
I took an image after creating a pihole “teleporter” backup, and began formatting. In my lack of caffeine and focus, I missed that my teleporter file was corrupt after I had successfully wiped the SD card. Thankfully I had that image as I was able to mount it and retrieve my blocklists via sqlite, otherwise I would have had to start from scratch.
One good thing that came out of it (for my taste, anyway) was that I swapped the OS on the pi to fedora. No more debian around here!
Tomorrow, I plan on setting up some backup automation for my pi, as it’s the only machine missing backups at this point.
@AmbiguousProps @tofuwabohu why would you privilege fedora over Debian? Asking because I am trying to do the reverse.
It’s mostly personal preference, but I have grown to hate
apt
in general. I used it for over a decade and constantly got in dependency hell. I’ve yet to have anything like that happen on Fedora, especially Silverblue and CoreOS.
Why so hostile sounding against debian?
What does fedora better?I don’t mean to sound hostile, that’s probably my past demons coming out. Like I said in my last comment, it’s really
apt
that I hate. It would constantly break or put me into dependency hell and I haven’t had to deal with that (yet) with Fedora.I haven’t put my finger on it, but Fedora, for whatever reason, also just feels faster.
Pihole 6 broke my DNS (dnsmasq), and since I had a fw rule in opnsense to only use pihole’s DNS, and deny public DNS access, it was an early rise for me :)
And that’s why you have either a backup for your DNS or know whats auto-updated ;)
As you mention opnsense:
What do you mean with fw rules to only use pihole dns?
This sounds partly like a DHCP config and partly like a deny (hardcoded) DNS requests and to please use what DHCP supplied (looking at you google/amazon)I did have backups, it was an easy fix. I had a
pihole -up
on a crontab for years, probably not the best idea :)FW rule accept :53 from pihole only, deny :53 from all. I had some devices with hardcored DNS settings (8.8.8.8).
Realised my jellyfin lxc had a maxed out bootdisk yesterday, haven’t been using it for a while. Luckily I have decent backups setup so I was able to restore a backup from late January when it wasn’t filled yet. A quick library rescan and everything was up and running again.