Selfhosting on M1CH's Log

Using SSH Config `Match exec` to Route Hostnames Dynamically

Thu, 20 Nov 2025 15:06:14 +0100

Why bother with a fancy `Match` block?

When you SSH into a fleet of servers that share a naming scheme, you usually end up copying-pasting the same options over and over. A Match block that tests the host name and then tweaks the connection parameters lets you:

Keep a single config file that works for every member of the group.
Automate proxying or port-translation without having to write a wrapper script.

The example below demonstrates the trick.

Glusterfs down 🫩

Fri, 24 Oct 2025 13:22:12 +0200

This morning I woke up and the radio was not playing. I soon figured out, that my DNS, AdGuard, was for some reason down.

I started with the debugging, even before I had breakfast. Not evan a coffee!

The docker-container for AdGuard was running and reported no error. So I dug deeper and deeper, just to find out, that several containers showed strange behavior. For example did Traefik had som error that it could not find the middlewares, that where configured via environment variables.

Selfhosting on M1CH's Log

Using SSH Config `Match exec` to Route Hostnames Dynamically

Why bother with a fancy Match block?

Glusterfs down 🫩

Using SSH Config `Match exec` to Route Hostnames Dynamically

Why bother with a fancy `Match` block?