Dasherr Monitoring with Vigilmon: Dashboard Uptime, SSL & HTTP Response Time Checks

You walk up to your home lab TV expecting to see your Dasherr dashboard — your single-pane view of all your self-hosted services. The screen is blank. Dasherr is down. And because Dasherr is what you use to check if your services are running, you have no idea what else might have gone with it.

Dasherr is a self-hosted application dashboard and startpage — a clean, customizable homepage that aggregates links and status indicators for all your self-hosted services. When Dasherr goes down, you lose visibility into everything it's monitoring. The cruel irony: your dashboard for checking service health has no one checking on it. Vigilmon gives Dasherr the external uptime monitor it deserves — watching your dashboard from outside your network, 24/7.

This tutorial walks you through setting up Dasherr monitoring with Vigilmon.

What You'll Build

• A Vigilmon HTTP monitor on the Dasherr web UI
• An SSL certificate expiry alert
• An HTTP response time performance check
• A dashboard service uptime monitor with keyword verification

Prerequisites

• A self-hosted Dasherr instance (Docker recommended)
• A free account at vigilmon.online

Step 1: Monitor the Dasherr Web UI

Dasherr is a single-page application served by a lightweight web server (typically Nginx or Caddy inside the Docker container). A container crash, a misconfigured reverse proxy, or a failed Docker upgrade can leave the page returning errors — or returning a generic Nginx error page while appearing "up" to a simple ping check.

Test it:

curl -I https://dasherr.your-domain.com/

Expected response:

HTTP/2 200
content-type: text/html; charset=utf-8

Set up the Vigilmon monitor:

1. Log in to Vigilmon and click New Monitor → HTTP.
2. Set URL to https://dasherr.your-domain.com/.
3. Set Check interval to 60 seconds.
4. Set Expected status code to 200.
5. Under Advanced → Keyword check, add:
   • Keyword present: "Dasherr" (appears in the page title)
6. Save.

Vigilmon now monitors Dasherr from multiple geographic regions every minute, catching container crashes and proxy failures immediately.

Step 2: SSL Certificate Monitoring

If Dasherr is exposed to the internet or accessed remotely (via VPN-less remote access, Cloudflare Tunnel, or a reverse proxy with a public domain), SSL certificate health is critical. An expired certificate blocks browser access entirely — no warning page, just a hard stop.

Even for purely local access with a self-signed cert, certificate expiry on internal CAs is a common cause of unexpected browser warnings that break dashboard access.

Vigilmon monitors SSL certificates automatically on HTTPS monitors. Add a dedicated expiry alert:

1. Click New Monitor → HTTP in Vigilmon.
2. Set URL to https://dasherr.your-domain.com/.
3. Under Advanced → SSL certificate, enable Alert when certificate expires within 14 days.
4. Save.

You'll receive an email (or Slack/webhook notification) two weeks before expiry — long before your browser starts blocking access.

Step 3: HTTP Response Time Monitoring

Dasherr is designed to be instant — it's a static dashboard that should load in under a second. Slow response times indicate problems with the underlying container (high CPU, memory pressure, storage I/O) or with the reverse proxy (upstream latency, connection pool exhaustion). You won't notice a gradual slowdown day-to-day, but your monitoring system will.

Test current response time:

curl -o /dev/null -s -w "Total: %{time_total}s\n" https://dasherr.your-domain.com/

Expected output:

Total: 0.084s

A response time above 1 second for a static dashboard page signals a serious underlying resource problem.

Set up the Vigilmon monitor:

1. Click New Monitor → HTTP in Vigilmon.
2. Set URL to https://dasherr.your-domain.com/.
3. Set Check interval to 60 seconds.
4. Under Advanced → Performance, set Alert if response time exceeds 2000ms.
5. Save.

This gives you a heads-up when your home lab server is under stress before it cascades into a full outage.

Step 4: Dashboard Service Uptime with Keyword Verification

A pure HTTP status check confirms the web server responded. A keyword check confirms Dasherr's actual application content is being served — not a fallback error page or a default Nginx placeholder. This matters when Dasherr's Docker volume is misconfigured and the container serves an empty index instead of your actual dashboard.

Test for your dashboard's expected content:

curl https://dasherr.your-domain.com/ | grep -i "dasherr"

Expected output: the Dasherr page title or branding in the HTML.

The Vigilmon monitor from Step 1 already covers this with the keyword check. To deepen the check, add a second keyword unique to your dashboard configuration:

1. Edit the monitor created in Step 1.
2. Under Advanced → Keyword check, add a second keyword:
   • Keyword present: a service name you've pinned in Dasherr (e.g., "Plex" or "Home Assistant")
3. Save.

Now Vigilmon confirms not just that Dasherr is running, but that your customized dashboard content is actually loading.

Step 5: Alert Channels

Go to Notifications → New Channel in Vigilmon and configure:

• Email — immediate alerts for container crashes or SSL issues
• Webhook — post to Slack, Discord, or a home automation webhook (e.g., trigger a Home Assistant notification on your TV)

A Slack alert when Dasherr goes down:

🔴 DOWN: dasherr.your-domain.com
Status: 502 Bad Gateway
Region: EU-West
Triggered: 2026-05-03 08:17 UTC

Recovery notification:

✅ RECOVERED: dasherr.your-domain.com
Downtime: 5 minutes

Step 6: Status Page

Go to Status Pages → New Status Page in Vigilmon. Add all Dasherr monitors and publish the page. When Dasherr itself is down, your Vigilmon status page becomes the fallback — a hosted, external status view you can access from any device:

<a href="https://vigilmon.online/status/<your-slug>">
  <img src="https://vigilmon.online/badge/<monitor-slug>" alt="Dasherr Status" />
</a>

What You've Built

| Scenario | How Vigilmon catches it | |---|---| | Dasherr container crash | HTTP monitor detects 502 or connection refused | | Reverse proxy misconfiguration | HTTP monitor detects non-200 on web UI | | SSL certificate expired or not renewed | Certificate monitor fires 14 days before expiry | | Slow response time (server under load) | Performance threshold alert fires above 2000ms | | Volume/config missing (empty page served) | Keyword monitor misses expected dashboard content | | DNS misconfiguration | HTTP monitor detects DNS resolution failure | | Server reboot not bringing Dasherr back up | HTTP monitor alerts within 60 seconds |

Dasherr gives you a beautiful, unified view of your home lab — but it needs its own watchdog. Vigilmon provides the external monitoring layer that catches Dasherr failures from outside your network, so your dashboard is always there when you need it.

Start monitoring Dasherr today — register free at vigilmon.online.