status.biskopstø.dk

One calm answer to
“is the stack okay?”

This first version is intentionally simple, read-only, and human. It gives Hen and Clippto a fast confidence check on the core surfaces without needing shell access or chat archaeology.

Last checked: 17 Apr 2026, 20:58 CEST Freshness: just updated Mode: read-only v1

Overall state

Gateway

OpenClaw gateway is reachable locally and the service is running under systemd.

OK · 427ms
Discord

Channel auth is healthy and the bot is responding.

OK
Dashboard

dash.biskopstø.dk is live and remains the shared planning surface.

LIVE
Lab

lab.biskopstø.dk is published and serving the new visual homepage.

LIVE

What still needs eyes

Reverse proxy trust Warn

If the Control UI is exposed through a reverse proxy, trusted proxy IPs should be configured so client IP handling stays clean.

Shared-user risk posture Warn

Discord is set fairly open right now. Fine for current use, but it should be tightened if access broadens.

Status automation depth Basic

This version is still snapshot-style. Automated periodic checks and incident history would make v2 stronger.

Gateway service
Running
systemd installed, enabled, active
Discord
Healthy
bot reachable, auth working
Heartbeat
30m
main-session wake cadence
Tracked issue level
3
0 critical, 3 warn, 1 info

What this page answers

The goal is confidence first, not completeness theater.

Fast checks

Can Hen reach the stack?Yes

Control UI is up, dashboard is up, and lab is live.

Is the core bot path alive?Yes

OpenClaw gateway and Discord both report healthy from the latest probe.

Is there a serious incident right now?No

No critical security issues and no active queued/running background-task pileup.

Missing pieces for a stronger v2

  • a real automated checker that rewrites the page or JSON status data on a schedule
  • public or private hosting route for status.biskopstø.dk in Caddy, if not already mapped
  • a tiny incident history section instead of only current-state cards
  • optional direct checks for specific URLs, webhooks, or service endpoints you care about most

Built as the first finished version now, so the next conversation can be about improving the checks, not wondering where the page is.