I know everyone hates on Oracle but they certainly have the best free tier out there for virtual private servers (VPS). I'm setting up a VPS to create my own reverse proxy tunnel outside of my home network with Pangolin. This allows me to expose home lab applications indirectly, without exposing my public IP and opening ports. It's like we're setting up our own Cloudflare Tunnel, just without the benefit of its CDN and DDoS protections.
Some docker containers create files that have read access to the public. I want to change that. Here's how with access control limits (acls).
I wanted to jot down some Tailscale flags I use quite a bit.
So it does in fact seem that my old m.2 hard drive which is running my Ubuntu server is dying. I've had to restart it daily the last couple of days and now multiple times today and from what I've seen in the logs it looks like there is some corruption going on.
The plan is going to be to boot up a new m.2 hard drive and install Kopia onto it.
Last week I showed you how to run AdguardHome and PiHole using MacVLans. This way we didn't have to deal with any port conflicts and each dns server could be run simultaneously on its own IP address. However, it is undeniable that the MacVLan is a little bit trickier, so in this post we're going to set these up again, only one running at a time of course, in the bridge network, so that our actual server is also a DNS server.
Too often I see folks relying on copies of a persisted database volume mount. While it is great people are backing up their database volumes, backing up a database volume can easily result in a corrupted backup unless the docker container is properly turned off prior to the backup. We like our containers running 24/7 though!
In this post, let's introduce ourselves to the following:
fradelg/mysql-cron-backup for MySQL / MariaDBprodrigestivill/postgres-backup-local for PostgresAds! We don't want them inside our home network. Trackers! We also don't want our apps tracking everything we do. Let's put a stop to it! On top of that we also have the benefit of our own DNS server!
NextCloud is one of those applications that can only take 1 domain. How how can we optimize our domain so that it can be used locally, over the tailnet, AND over the public internet, with different considerations for each?? This is where context aware DNS comes in handy.
Unlike the AIO, we just use a compose file to launch a nextcloud instance. I kind of prefer this, however, you do have to set up your own Collabora and OnlyOffice containers as well, which is not a big deal.