What are your other hobbies/interests? What are some things you’re completely uninterested in but it’s annoying shit you would really like a better way of handling? Got some answers? Now check the awesome self hosted page to see if there are any existing solutions that look promising. If so, now you know at least some things to host.

How to go about it? When I started I was an idiot kid, on Windows ninety-something (or maybe ME), running Apache, MySQL and phpBB. Copy-pasting snippets in Notepad and not comprehending everything. I found desktop Linux later, learned about init systems, watched that go out the window with systemd, etc. I was installing Ubuntu on every beige clunker I could get my hands on back when the Beryl (Compiz) cube desktop video went semi-viral. Eventually moved on to Arch, learned more about CLI tools, editing configs, etc. If you have something that can host VMs, and you want to play with mock bare-metal setups where you create the users, directories, set permissions, blah blah blah - VMs aren’t a bad way to go. It’s good stuff to learn and know. Gives you an excuse to play with tmux’s synchronized input feature, maybe learn some Ansible, and whatever else. If you just have one dust collector sitting around, start trying distros on it. Mess with stuff til it breaks, boot into install/recovery media and try to unbreak it, repeat. As long as it’s fun (or tolerably annoying enough to reach some end goal).

I’ve personally gotten lazy and I’m nearly all-in on containers. A few things are manual but I’ve come to like Docker. I do still manage mine with compose files, even on my TrueNAS system with their “apps,” because compose files are easy to read, keep track of, and modify. My non-TrueNAS machines, I use Docker + Portainer. I should maybe look into podman and quadlets but haven’t bothered yet.

My recent hardware went from RPi4B to Thinkcentre mini PC to building out a 2U TrueNAS system. A PoE switch powers a Home Assistant Yellow and a few cameras. The RPi was repurposed to only host Homepage, NUT (server, watches my UPS and tells more power hungry machines to shut down during outages) and might eventually host Grafana if I ever get into learning it. Another 4B is my Pi-Hole. The Thinkcentre has an 8TB external plugged in and scheduled rsync tasks, on the TrueNAS machine, push back ups of my more important files to it. It also has a couple users set up strictly for running game servers (ioquake and teeworlds at the moment). Those aren’t containerized and things like rcon, config management, map rotation, mods, etc are all handled manually.

TrueNAS hosts everything else. If you need ideas based on what others are hosting, here’s some of what is on it:

• Jellyfin, for TA (see below) and my legally obtained DVD backups.
• TubeArchivist, (TA) for backing up YouTube videos, descriptions, comments. Has a Jellyfin plugin so your backup library is watchable in JF
• Homebox, for home inventory management. I use it to keep track of my tools mostly. You can have locations, sub locations, items… if I pull a rail of sockets, stick them in my toolbag, then carry it out to the shed - so long as I bothered to update their locations in Homebox I won’t waste time digging in the back of my truck, tool chest or other bags because I can’t remember where I last used my 1/2" drive 14mm deep impact. It’s a mildly inconvenient extra step to essentially “check in/out” my own tools, as if I’m working in an aircraft hangar or I’m doing IT asset management, but I find it worth it.
• LubeLogger, for keeping track of vehicle service. Early this year I put a lot of money into fixing my truck. A lot of tools, fluids, and parts to handle a broken water pump and do some preventative maintenance. Still a quarter of what a shop might’ve charged. Since I’m becoming my own mechanic, I wanted something to properly record what I do and how much I spend on it. LubeLogger fits the bill.
• Factorio, for the factory must grow.
• Dawarich, self hosted GPS logs. Seems decent but I might shop around still. I just wanted an alternative to Google Maps for tracking my travel history.
• Audiobookshelf, for some audiobooks but mainly for archiving a small handful of podcasts.
• Romm, because I’m compelled to hoard old games and occasionally even play them.
• Immich, because I’m not paying Google to store my photos.
• FreshRSS, because there’s still a dwindling number of sites that don’t force you to visit them to read an article in its entirety. Mainly for Hack A Day, a couple devlogs from game makers, the latest CVEs, some global news sites, NASA’s “Astronomy Picture of the Day” (APOD), etc.
• Samba, for some SMB shares that family can dump files into
• ClamAV, because family is dumping files into their SMB shares

