#homelab — Public Fediverse posts

I’m fine-tuning the cooling system for the USBridge-KVM 2.0 (which transmits BIOS data in text format via SSH). Under heavy load (2K video streaming), the temperature rose to 70 °C, which wasn’t acceptable to me.

I replaced the axial fan with a turbine fan for side-exhaust cooling.
I soldered a 2-millimeter copper spacer directly to the heatsink to reduce the gap to the chip.

Stable temperature of 50°C under load. It’s incredibly satisfying to see the improvement thanks to the hardware modification.

#DIY #Hardware #sysadmin #KVM #Engineering #Homelab #SelfHosted

I’m fine-tuning the cooling system for the USBridge-KVM 2.0 (which transmits BIOS data in text format via SSH). Under heavy load (2K video streaming), the temperature rose to 70 °C, which wasn’t acceptable to me.

I replaced the axial fan with a turbine fan for side-exhaust cooling.
I soldered a 2-millimeter copper spacer directly to the heatsink to reduce the gap to the chip.

Stable temperature of 50°C under load. It’s incredibly satisfying to see the improvement thanks to the hardware modification.

#DIY #Hardware #sysadmin #KVM #Engineering #Homelab #SelfHosted

I’m fine-tuning the cooling system for the USBridge-KVM 2.0 (which transmits BIOS data in text format via SSH). Under heavy load (2K video streaming), the temperature rose to 70 °C, which wasn’t acceptable to me.

I replaced the axial fan with a turbine fan for side-exhaust cooling.
I soldered a 2-millimeter copper spacer directly to the heatsink to reduce the gap to the chip.

Stable temperature of 50°C under load. It’s incredibly satisfying to see the improvement thanks to the hardware modification.

#DIY #Hardware #sysadmin #KVM #Engineering #Homelab #SelfHosted

I’m fine-tuning the cooling system for the USBridge-KVM 2.0 (which transmits BIOS data in text format via SSH). Under heavy load (2K video streaming), the temperature rose to 70 °C, which wasn’t acceptable to me.

I replaced the axial fan with a turbine fan for side-exhaust cooling.
I soldered a 2-millimeter copper spacer directly to the heatsink to reduce the gap to the chip.

Stable temperature of 50°C under load. It’s incredibly satisfying to see the improvement thanks to the hardware modification.

#DIY #Hardware #sysadmin #KVM #Engineering #Homelab #SelfHosted

I’m fine-tuning the cooling system for the USBridge-KVM 2.0 (which transmits BIOS data in text format via SSH). Under heavy load (2K video streaming), the temperature rose to 70 °C, which wasn’t acceptable to me.

I replaced the axial fan with a turbine fan for side-exhaust cooling.
I soldered a 2-millimeter copper spacer directly to the heatsink to reduce the gap to the chip.

Stable temperature of 50°C under load. It’s incredibly satisfying to see the improvement thanks to the hardware modification.

#DIY #Hardware #sysadmin #KVM #Engineering #Homelab #SelfHosted

Uptime Kuma 2.3.2 reverts back to a single SQLite connection by default, fixing stability issues some users were hitting with the multi-connection approach. Small but important patch if you run Kuma. #selfhosted #homelab

https://github.com/louislam/uptime-kuma/releases/tag/2.3.2

Uptime Kuma 2.3.2 reverts back to a single SQLite connection by default, fixing stability issues some users were hitting with the multi-connection approach. Small but important patch if you run Kuma. #selfhosted #homelab

https://github.com/louislam/uptime-kuma/releases/tag/2.3.2

Uptime Kuma 2.3.2 reverts back to a single SQLite connection by default, fixing stability issues some users were hitting with the multi-connection approach. Small but important patch if you run Kuma. #selfhosted #homelab

https://github.com/louislam/uptime-kuma/releases/tag/2.3.2

Uptime Kuma 2.3.2 reverts back to a single SQLite connection by default, fixing stability issues some users were hitting with the multi-connection approach. Small but important patch if you run Kuma. #selfhosted #homelab

https://github.com/louislam/uptime-kuma/releases/tag/2.3.2

