lucullus

One big reason why not to buy a Rqspberry Pi for Self Hosting is the price. If you want to run more heavy services (like jellyfin can be), you need the Pis with 8GB of RAM. Though those where already expensive before the sharp rise is RAM pricing. When you include a fitting power supply and a small cooler with fan (so that you don’t run into thermal throttle fast) you are probably already at like 110€ at least. For that money you can also get a used mini PC (those that companies use for their employees), that already has more power and offers better upgradebility (RAM, storage). Also for some services you might run into the problem, there is no version build for ARM devices (though that happens very rarely nowadays).

Though with the RAM pricing problem every computing device gets more expensive. Just include such mini PCs into your comparison to make a good decision.

Mhh, you are probably right. I’m really hesitant to invest more time into troubleshooting tailscale. My own tailscale connections at home are stable, and for troubleshooting at my family member I always have to drive and setup my notebook there.

Maybe I could try to setup wireguard directly in the fritzbox router at my family member. That might need less maintenance as running tailscale in a docker container, as it would remove the wireguard connection out of the NAS itself.

Opening a port directly gives me kind of an ick, because I don’t want to fiddle too much with the family members network. If something happens with it, I will be the one troubleshooting it, and I don’t need more work currently.

So Tailscale connection instability is not common? I don’t like debugging this, since the NAS is remote and I don’t have much time going to the family member again and again for this. It definitely is something on the remote site, since the tailscale connections at my home are stable.

I will definitely have a look at Kopia. I was in search of a good open source backup solution, since borg also has its flaws. I will check it out, when I setup the remote NAS again (as I also want to put bigger disks in it)

For proxmox on a VPS beware: Some hosters are using a kind of virtualization, that is more like a container instead of a VM. This means, that if you need kernel access (like changing active modules) you will fail. Proxmox probably won’t run on such a VPS.

Also: A VPS is already virtualized. Running nested VMs (some VMs on your Proxmos VM/VPS) will hurt the performance. Better stick to containers on a VPS.

I support this change. Hardware can also be relevant apart from thr typical servers/mini PCs. Recently I asked about possibilities for a self hosted video/audio doorbell and was met with really helpful answers. While this question could also have fitted into communities for smart homes, I still think it is a good fit here. Self hosting already is a rather broad term. We should not limit ourselves too much in its definition.

One problem can be, that the better fit community does not have enough active users, thus being unlikely to give a good answer. I think we should have a look at that before refering the user to that community.

Eh, I’m pretty sure it is. Haven’t had Kodi running for a while, but I used it on a Raspberry Pi with an USB HDD with my content long before I had Jellyfin. Though it cannot stream the content over network, just display it on the machines video output (which is what media PCs do)