I’m looking at hosting lemon-manuals (successor to charm.li). It’s basically a massive collection of service procedures, bulletins, fluid/torque/etc specs, and so on for decades worth of automobiles. Stuff the industry would like to force you into paying AllData, Identifix, or whoever for. I just haven’t had a chance to review their provided “server.” It’s also over 1TB. It’s overkill when I’m only working on three vehicles (mine and my folks’) but I’d like to have it all in case an auto industry lawyer tries to shut them down or i inevitably get a new set of wheels.

I’ve also got intentions of implementing some sort of documentation system but I haven’t settled on one yet. It’s not really for me. I can read my configs and go off plain text. Mainly it needs to be simple enough for my family to work with. My homelab has a bus factor of Me. Whoever has to deal with it when I’m gone needs to know enough to retrieve my encrypted password database so they can get into my emails/bank account to cancel/pay for things or whatever, back up any media of mine they want to keep, back up their own stuff, probably some instructions on how to burn their shows/movies/music back to discs, and shut everything down. Because one day things will break, servers they don’t understand will have failures, they’ll sell the hardware or give it away to designated friends/family members who can hopefully use it… all that unhappy stuff most of us don’t think about until it happens. In fact some sort of contingency plan should probably have been the first thing I recommended, but with some luck you’ve read this far and will put your own into place.

Anyway, hopefully something in the above rambling helps you on your way.

What device did you use to post this question?

Use that device to run a web server.

My personal recommendation is to get started asap with what you have. That would mean using any old thing you have laying around. Do you have an old laptop? They are ideal for beginner self hosting as you can physically access the machine and it includes a battery backup right in the machine. Usually they are also fairly lower efficient, so that is nice too.

Buying dedicated hardware acts as a barrier to actually doing things, so getting past that is key. If you find you don’t actually want to do self hosting you can just stop using your old laptop, but if you bought a full server machine it will be a bit of a trap and make you feel like you failed in some way. Also, the cost right now is fairly prohibitive, but using existing hardware can make that much more manageable.

As for what to run, I would recommend trying a fresh install of a distro based on Debian, Ubuntu, Fedora, and Arch. Yes, four. They are different and have a different feel to them, but also have different communities. By going through the process of installing each one you will get a feel for the system and the community around it and have a better idea what works for you. I spent a few years having around the Debian end of things but eventually moved over to Arch stuff and am currently using EndeavourOS. Your experience will likely be different to mine but trying a few different options will help you figure it out.

Then moving on to services. Try to see what you actually use your machine to do now and then find services for that. For example, if you use something like Google Drive to synchronise data from your phone to your desktop then try using Syncthing to replace that. If you use Netflix to watch stuff try using Jellyfin. If you do play things like Minecraft get a local server running.

These will all be for learning, so their performance doesn’t need to be better than what a professional can provide, they just need to work and be yours to learn with. If you find you love doing this and enjoy the process but the hardware is holding you back this is a good time to upgrade to a dedicated machine.

For this I would recommend getting an office computer like an Optiplex or similar, just a basic office computer with an i5 or similar. You will want a fairly good amount of RAM in it, probably 16GB minimum and really 32GB is where things start getting good. A dedicated graphics card is not likely to be useful this early as the iGPU in most modern processors is actually fairly robust and should handle transcoding video for most use cases at a small scale. Storage could be one SSD for the OS and multiple spinning disk drives in a RAID or similar configuration for storage. The SSD will make the actual OS faster, decrease boot times, and make it faster to install and update things making updates less disruptive. The spinning media is way cheaper and you can backup all of your OS drive onto the spinning disks as a cron job in low usage times.

That’s my two cents on it, start with what you have, expand as you need but not aggressively before you need it, and try things now before you are too afraid to mess something up because you rely on it. Remember to have fun and experiment, nothing teaches better than experience. Enjoy yourself, don’t take it too seriously, and don’t lock yourself in to one specific thing, be flexible and willing to experiment.