Uptime Kuma 2.3.2 reverts back to a single SQLite connection by default, fixing stability issues some users were hitting with the multi-connection approach. Small but important patch if you run Kuma. #selfhosted #homelab

https://github.com/louislam/uptime-kuma/releases/tag/2.3.2

Added QR codes for tunnel configs in wgxdp to make smartphone onboarding more convenient https://github.com/andreek/wgxdp/commit/cf28499e9596dd8ec435381cf344bbc67e1da4ba #wireguard #homelab

Added QR codes for tunnel configs in wgxdp to make smartphone onboarding more convenient https://github.com/andreek/wgxdp/commit/cf28499e9596dd8ec435381cf344bbc67e1da4ba #wireguard #homelab

Added QR codes for tunnel configs in wgxdp to make smartphone onboarding more convenient https://github.com/andreek/wgxdp/commit/cf28499e9596dd8ec435381cf344bbc67e1da4ba #wireguard #homelab

Debian 13 installed. SSH is working. The base configuration has been deployed with Ansible. The host is now in my basement under a table, ready to be forgotten. Next step for when I have time will be to configure encrypted ZFS and Jellyfin.

#selfhosting #homelab

Debian 13 installed. SSH is working. The base configuration has been deployed with Ansible. The host is now in my basement under a table, ready to be forgotten. Next step for when I have time will be to configure encrypted ZFS and Jellyfin.

#selfhosting #homelab

Debian 13 installed. SSH is working. The base configuration has been deployed with Ansible. The host is now in my basement under a table, ready to be forgotten. Next step for when I have time will be to configure encrypted ZFS and Jellyfin.

#selfhosting #homelab

Debian 13 installed. SSH is working. The base configuration has been deployed with Ansible. The host is now in my basement under a table, ready to be forgotten. Next step for when I have time will be to configure encrypted ZFS and Jellyfin.

#selfhosting #homelab

Debian 13 installed. SSH is working. The base configuration has been deployed with Ansible. The host is now in my basement under a table, ready to be forgotten. Next step for when I have time will be to configure encrypted ZFS and Jellyfin.

#selfhosting #homelab

@homelab_de

Heute Spaß mit Proxmox, dem Datacenter Manager und dem Backup Server.

Demnächst steht eine Installation eines Clusters in der Firma an. Mal damit beschäftigen.

Ich habe hier noch 5 arbeitslose Nipogi AMD Ryzen Mini-PCs aus der Ära herumstehen, in der Storage und RAM noch preiswert waren.

Ursprünglich war das mal ein Red Hat Openshift Cluster.

Jetzt könnte es ein 3-Node Proxmox-Cluster + separatem Backup-Server + .... werden.

Die PCs haben zwei Ethernet-Interfaces mit bis zu 2,5Gbit/s.

Könnte einen Ceph-Cluster mit niedrigem Replikationstraffic aushalten.

#homelab #proxmox #virtualisierung #minipc

Replaced the motherboard including new CPU and RAM, the host boots correctly now and the keyboard works! It's time to install Debian 13.

#selfhosting #homelab

Replaced the motherboard including new CPU and RAM, the host boots correctly now and the keyboard works! It's time to install Debian 13.

#selfhosting #homelab

Replaced the motherboard including new CPU and RAM, the host boots correctly now and the keyboard works! It's time to install Debian 13.

#selfhosting #homelab

Replaced the motherboard including new CPU and RAM, the host boots correctly now and the keyboard works! It's time to install Debian 13.

#selfhosting #homelab

Replaced the motherboard including new CPU and RAM, the host boots correctly now and the keyboard works! It's time to install Debian 13.

#selfhosting #homelab

Kurz nach neun, eine Tasse Kaffee getrunken und schon zwei #Immich Instanzen, zwei #Nextcloud Instanzen, eine #Vaultwarden Instanz und #eOS auf meinem #Fairphone aktualisiert.

Kann mich wieder hinlegen 😁

#homelab #selfhost

I've self-hosted my own #Forgejo server for a while now and it's been such a freaking delight to work with, and gives me some relief that my code/#Git repos have a place outside of #GitHub. When I started this however, I couldn't fully migrate everything I had to Forgejo - as some were still tied to GitHub's actions and their hosted runners. Before I could migrate them, I'd need to set up runners of my own on the Forgejo server.

