Uptime monitoring
How the panel checks each website the way visitors reach it, records uptime and downtime, and raises the Website down alert when a site stops answering.
VaultPanel checks every website from the panel itself, the way visitors reach it: through public DNS, over HTTPS when the site has a certificate for the name. A site that stops answering shows Down and raises the Website down alert. Monitoring is on for every new website.
How a check works
Every 5 minutes by default, the panel's worker checks the websites that are due:
- It looks the website's primary domain up in public DNS (or the first domain that is not a wildcard).
- It asks for the front page, over HTTPS when the website's active certificate covers that domain, otherwise over HTTP. Redirects are not followed.
- When the check fails, it waits 10 seconds and checks again, so a single blip does not count.
A website is down when it:
- does not answer within 10 seconds, or refuses the connection,
- answers with a server error (HTTP 5xx),
- serves a certificate that browsers refuse: expired, not covering the domain, not valid yet, or not trusted. A website on a Let's Encrypt staging certificate is not counted as down for being untrusted.
Any other answer, including redirects and 404, means the website is up.
Only public addresses, or the website's own server, are contacted. A domain that points at an internal address is reported as down instead of being checked, unless the panel allows private networks with VAULTPANEL_WEBHOOK_ALLOW_PRIVATE.
Only enabled websites with monitoring on are checked. A website with only wildcard domains has no address to check.
The Uptime card
The Uptime card on a website's Overview tab shows:
| Field | What it shows |
|---|---|
| Status | Up or Down, and for how long. |
| Message | The last result, such as HTTP 200 in 84 ms or the reason it is down. |
| Last 24 hours, Last 7 days, Last 30 days | Uptime as a percentage. |
| Response time | The average response time today. |
| Certificate served | When the certificate the site served expires. |
| Recent downtime | When each outage started, how long it lasted and why. |
Check now runs one check straight away, without the second try. Turn monitoring off stops the checks for this website, forgets its current state and ends any open downtime, so its alert resolves. Turn monitoring on starts them again.
The Website down alert
A built-in alert rule, Website down, fires while a website fails its uptime checks for 60 seconds, with severity critical. It works like any other alert rule: change its duration or severity, turn it off, and get it by email and webhook through the alert.firing and alert.resolved events.
- Email: tick An alert started firing under Alerts by email on Panel email. It is ticked by default.
- Webhooks: subscribe a webhook to
alert.firing.
Settings
Two settings in the panel's .env file (/opt/vaultpanel/.env on a panel set up by the installer) control the checks:
| Setting | Default | What it does |
|---|---|---|
VAULTPANEL_UPTIME_CHECK_SECONDS | 300 | How often each website is checked. At least 60 seconds, or 0 to turn regular checks off (Check now still works). |
VAULTPANEL_UPTIME_HISTORY_DAYS | 30 | How many days of check history the panel keeps, from 1 to 365. |
Restart the panel after changing them:
sudo vaultpanel restartGit deploy
Deploy static and PHP websites from a Git repository into release folders, with builds, environment variables, instant rollbacks and signed push-to-deploy webhooks.
App installer
Install WordPress, Joomla, Drupal or Laravel in a PHP website in one step, with its database and admin account, from the official release checked on download.