What's up, selfhosters? - The Sunday thread
-
@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
aptin 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
aptthat 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.
-
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.
Trying to get my hands dirty with LLM, Ollama and Web Scrapping.
I don't understand most of it , but hey, that's the fun. No complaints.
-
Try the WebOCC app in nextcloud apps.
Thanks! It just threw an error at me when I launched it, but I'll see what I can do. Based of the warnings in the admin panel, there isn't anything critical for me to address, I just hate that orange.
-
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 -upon 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).
-
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.
I've had two failed harddrives in the last month. Not sure if bad batch or what. Thankfully the order these were on only were the two drives so may not see more. They are under warranty but it's still a pain!
Otherwise I'm enjoying Mealie lately for my recipes. Kinda nice having them all in one place but accessible by anyone in the house.
-
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.
I feel bi-weekly is a good rhythm for this.
What does biweekly mean to you? Twice a week, or once every two weeks? If it's the latter, I prefer to use fortnightly, since it's not ambiguous.
-
Cool! Which installation method did you use?
-
I feel bi-weekly is a good rhythm for this.
What does biweekly mean to you? Twice a week, or once every two weeks? If it's the latter, I prefer to use fortnightly, since it's not ambiguous.
I mean every other week. I wasn't aware of the other interpretation, but I think in combination with "The Sunday thread" it's unambiguous?
I have never heard fortnightly, but then I'm not a native speaker. Is that commonly used?
-
I did manual docker. I host some other things as well, so running it through nginx proxy manager that I already had set up.
I also planned to do the same (bare nginx instead of NPM but otherwise the same). Did you just remove the nginx container from docker compose and use the same arguments in NPM or do you double-reverseproxy or something else?
-
I feel bi-weekly is a good rhythm for this.
What does biweekly mean to you? Twice a week, or once every two weeks? If it's the latter, I prefer to use fortnightly, since it's not ambiguous.
Yeah, nobody other than Brits use fortnightly anymore.
-
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
Unbound broke on both of mine day one of v6 and I’ve still not gone and fixed it. Sigh.
-
How exactly does stuff get broken?
Never rly had a problem bumping up the version in docker. The only issue has been the playstore version taking longer to push updates sometimes for the mobile apps.A few versions ago I upgraded it and some default port configs changed rendering it unusable. Since my upgrades are a docker command, I had to go hunt down the error message. It didn't take long, but it def broke the setup.
-
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.
ITT: lots of busted pihole v6 updates
Finally got started with Grafana, Prometheus and Meshtastic.
-
I also planned to do the same (bare nginx instead of NPM but otherwise the same). Did you just remove the nginx container from docker compose and use the same arguments in NPM or do you double-reverseproxy or something else?
Short answer, yes I removed the nginx container from the lemmy compose file. I followed this guide if it helps: https://www.reddit.com/r/nginxproxymanager/comments/1485y0d/getting_lemmy_running_with_a_separate_nginx_proxy/
-
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.
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.
-
For no 2, in k8s, you can use MetalLB. Then the service will be of type LoadBalancer and you won’t have to create an ingress.
Good suggestion actually, i’ll head back to MetalLB docs. Thanks !
-
Did you check Mint recently? If it's been a while, it could also be dust buildup at the fan.
Its only been a few weeks, but I should give it a good blowout regardless.
-
Short answer, yes I removed the nginx container from the lemmy compose file. I followed this guide if it helps: https://www.reddit.com/r/nginxproxymanager/comments/1485y0d/getting_lemmy_running_with_a_separate_nginx_proxy/
Cool, thanks!
-
I upgraded immich without breaking everything. That's always reason to celebrate.
I’m running the Immich Flatpak specifically for this reason. It’s always one version out of date but always self updates without issues
