Release notes / 2026.10.4

Early access release

Moorhold 2026.10.4 Replaced

Published

Release state

Replaced #

This was the Latest release until 2026.10.5 replaced it. That was before we ran each Latest release on our own Moorhold server first. We haven't tested an update from this release to 2026.11.4. If your server runs it, email hello@moorhold.dev and we'll help you move it.

This release adds a network check to the installer and an optional relay for home networks.

https://moorhold.dev/releases/2026.10.4

Before you update #

What changes
Adds a network check to the installer and an optional relay for home networks. The relay hasn't been tried on a real cloud server yet.
Downtime
Not known yet: there's no one-step upgrade. See Upgrading.
Backup
Updating doesn't take a backup for you yet.
Manual steps
Yes: there's no one-step upgrade yet. See Upgrading.
Still to be tested
No relay has been set up on Hetzner or IONOS yet.

New #

  • A network check before the certificate is requested. moorhold install now checks and reports the server's network: whether DNS for your hostname resolves, where it points, whether the router has NAT loopback, and whether the connection is behind carrier-grade NAT. When a browser on your own network could not reach your Moorhold address, it says so and recommends a relay. The check only reports; it never stops the install. Skip it with --no-network-check.
  • An optional relay for home networks. For a router without NAT loopback, a connection behind carrier-grade NAT, or a contract that blocks inbound ports 80 and 443, you can run a small relay server of your own on Hetzner or IONOS. It passes HTTPS through to your Moorhold over WireGuard without decrypting it, so your certificates and keys stay on your server.
    • moorhold relay init --provider hetzner|ionos makes this server's WireGuard key (kept on the server) and writes the relay's cloud-init, which carries public keys only.
    • moorhold relay connect --endpoint <address> --relay-key <key> brings the tunnel up, declares the relay in the Stack and runs the network check again.
    • moorhold relay disconnect takes it out again; moorhold relay check runs the network check on its own.
  • Your clients' real addresses through the relay. The public front accepts the relay's PROXY protocol header, so per-client rate limits and the access log still see each client's own address.
  • moorhold on the PATH. The installer adds /usr/local/bin/moorhold, the current release's command line, for later commands such as moorhold relay and moorhold sample-data.

Verified #

  • Unit and golden tests: pass.
  • Locally: the relay, the tunnel and the front were run in local containers.
  • Owed: no relay has been set up on Hetzner or IONOS yet.

Images #

The shell, reconciler, collector and portal MCP images are rebuilt. Every other image keeps the digest it had in 2026.10.3.

Still known #

  • Signing in to the tools. Opening a tool after the setup wizard still shows that tool's own sign-in page, then the sign-in service's page. Setup will sign you in once for every tool in a later release.
  • The sample data has no dashboard yet. Superset opens with the sample datasets but no chart.
  • x86_64 (amd64) servers only.

Upgrading #

On a server running 2026.10.7 or later, update from the server's command line with sudo moorhold upgrade <version>, giving the release you're moving to. On a server running 2026.10.6 or later, you can instead download the new release's installer and run it on the server as you did to install, but without --hostname.

Each newer release's notes give its steps under Updating, and say which releases it updates from. If they don't cover the release your server runs, email hello@moorhold.dev and we'll help. More about upgrading

Recovery steps #

There's no automatic rollback yet, so there are no recovery steps to follow on your own. If something has gone wrong with your Moorhold, email hello@moorhold.dev with the version you're on and what you saw, and we'll help. Please don't send passwords or keys.

Download and verify #

The signed release is on get.moorhold.dev. Check the signature on release.lock first, then each file's SHA-256.

FileSHA-256
moorhold-2026.10.4.tar.gz855ab53207f57ce4e150c2e1d0a81cef88127a2b5274dce36aa669efec1cff16
release.lock90091874e300de46b5b1396af453941a99633e3c08b6612a6c95f43b2e4de2b1
install.shf005dc4a4d277e38de6bf9aa31db8ca070b736e6cbbf91019956ac431e4dcd36
cloud-init-ionos.yamld96ea57d83eb93bb2448a4ab553b2c55b3f014ae449b3d5447c89fbc23167edf
cloud-init-hetzner.yaml1d6d57d709826ed2b84b34356f07e907340b13a4f950f08a033eb218fd9245a9
release.lock.minisigSignature, key 7F6D12F3F6217F9C
SHA256SUMSThe checksums above
minisign -Vm release.lock -p moorhold-release.pub
sha256sum -c SHA256SUMS

Public key: get.moorhold.dev/moorhold-release.pub