I have a garbage dell wyze thin client with tiny11 and hyper-v running Homeassistant OS. I did this because the solar inverters and batteries have windows only software tools plus an android app in WSA. Also runs jellyfin with a few shows. I plan to migrate but can’t decide on what OS. I found out USB and serial passthrough will work, so I can use a Windows VM.

The networking is garbage because it’s actually got two wifi NICs, I haven’t pulled Ethernet. One dedicated to HAOS. Tailscale works great.

I have one question. Are you using an of the shelf router or something like OpnSense?

If the answer is no then you have found a good place to get started. As you begin to self host you will need to look at securing your new toys.

You will gain a ton over a consumer router. They are often just powerful enough to get the job done today. They rarely get updated and if the product is end of life you can only hope a project has picked it up or replace it with similar risks. Building your own you can shoot the specs to a point where you have room to run other features and last a long time. You can run something like CrowdSec, multiple vLan’s, time server, DNS servers with multiple upstream servers and ad blocking similar to piHole, Caddy, ACME client, captive portal for guest networks, Intrusion Detection, and a lot more.

Then you will not only have some understanding of the function and use while you expand your self hosting journey to all those fun services you will also have the flexibility to secure your network when you begin to integrate those things into your home and life.

I’m running my own router using OpnSense, server running TrueNAS, smart home with HomeAssistant and fairly complex network of devices. I have a 10Gbps fiber backbone and a 48 port switch for my 1Gbps ethernet. It can be addictive especially when you are rebuilding a house.

After that figure out what you need, want, and desire. But keep your router as a separate device from everything else. And remember that what you think you need will only work for today, software is only going to get more complex and need more horsepower to keep it going.

For hardware there are two schools of thought, newer lower power devices and older stuff. The choice is spend now or over time. My used X10SLL-F with a xeon E3-1226 v3 router, my X10DRH-C with a pair of E5-2683 v3’s and my desktop Ryzen 5800X which is currently also my Frigate NVR host along with other miscellaneous hardware draws along with the other devices in the house (fridge, deep freezer, smarthome stuff, and the like) draw about 1100 watts. So my baseload is about the same as any other us household.

My first advice is: it’s always too small. You always realize that you need more, as you can get bigger. As an example from me. I started with 3TB of storage for data hoarding. I quickly upgraded to 21TB and it’s still not enough. You may start with something small, but there is so much. Technically you could go up to AI selfhosting. Especially when you go the route with image and video generation, this takes up resources. I heard the Mac Mini is getting used for local AI.

As for what to host, you should ask yourself what do you need. Lemmy and Peertube I count towards not useful for private usage. A cloud storage like Nextcloud is something very useful. Jellyfin is useful. I would start with cutting out 3rd party cloud services from your personal usage. Instead using dropbox/google drive/iCloud and so on, use Nextcloud. Same for images. Make your local media like movies, music, audio books, books and so on accessible to all devices, with the neat features we love from other services like Netflix, Audible, Kindle and so on. You could also just starting hosting your own game servers, than renting or making it only available when you also play.

But be aware of the risks. Something like a Minecraft Server can be made accessible via VPN. If its open to the internet, the damage is rather small, if you don’t value your minecraft world that high. I rather have my Minecraft World deleted, than my personal pictures stolen. When you can open your service only to LAN, you have a lower risk to get it compromised (the risk isn’t zero! It’s never zero. Air gaped systems make it near zero, but not zero.)

When you do open your stuff to the internet, you need to update your software well and configure it well. Stuff like email is a pain to configure. I looked long for a managing software package, which made it easier for me but to leave me freedom. Next important thing is updates. YOU NEED TO UPDATE YOUR STUFF! I do prefer everything with auto updates. I use watchtower for my docker containers, even though it’s not recommended with some containers. What’s currently a big deal breaker for me is PostgreSQL. I threw out containers and avoided containers requiring it, as it needs manual interaction. For work I actually need to migrate from MariaDB to PostgreSQL for our chat system. At least they do use the LTS version, so you aren’t constantly needing to manually update.

