The 2023 IceWhale Community thread about Uptime Kuma is more of an introduction than an installation walkthrough. The post says the tutorial covers installation on CasaOS, while the replies focus on why people value Uptime Kuma: outage notifications, production monitoring for non-critical services, and push monitors. The forum text itself does not preserve the step-by-step installer configuration.
A useful current page should therefore preserve the CasaOS context and community use cases while using Uptime Kuma's maintained Docker requirements for the actual deployment.
What Uptime Kuma Adds to a Home Server
Uptime Kuma is a self-hosted monitoring dashboard. It can test whether a website, TCP service, DNS endpoint, ping target, Docker-related service, or push-based job is healthy and can send notifications when status changes.
The original replies repeatedly highlighted notifications as the practical value. A dashboard is useful, but the main benefit is finding out that a service is down before someone in the household reports it.
Use the Current Uptime Kuma Container
Current Uptime Kuma deployment instructions use the maintained louislam/uptime-kuma:2 image. The web application listens on port 3001 and stores its persistent database and configuration under /app/data.
For a current CasaOS custom application, translate Uptime Kuma's maintained Docker installation settings into the CasaOS app form rather than using an old image tag from a 2023 video.
Expose the Dashboard on Port 3001
The container-side web service uses TCP port 3001. If that host port is already occupied, map another host port to container port 3001 and open the CasaOS app through the chosen host port.
Changing the host port does not require changing Uptime Kuma's internal port unless the upstream application explicitly supports and needs that change.
Persist /app/data
Map a CasaOS host folder or Docker volume to /app/data. This is the important backup target because it contains the monitoring configuration, user data, and SQLite database.
Recreating the container without that persistent volume makes it behave like a fresh Uptime Kuma installation.
Keep the Database on a Filesystem with Reliable Locking
Current Uptime Kuma guidance warns that the SQLite database needs reliable POSIX file locking and specifically cautions against filesystems such as many NFS configurations for its data directory.
For a home server, keeping /app/data on local storage is the simplest choice. You can then back that local directory up to another disk or remote target.
Choose Monitors That Match the User Experience
A ping monitor only proves a machine responds to ICMP. If the real requirement is “Jellyfin should load,” an HTTP monitor for the Jellyfin endpoint is more meaningful.
A practical set can include:
- HTTP checks for web applications;
- TCP checks for services without a useful web endpoint;
- DNS checks for Pi-hole or AdGuard Home;
- ping checks for basic host reachability;
- push monitors for scheduled jobs that should report completion.
Why the Push Monitor Mentioned in the Thread Matters
One community participant specifically said they used push monitors frequently. Instead of Uptime Kuma polling a service, a backup script or scheduled job calls a unique URL when it succeeds. If that heartbeat does not arrive within the expected window, Uptime Kuma marks the monitor unhealthy.
This is useful for tasks where “the server is online” does not prove the job actually ran.
Test Notifications Before the First Outage
Configure at least one notification channel and deliberately trigger a test alert. A monitoring system that silently fails to send notifications is only a historical dashboard.
For household services, also consider alert fatigue. Monitoring every minor endpoint with immediate notifications can make real outages easier to ignore.
Keep the Monitoring Dashboard Private Unless Remote Access Is Intentional
Uptime Kuma can reveal internal hostnames, service names, network addresses, and outage history. Do not expose it directly to the public internet simply because remote monitoring is useful. Use a VPN, private overlay network, or authenticated reverse proxy if remote access is required.
Do Not Treat the 2023 CasaOS Thread as a Current Version Pin
The source discussion praises a well-maintained application but does not preserve an image version. That is beneficial: use the current upstream release rather than trying to recreate the exact container that existed in September 2023.
Uptime Kuma on CasaOS FAQ
Which port does current Uptime Kuma use?
Port 3001 for the web interface.
Which directory must persist?
/app/data.
Why should the data directory stay on local storage?
The SQLite database requires reliable file locking, and current upstream guidance warns against unsuitable network filesystems.
What did the original community value most?
Notifications and push-monitor functionality were repeatedly highlighted in the replies.
