<p>First, I apologise for not noticing that the comments had been broken for a while. This was entirely my fault and not fault of <a href="https://posativ.org/isso/">ISSO</a>, which I’m still super happy with as a self-hosted comments system. So in this post I’m going to describe what went wrong, and also how I made the system a little more resilient at the same time.</p>

<p>I’ve blogged about <a href="https://www.lonecpluspluscoder.com/2019/12/27/building-an-openbsd-wireguard-server/">putting together a WireGuard server using OpenBSD a couple of years back</a>. The main purpose of the server was to ensure a slightly more secure connection when I was on hotel WiFi. Of course thanks to the pandemic, I have barely travelled in the past couple of years so the server was mostly dormant. In fact, I kept VM turned off for most of the time. The VPN server was set…

<p>I’m in the middle of a server redo - right now, I’m setting up a replacement server for my trusty Dell T30, plus it was time to give this web server a new home. When I started the migration from my old WordPress site to the new static site, the static site was running on a small 1 core / 1GB RAM cloud server at <a href="https://www.vultr.com">Vultr</a>. That had enough oomph for testing and for the last couple of months. That said, this machine is running FreeBSD with ZFS on root,…

<p><em>Update 2021-12-18: It looks like the rdiff-backup port has been removed from the FreeBSD ports tree, so installing it via the port is definitely not an option anymore. Also, the method described below works on FreeBSD 13.0 as well.</em></p>

<p>In <a href="https://www.lonecpluspluscoder.com/2020/01/16/building-an-openbsd-wireguard-vpn-server-part-2-unbound-dns-setup/">part 2</a>, I reconfigured my WireGuard VPN to use an Unbound DNS server on the VPN server rather than rely on a third party server I had used for the original quick and dirty configuration. It was important for me to set up a validating DNS server, which I did in that part.</p>