tutorial

Homer Dashboard Monitoring with Vigilmon: Uptime and SSL Alerts for Your Self-Hosted Startpage

Monitor your self-hosted Homer dashboard with Vigilmon — track web UI availability, SSL certificate expiry, and uptime for the static asset server that powers your homelab startpage.

Homer is the central hub of many homelabs — a clean startpage that links to every self-hosted service you run. When Homer goes down, you lose the navigation layer for your entire homelab. Worse, Homer is often the first thing you check when something else breaks, so it going offline at the same moment as another service doubles the confusion.

Vigilmon gives Homer external uptime monitoring — watching your dashboard from outside your network with no agents to install, catching outages before you try to click a link that silently fails.

What You'll Build

  • An HTTP monitor on Homer's web interface with keyword verification
  • An SSL certificate expiry alert
  • A static asset and config file availability check
  • Alert channels for immediate notification when Homer goes offline

Prerequisites

  • A running Homer instance (Docker or bare-metal, served via Nginx, Caddy, or Apache)
  • A free account at vigilmon.online

Step 1: Understand Homer's Health Surface

Homer is a static site — a Vue.js application served as HTML, CSS, and JavaScript files. It has no backend process, no database, and no application server to crash. What it does have is:

  • A web server (Nginx inside Docker, or your own reverse proxy) that can go down
  • A config.yml that the frontend loads at runtime — if this file 404s, Homer shows a broken UI
  • An SSL certificate on your domain that can expire
  • A reverse proxy layer that can misconfigure after updates

Monitoring Homer is about verifying these layers externally, since there is no built-in /health endpoint.

Step 2: Monitor Web UI Availability

The primary Homer monitor checks that the dashboard loads correctly:

  1. Log in to Vigilmon and click New Monitor → HTTP.
  2. Set URL to https://homer.yourdomain.com (your Homer homepage URL).
  3. Set Check interval to 60 seconds.
  4. Set Expected status code to 200.
  5. Under Advanced → Keyword check:
    • Keyword present: Homer
  6. Save the monitor.

Homer's default HTML includes the application name in the page title and meta tags. If the web server is down, this check returns a connection error. If the reverse proxy is misconfigured, it returns a 502. Either way, Vigilmon opens an incident and alerts you.

Step 3: Monitor the Config File

Homer loads its config.yml at startup. If this file is missing or returns a 404, the dashboard loads a blank or broken state — the page itself returns 200 but Homer silently fails to display any services.

Add a dedicated config file monitor:

  1. Click New Monitor → HTTP in Vigilmon.
  2. Set URL to https://homer.yourdomain.com/assets/config.yml.
  3. Set Expected status code to 200.
  4. Under Advanced → Keyword check:
    • Keyword present: services
  5. Save.

This check catches the case where a Docker volume mount is lost, a config file is accidentally deleted, or a deployment replaces the assets directory without restoring the config. If you use config.json instead of config.yml, adjust the URL accordingly.

Step 4: Monitor Static Asset Delivery

A broken JavaScript or CSS bundle leaves Homer's UI non-functional even when the HTML loads correctly. You can verify that core assets are served by monitoring a specific asset URL.

To find Homer's main JavaScript bundle filename:

  1. Open your Homer dashboard in a browser.
  2. Open DevTools → Network tab → reload the page.
  3. Find the main app.*.js file and copy its full URL.

Add an asset monitor:

  1. Click New Monitor → HTTP in Vigilmon.
  2. Set URL to the full URL of Homer's main JS bundle.
  3. Set Expected status code to 200.
  4. Save.

Note: Homer's asset filenames include a content hash that changes with each release. Update this monitor URL after upgrading Homer to a new version.

Step 5: SSL Certificate Monitoring

Homer is typically served over HTTPS. An expired TLS certificate means every device that tries to open your homelab dashboard gets a browser security warning, blocking access entirely on managed or hardened devices.

Vigilmon monitors SSL certificate expiry automatically on HTTPS monitors. To enable explicit alerts:

  1. Open your Homer HTTPS monitor in Vigilmon.
  2. Navigate to Settings → SSL.
  3. Enable Alert when certificate expires within 14 days.
  4. Optionally enable 30-day early warning.

A certificate expiry alert from Vigilmon:

⚠️  SSL Warning: homer.yourdomain.com
Certificate expires in 12 days (2026-07-12)
Action required: renew certificate

For Homer behind Caddy (which auto-renews Let's Encrypt certificates), this warning tells you if Caddy's auto-renewal is failing silently — something that happens when DNS challenge provider credentials rotate or your Caddy configuration has a syntax error.

Step 6: Configure Alert Channels

Go to Notifications → New Channel in Vigilmon:

  • Email — good for daily digests and non-urgent alerts
  • Webhook → Discord — instant notifications to your homelab Discord server
  • Webhook → ntfy.sh — push notifications on mobile without a separate app

A Homer downtime alert in Discord:

🔴 DOWN: homer.yourdomain.com
Homer dashboard unreachable (HTTP 502)
Reverse proxy returned bad gateway
Region: EU-West
Started: 2026-02-10 08:23 UTC

For a homelab, discovering Homer is offline while you're already troubleshooting something else doubles the cognitive load. An immediate alert scopes the problem before you start blaming the wrong service.

Step 7: Add a Status Page

Go to Status Pages → New Status Page in Vigilmon. Add your Homer monitors and publish. Keep the status page URL bookmarked separately — if Homer is down, you'll want a status check that doesn't depend on Homer being up.

What You've Built

| Failure scenario | How Vigilmon catches it | |---|---| | Nginx or Caddy container crash | HTTP monitor returns connection error | | Reverse proxy misconfiguration | Monitor detects 502 Bad Gateway | | config.yml missing or deleted | Config file monitor returns 404 | | Static assets broken after upgrade | Asset monitor returns 404 or error | | SSL certificate expired | SSL expiry alert fires at threshold | | Docker volume for assets disconnected | Config and asset monitors both fail |

Homer is lightweight and reliable — it rarely fails on its own. But the infrastructure around it (reverse proxies, Docker volumes, SSL certificates, DNS) fails often enough that external monitoring pays for itself. Vigilmon watches from outside, from multiple regions, with no configuration inside Homer required.

Start monitoring your Homer dashboard today — register free at vigilmon.online.

Monitor your app with Vigilmon

Free plan — 5 monitors, no credit card required. Up and running in 60 seconds.

Start free →
← Back to all articles