tutorial

OwnCloud Monitoring with Vigilmon: Uptime, WebDAV & SSL Checks for Self-Hosted File Sync

Monitor your self-hosted OwnCloud instance with Vigilmon — use the built-in status endpoint, check WebDAV availability, detect sync failures, and get SSL certificate alerts before users lose access to their files.

It's Monday morning and your team can't sync files. The OwnCloud desktop client is spinning. Someone filed a ticket saying "the cloud is down." You check the server — the process is running, the disk is full, but nobody got an alert. Clients silently failed for six hours over the weekend.

OwnCloud is one of the most widely deployed self-hosted file sync and share platforms, used by teams and enterprises to keep data on-premises. When OwnCloud goes down, sync clients stall silently, WebDAV mounts disappear, and users lose access to shared folders — all without a single notification unless you have external monitoring in place.

Vigilmon gives you the external uptime monitor that catches OwnCloud failures, WebDAV endpoint problems, and SSL certificate expiry before your users file support tickets.

What You'll Build

  • A Vigilmon HTTP monitor on OwnCloud's built-in /status.php health endpoint
  • A web UI availability monitor for the login page
  • A WebDAV endpoint check to verify sync connectivity
  • SSL certificate expiry alerts
  • Alert channels for your operations team

Prerequisites

  • A running OwnCloud instance (OwnCloud 10.x recommended)
  • A free account at vigilmon.online

Step 1: Monitor OwnCloud's Built-In Status Endpoint

OwnCloud ships with a built-in health endpoint at /status.php that requires no authentication and reports the server's operational state.

Test it:

curl https://your-owncloud.example.com/status.php

Expected response:

{
  "installed": true,
  "maintenance": false,
  "needsDbUpgrade": false,
  "version": "10.14.0.0",
  "versionstring": "10.14.0",
  "edition": "Community",
  "productname": "ownCloud"
}

The key fields to watch are installed: true and maintenance: false. If OwnCloud enters maintenance mode (triggered manually or after a failed upgrade), maintenance flips to true and clients stop syncing.

Set up the Vigilmon monitor:

  1. Log in to Vigilmon and click New Monitor → HTTP.
  2. Set URL to https://your-owncloud.example.com/status.php.
  3. Set Check interval to 60 seconds.
  4. Set Expected status code to 200.
  5. Under Advanced → Keyword check:
    • Keyword present: "installed":true
    • Keyword absent: "maintenance":true
  6. Save the monitor.

Vigilmon now checks your OwnCloud status endpoint every minute. If the server enters maintenance mode or returns a non-200 response, you'll be alerted immediately.

Step 2: Monitor the Web UI Login Page

The /status.php endpoint confirms the backend is responding, but users interact with the web UI. A broken reverse proxy, misconfigured Nginx vhost, or failed PHP-FPM process can take down the UI while the status endpoint stays reachable on a direct port.

Add a web UI monitor:

  1. Click New Monitor → HTTP in Vigilmon.
  2. Set URL to https://your-owncloud.example.com/login.
  3. Set Expected status code to 200.
  4. Under Advanced → Keyword check:
    • Keyword present: ownCloud (or your custom instance name)
    • Keyword absent: 502 Bad Gateway, 503 Service Unavailable
  5. Set Check interval to 60 seconds.
  6. Save.

This monitor validates the full request path: DNS resolution → TLS handshake → reverse proxy → PHP-FPM → OwnCloud application.

Step 3: Monitor the WebDAV Endpoint

OwnCloud desktop and mobile clients use WebDAV to sync files. The WebDAV endpoint is at /remote.php/dav/files/<username>/. You can monitor it without authentication by checking that it returns a 401 Unauthorized response — a 401 means the endpoint is alive and asking for credentials, which is exactly what healthy WebDAV looks like.

  1. Click New Monitor → HTTP in Vigilmon.
  2. Set URL to https://your-owncloud.example.com/remote.php/dav/.
  3. Set Expected status code to 401.
  4. Set Check interval to 60 seconds.
  5. Save.

If WebDAV goes down (PHP errors, misconfigured rewrite rules, or a failed database connection), you'll get a 500 or 502 instead of the expected 401 — and Vigilmon fires an alert. This directly predicts whether desktop sync clients will work.

Step 4: SSL Certificate Monitoring

OwnCloud is typically deployed over HTTPS. A lapsed SSL certificate breaks sync clients immediately — they refuse to connect to an endpoint with an invalid certificate.

Vigilmon checks the TLS certificate on every HTTPS monitor automatically. To configure explicit expiry warnings:

  1. Open your /status.php monitor in Vigilmon.
  2. Click Settings → SSL Certificate.
  3. Set Alert when certificate expires in less than to 14 days.
  4. Save.

You'll receive an alert two weeks before your certificate expires — enough time to renew via Let's Encrypt or your CA before clients start failing.

For Let's Encrypt certificates (90-day validity), set the alert threshold to 30 days to give yourself a comfortable renewal window.

Step 5: Alert Channels

Go to Notifications → New Channel in Vigilmon and configure:

  • Email — immediate alerts to your sysadmin or IT team
  • Webhook — post to Slack, Teams, or a ticketing system like Jira

For Slack, a maintenance mode alert looks like:

🔴 DOWN: owncloud.example.com (keyword check failed)
Keyword "maintenance":false not found — OwnCloud may be in maintenance mode
Region: EU-West
Triggered: 2026-03-10 08:23 UTC

When OwnCloud recovers:

✅ RECOVERED: owncloud.example.com
Downtime: 4 hours 12 minutes

For WebDAV failures, which directly impact sync clients, consider a lower alert threshold and routing to an on-call channel.

Step 6: Status Page

Go to Status Pages → New Status Page in Vigilmon. Add all three monitors and publish the page. Share the URL with your team so they can self-serve status checks before filing tickets:

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

Embed the badge in your internal IT wiki or intranet page so users can check status themselves.

What You've Built

| Scenario | How Vigilmon catches it | |---|---| | OwnCloud process crash | HTTP monitor detects 502/503 from reverse proxy | | Server enters maintenance mode | Keyword monitor detects "maintenance":true in status.php | | Database (MySQL/MariaDB) unreachable | /status.php returns non-200 or error body | | PHP-FPM failure | Web UI monitor detects 502 Bad Gateway | | WebDAV endpoint broken (sync clients stall) | WebDAV monitor detects unexpected status code | | Disk full (OwnCloud writes fail) | Status endpoint returns error; web UI shows error page | | SSL certificate expiry | Vigilmon TLS check fires 14 days before expiry | | Nginx/Apache reverse proxy failure | Web UI and status monitors both detect the failure |

Self-hosted file sync carries real responsibility — your team depends on it for daily work. OwnCloud won't send you an alert when it goes down; that's Vigilmon's job.

Start monitoring your OwnCloud instance 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