As for the hardware, it highly depends on what do you need. A rented server (a VPS or a dedicated Server) does have the advantage to be easily in the internet and on the same note, this is a disadvantage. For email and websites this is good but you need to be very careful. You can start with a Raspberry Pi. Home Assistant does run on it and they do offer some apps, like AdGuard Home, Bookstack and Vaultwarden. You can also start with a NAS. I run my stuff on my Synology NAS, a DS920+. It has Docker. But you may want to look into a different company, as Synology did some bad stuff, that makes me them not recommending it anymore. I did heard Ugreen should be good. Obviously you could always go bigger and build your own NAS and using truenas or something else. You can also start with a MiniPC and use Proxmox.

For the operating system, I think the best thing is what floats your boat. I do use Ubuntu. Why? Because I like it. Using Containers is a big recommendation from me. With Proxmox you have VMs and LXC containers, which allows you to experiment within a container and separate stuff. You can throw it away easier, without disturbing other stuff, that is working.

I really would recommend to start small and keeping an eye on risk. Start in your local network and with stuff that isn’t big risk. If you stark taking more risks, don’t go full in in the beginning. If for example you hosts your own file cloud or email, don’t abandon your previous provider and start small, with unimportant stuff.

Now to myself: I have running a rented server, a Pi, a Synology NAS and a mini PC.

I did start with a VPS. Very hard and I made quite a few mistakes. the authorities twice called me out for stupid mistakes. It was the fun days, where I actually thought running a Windows Server in the Internet was a smart idea. I did run a webserver and email from them for quite some time. I even had a Skype Music Bot running without issues. What the authorities didn’t like where my attempts with the DNS Server and my MSSQL Server. Now my rented server is running my mail and webserver (with Nextcloud) and if I feel fancy, a game server. I don’t utilize it as I could and in the near future, I do want to switch things up but I need to keep my mail running.

My Synology NAS is the big stuff. It has my data on it and runs most my docker stuff. There I run audiobookshelf, calibre-web, gitea, jellyfin and paperless-ngx for my main stuff.

My Raspberry Pi 5 is running HomeAssistant to control my smart home stuff and a new addition is Music Assistant.

My mini PC is running Proxmox with Frigate. Frigate is a NVR for your cctv. Not that I have a big cctv system.

Technically I did start earlier with a Minecraft Server and a Teamspeak server, running from my own PC but that has the big downside, that you need to keep your PC running.

Depends if you’re hosting something public, or something private.

For public, a webserver is a simple start. Can be anything you want it to be, but as complexity increases, so does the potential amount of attack vectors, so keep that in mind of you’re considering adding things like WordPress and the like.

For private, a NAS and/or a simple game server is a simple and useful start.

As for how, there’s a million ways to do it, and I’m an old stubborn BOFH that still cling to the old ways of doing it (as in, no VMs, no containers), so I’ll defer to others for that.

While purpose built server hardware is always nice since it comes with some useful additions, the truth is that “any” machine will do. Old discarded PC will do just fine.

Copy/paste from another comment I made a while back:

Look into docker containers in general. If I was going to start from scratch in your position this is what I’d do:

Install a Linux distribution on the computer you plan to use for self hosting. This can be anything from a raspberry pi up to a custom build but I would recommend starting with something you have physical possession of. I found Debian with the KDE plasma desktop environment to be pretty familiar coming from Windows. You could technically do most of this on Windows but imo self hosting is pretty much the only thing that a casual user would find better supported through Linux than Windows. The tools are made for people who want to do things themselves and those kinds of people tend to use Linux.

Once you have a Linux distribution installed, get docker set up. Once docker is set up, install portainer as your first docker container. The steps above require some command line work, which may or may not be intimidating for you, but once you have portainer functional you will have a GUI for docker that is easier to use than CLI for most people.

From this point you can find the docker installation instructions for any service you want to run. Docker containers have all the required dependencies of a given service packaged together nicely so deploying new services is super easy once you get the hang of it. You basically just have to define where the container should store it’s data and what web port you want to access the service on. The rest is preconfigured for you by the people who created the container.

There’s certainly more to be said on this topic, some of which you would likely want to look into before you deploy something your whole family will be using (storage setup and backup capability, virtual machines to segregate services, remote accessibility, security, etc). However, the above is really all you need to get to the point where you can deploy pretty much anything you’d like on your local network. The rest is more about best practices and saving yourself headaches when something breaks than it is about functionality.