Seeing GitHub's rapid deterioration lately, I resumed my search on setting up runners on Forgejo the right way, and was initially under the impression that it's gonna be complicated... but as it turns out, it really isn't. I set up a simple runner on a remote #RaspberryPi I had using #Docker (Compose) and it was ready to go. Porting my actions/workflows files were super easy too, unlike doing the same for something like #GitLab. Now all of my repos that were on GitHub and had some CI/CD set up have been migrated to my Forgejo server, using my own runners.

I've updated my #Homelab Wiki topic on Forgejo to include the optional step to set up a Forgejo runner. If you're now only considering deploying Forgejo, feel free to check out the rest of the topic which covers the complete setup, some basic recommended configurations, and even how to migrate your repos to Forgejo and set up push mirroring so they still exist on GitHub (if you choose to).

🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/forgejo.md#forgejo-runner

If you're looking for other places to find me online, be sure to check out https://dbt3.ch where you'll find all my social media accounts!

#selfhosting #homelab #social

I didn't like having to use a reverse proxy for the Wii homeserver, even if just for IPv4, so I've set up IP-level packet forwarding from another host with an extra IPv4 address.

Now retro internet clients can talk to the Wii directly!

Details:
http://wii.sjmulder.nl/#forwarding
gopher://wii.sjmulder.nl/1/forwarding

#Wii #HomeLab #LegacyInternetProtocols

I didn't like having to use a reverse proxy for the Wii homeserver, even if just for IPv4, so I've set up IP-level packet forwarding from another host with an extra IPv4 address.

Now retro internet clients can talk to the Wii directly!

Details:
http://wii.sjmulder.nl/#forwarding
gopher://wii.sjmulder.nl/1/forwarding

#Wii #HomeLab #LegacyInternetProtocols

I didn't like having to use a reverse proxy for the Wii homeserver, even if just for IPv4, so I've set up IP-level packet forwarding from another host with an extra IPv4 address.

Now retro internet clients can talk to the Wii directly!

Details:
http://wii.sjmulder.nl/#forwarding
gopher://wii.sjmulder.nl/1/forwarding

#Wii #HomeLab #LegacyInternetProtocols

I didn't like having to use a reverse proxy for the Wii homeserver, even if just for IPv4, so I've set up IP-level packet forwarding from another host with an extra IPv4 address.

Now retro internet clients can talk to the Wii directly!

Details:
http://wii.sjmulder.nl/#forwarding
gopher://wii.sjmulder.nl/1/forwarding

#Wii #HomeLab #LegacyInternetProtocols

I didn't like having to use a reverse proxy for the Wii homeserver, even if just for IPv4, so I've set up IP-level packet forwarding from another host with an extra IPv4 address.

Now retro internet clients can talk to the Wii directly!

Details:
http://wii.sjmulder.nl/#forwarding
gopher://wii.sjmulder.nl/1/forwarding

#Wii #HomeLab #LegacyInternetProtocols

