Open Source

Adding an SSL certificate to HomeAssistant

In my previous blog post, I got homeassistant up and running, but without a TLS connection. Let’s fix that. In this post: FreeBSD 13.1 but that’s not relevant to the work being done homeassistant-2022.8.7 creation of a certificate is not covered the sysadmin.com guide covers this – it creates a self-signed cert I’m using a […]

Adding an SSL certificate to HomeAssistant Read More »

Getting Home Assistant running in a FreeBSD 13.1 jail

Home Assistant is not friendly for plain installs. It seems designed for containers or running everything out of pip install. That, in itself, is a disturbing trend I’ve seen on several projects (what? you’re not running a git cloned image?). I’ve seen reports of people running containers etc. However, I want to run this on

Getting Home Assistant running in a FreeBSD 13.1 jail Read More »

Creating a wireguard connection between my home and colo

For years I’ve run the dev, test, and stage nodes for FreshPorts off servers in my basement. This meant that those hostnames have always pointed at my home IP address. I’d like to change that. I first started this using interactive commands (e.g. wg set) but found that approach unsatisfactory. I think directly editing the

Creating a wireguard connection between my home and colo Read More »

Creating a wireguard connection between my home and colo – failed attempt

NOTE: I wrote this, got stuck, then went a slightly different direction: I stopped using wg set Instead, I updated the configuration files directly I was not satisfied with the wg approach Although it is great for modifying things on the file, I don’t think it helps novices learn Wireguard I’m leaving it here anyway.

Creating a wireguard connection between my home and colo – failed attempt Read More »

logcheck – egrep: trailing backslash (\)

When updating to FreeBSD 13.1, I started getting these messages from sysutils/logcheck: egrep: trailing backslash (\) This post will document how I tracked down the problem. It is occurring on several hosts. In this post: FreeBSD 13.1 logcheck-1.3.24 Other similar issues I suspect the issue arises because of the change from egrep 2.5.1 under FreeBSD

logcheck – egrep: trailing backslash (\) Read More »

I forgot to enable compression on ZFS

I forgot to enable compression on this FreshPorts node. I have no idea why/how. After doing this, I went to a directory with a lot of space and copied stuff around. [aws-1 dan /jails/ingress01/var/db/freshports/message-queues/archive] % sudo mv 2021_03.tar.gz 2021_03.tar.gz.tmp 21:01:28 [aws-1 dan /jails/ingress01/var/db/freshports/message-queues/archive] % sudo mv 2021_03.tar.gz.tmp 2021_03.tar.gz 21:01:38 That will free up *some* space.

I forgot to enable compression on ZFS Read More »

Making my pkg.conf configuration version independent

In this post, I will talk about how I modified my pkg configuration so I don’t have to modify it after upgrading a host/jail from one version of FreeBSD to another. You might say that you don’t have to do that. Perhaps you have a different configuration and aren’t doing what I’m doing. HEADS UP:

Making my pkg.conf configuration version independent Read More »

freebsd-update fetch install -> Cowardly refusing to proceed any further.

Today I encountered this. [r720-01 dan ~] % sudo freebsd-update fetch install 14:39:01 Looking up update.FreeBSD.org mirrors… 2 mirrors found. Fetching metadata signature for 13.0-RELEASE from update1.freebsd.org… done. Fetching metadata index… done. The update metadata is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further. I confirmed it was just the

freebsd-update fetch install -> Cowardly refusing to proceed any further. Read More »

Scroll to Top