//jellyfin// Latest Updates: https://wiki.haacksnetworking.org/doku.php?id=computing:jellyfin This tutorial is for Debian users wanting to set up a production-ready Jellyfin server. This instance runs on a VM inside my virsh+qemu stack recently recapped in detail in this article. This VM is set up with a LAMP stack, a reverse proxy with Let’s Encrypt, automated syncing, scanning, and some…
//classic-bridging// Latest Updates: https://wiki.haacksnetworking.org/doku.php?id=computing:classic-bridging This tutorial is for Debian users who want to create network bridges, or virtual switches, on production hosts. By production hosts, I mean something that’s designed to run virtual appliances (VMs, containers, etc.). This tutorial assumes you have access to PTR records and/or have a block of external IPs. In this…
//navidrome// Latest Updates: https://wiki.haacksnetworking.org/doku.php?id=computing:navidrome This tutorial is for Debian Trixie users seeking to set up a production-ready Navidrome server. I used virsh+qemu to make a VM sufficient storage, and the VM is set up with a LAMP stack, a reverse proxy with Let’s Encrypt, automated syncing, scanning, and some hardening measures. Im using fpm with…
//mailserver// Wiki Entry: https://wiki.haacksnetworking.org/doku.php?id=computing:mailserverSlides: https://nextcloud.haacksnetworking.org/index.php/s/s6wAL5p7jKHc9DbSeaGL Presentation: https://content.haacksnetworking.org/w/nsMwnJhLnfMrs17W5cAdWg Introduction Contrary to popular belief, it’s entirely possible to self-host email servers. Like others, I listened to the propaganda that “it’s no longer feasible to self-host email” or “it’s too complex and servers won’t respect your mail health anyway” or other such explanations. In 2014, while running workshops…
Latest Updates: https://wiki.haacksnetworking.org/doku.php?id=computing:monitorvitals This tutorial is Debian GNU/Linux users wanting to regularly monitor the temperature and SMART health of their hard drives, as well as a slew of helpful zfs reports. Any production server I build includes these scripts and techniques. I set the vitals script to send me an email each hour, with the…
//managingbots// Latest Updates: https://wiki.haacksnetworking.org/doku.php?id=computing:managingbots This tutorial is designed for Debian OS and LAMP stack users that want to track and or prohibit bot scraping (or other url requests) that might harm server performance and/or cause it to fail. In my case, I have a multi-site WordPress that includes my tech blog, poetry, and teaching blog.…
//mailserver////roundcube// Latest Updates: https://wiki.haacksnetworking.org/doku.php?id=computing:roundcube Latest Updates: https://wiki.haacksnetworking.org/doku.php?id=computing:mailserver It’s been 5 years since I switched full time to my own email server. When I first built it, I was overtaken by the enormity of migrating all the emails, creating all the new accounts, and building two more servers for the other two domains I used for…
//backupnode// Latest Updates: https://wiki.haacksnetworking.org/doku.php?id=computing:backupnode As I discussed in the last post, the sudden server failure and/or link failure that happened a month ago were a source of concern for me. After all, in addition to having my own infra there and that of my clients, I also volunteer and host floss instances of the PubGLUG…
//peertube// Latest Updates: https://wiki.haacksnetworking.org/doku.php?id=computing:peertube As part of the Haack’s Networking business, I run a virtualization stack on a Supermicro 6028U-TRTP+ Dual 8-core Xeon E5-2650 2.2Ghz, with 384GB RAM, which has 576 virtual CPUs to allocate, or 24*12*2, which is threads *cores*sockets. This host uses Debian and virsh+qemu and a collection of bash scripts to manage…
//rustdesk// Latest Updates: https://wiki.haacksnetworking.org/doku.php?id=computing:rustdesk This tutorial is for users of Debian GNU/Linux who want to setup a self-hosted RustDesk instance. This tutorial is designed for a public facing instance/domain which uses an apache2 reverse proxy to serve TLS requests back to the gohttp server listening on port 8000. TLS certs are handled by Let’s Encrypt…