New canary Unbound QUIC build is out. Runs on basically any platform @nlnetlabs Unbound supports. Distroless, and built using our hardened native and mighty 🦾 OpenSSL 3.6.2 + QUIC build environment! (https://github.com/madnuttah/openssl-buildenv)

Full DNSSEC support, QUIC/HTTP3 via ngtcp2/nghttp3... So much fun!

cc @nlnetlabs 💚

https://github.com/madnuttah/unbound-docker

https://hub.docker.com/r/madnuttah/unbound

#DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy

New canary Unbound QUIC build is out. Runs on basically any platform @nlnetlabs Unbound supports. Distroless, and built using our hardened native and mighty 🦾 OpenSSL 3.6.2 + QUIC build environment! (https://github.com/madnuttah/openssl-buildenv)

Full DNSSEC support, QUIC/HTTP3 via ngtcp2/nghttp3... So much fun!

cc @nlnetlabs 💚

https://github.com/madnuttah/unbound-docker

https://hub.docker.com/r/madnuttah/unbound

#DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy

New canary Unbound QUIC build is out. Runs on basically any platform @nlnetlabs Unbound supports. Distroless, and built using our hardened native and mighty 🦾 OpenSSL 3.6.2 + QUIC build environment! (https://github.com/madnuttah/openssl-buildenv)

Full DNSSEC support, QUIC/HTTP3 via ngtcp2/nghttp3... So much fun!

cc @nlnetlabs 💚

https://github.com/madnuttah/unbound-docker

https://hub.docker.com/r/madnuttah/unbound

#DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy

New canary Unbound QUIC build is out. Runs on basically any platform @nlnetlabs Unbound supports. Distroless, and built using our hardened native and mighty 🦾 OpenSSL 3.6.2 + QUIC build environment! (https://github.com/madnuttah/openssl-buildenv)

Full DNSSEC support, QUIC/HTTP3 via ngtcp2/nghttp3... So much fun!

cc @nlnetlabs 💚

https://github.com/madnuttah/unbound-docker

https://hub.docker.com/r/madnuttah/unbound

#DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy

New canary Unbound QUIC build is out. Runs on basically any platform @nlnetlabs Unbound supports. Distroless, and built using our hardened native and mighty 🦾 OpenSSL 3.6.2 + QUIC build environment! (https://github.com/madnuttah/openssl-buildenv)

Full DNSSEC support, QUIC/HTTP3 via ngtcp2/nghttp3... So much fun!

cc @nlnetlabs 💚

https://github.com/madnuttah/unbound-docker

https://hub.docker.com/r/madnuttah/unbound

#DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy

#netbird ist ja komplett out of control!

Ich wollte per #headscale meine VPS mit meiner homeprod verdrahten.
Netbird ist alles was tailscale per SaaS sein kann, aber #selfhosted.
Das setup ist irre. FW auf auf den relevanten Ports, DNS aufsetzen, script anwerfen, Fertig.

Wer wie ich keine Lust auf externe Infrastruktur ausserhalb der eigenen Kontrolle hat und site2site braucht, ich glaube besser gehts nich.

#diy #homelab #overlaynetwork #wireguard

danke @staticvoid für den #nerdsnipe

#netbird ist ja komplett out of control!

Ich wollte per #headscale meine VPS mit meiner homeprod verdrahten.
Netbird ist alles was tailscale per SaaS sein kann, aber #selfhosted.
Das setup ist irre. FW auf auf den relevanten Ports, DNS aufsetzen, script anwerfen, Fertig.

Wer wie ich keine Lust auf externe Infrastruktur ausserhalb der eigenen Kontrolle hat und site2site braucht, ich glaube besser gehts nich.

#diy #homelab #overlaynetwork #wireguard

danke @staticvoid für den #nerdsnipe

#netbird ist ja komplett out of control!

Ich wollte per #headscale meine VPS mit meiner homeprod verdrahten.
Netbird ist alles was tailscale per SaaS sein kann, aber #selfhosted.
Das setup ist irre. FW auf auf den relevanten Ports, DNS aufsetzen, script anwerfen, Fertig.

Wer wie ich keine Lust auf externe Infrastruktur ausserhalb der eigenen Kontrolle hat und site2site braucht, ich glaube besser gehts nich.

#diy #homelab #overlaynetwork #wireguard

danke @staticvoid für den #nerdsnipe

#netbird ist ja komplett out of control!

Ich wollte per #headscale meine VPS mit meiner homeprod verdrahten.
Netbird ist alles was tailscale per SaaS sein kann, aber #selfhosted.
Das setup ist irre. FW auf auf den relevanten Ports, DNS aufsetzen, script anwerfen, Fertig.

Wer wie ich keine Lust auf externe Infrastruktur ausserhalb der eigenen Kontrolle hat und site2site braucht, ich glaube besser gehts nich.

#diy #homelab #overlaynetwork #wireguard

danke @staticvoid für den #nerdsnipe

#netbird ist ja komplett out of control!

Ich wollte per #headscale meine VPS mit meiner homeprod verdrahten.
Netbird ist alles was tailscale per SaaS sein kann, aber #selfhosted.
Das setup ist irre. FW auf auf den relevanten Ports, DNS aufsetzen, script anwerfen, Fertig.

Wer wie ich keine Lust auf externe Infrastruktur ausserhalb der eigenen Kontrolle hat und site2site braucht, ich glaube besser gehts nich.

#diy #homelab #overlaynetwork #wireguard

danke @staticvoid für den #nerdsnipe

Arcane v1.19.1 brings serious security hardening with rate limiting, proper JWT checks, and session storage in the database. Also migrates from Gin to Echo and squashes a bunch of UI bugs. #selfhosted #homelab

https://github.com/getarcaneapp/arcane/releases/tag/v1.19.1

Zwischendrin berichte ich ja immer mal von meinem Mac-Mini von 2014 (mit 500 GB SSD) den ich aktuell mit ZimaOS betreibe.

Bespielen kann ich ihn nur via WLAN, aber die Geschwindigkeit ist wirklich okay:

#homeserver #homelab #laufwerke

Ich werde wohl morgen den Tag #urlaub dazu nutzen, im #garten zu pflanzen und eine Liste zu verfassen, was ich an meinem #selfhosted #gitlab im #homelab brauche und drüber nachdenken, wie ich potentielle Kandidaten testen kann... Der Anfang der Liste ist:
* Issues müssen auf allen branches sichtbar sein
* #markdown support
* #plantuml support
* Keine merge-konflikte wenn Kommentare von unterschiedlichen committern gepusht werden
* Import von gitlab (inkl. Closed, tags, comments
* (Attachments?)

Ich werde wohl morgen den Tag #urlaub dazu nutzen, im #garten zu pflanzen und eine Liste zu verfassen, was ich an meinem #selfhosted #gitlab im #homelab brauche und drüber nachdenken, wie ich potentielle Kandidaten testen kann... Der Anfang der Liste ist:
* Issues müssen auf allen branches sichtbar sein
* #markdown support
* #plantuml support
* Keine merge-konflikte wenn Kommentare von unterschiedlichen committern gepusht werden
* Import von gitlab (inkl. Closed, tags, comments
* (Attachments?)

Ich werde wohl morgen den Tag #urlaub dazu nutzen, im #garten zu pflanzen und eine Liste zu verfassen, was ich an meinem #selfhosted #gitlab im #homelab brauche und drüber nachdenken, wie ich potentielle Kandidaten testen kann... Der Anfang der Liste ist:
* Issues müssen auf allen branches sichtbar sein
* #markdown support
* #plantuml support
* Keine merge-konflikte wenn Kommentare von unterschiedlichen committern gepusht werden
* Import von gitlab (inkl. Closed, tags, comments
* (Attachments?)

Ich werde wohl morgen den Tag #urlaub dazu nutzen, im #garten zu pflanzen und eine Liste zu verfassen, was ich an meinem #selfhosted #gitlab im #homelab brauche und drüber nachdenken, wie ich potentielle Kandidaten testen kann... Der Anfang der Liste ist:
* Issues müssen auf allen branches sichtbar sein
* #markdown support
* #plantuml support
* Keine merge-konflikte wenn Kommentare von unterschiedlichen committern gepusht werden
* Import von gitlab (inkl. Closed, tags, comments
* (Attachments?)

Ich werde wohl morgen den Tag #urlaub dazu nutzen, im #garten zu pflanzen und eine Liste zu verfassen, was ich an meinem #selfhosted #gitlab im #homelab brauche und drüber nachdenken, wie ich potentielle Kandidaten testen kann... Der Anfang der Liste ist:
* Issues müssen auf allen branches sichtbar sein
* #markdown support
* #plantuml support
* Keine merge-konflikte wenn Kommentare von unterschiedlichen committern gepusht werden
* Import von gitlab (inkl. Closed, tags, comments
* (Attachments?)

Snipe-IT v8.5 brings PHP 8.5 support, Laravel 12, critical security fixes, and a supercharged advanced search with AND/OR filtering. Plus the mobile app beta is almost here. Update ASAP. #selfhosted #homelab

https://github.com/grokability/snipe-it/releases/tag/v8.5.0