Healthchecks

Cron job monitor that alerts you when a scheduled task stops checking in

  • ghcr.io/hsinghhira/healthchecks:1.0.1
  • v5.0.3
  • Updated 21 Nov 2026
  • port 6773
  • amd64 · arm64
  • Networking
  • 10.5k stars

Screenshots

Healthchecks screenshot 1: My checksHealthchecks screenshot 2: Check detailsHealthchecks screenshot 3: Cron schedule

Open the app

Web UI

http://localhost:6773/

API docs

http://localhost:6773/docs/api/

About Healthchecks

Healthchecks watches your scheduled jobs: backups, cron jobs, scripts. Each job calls its own ping URL when it runs. When a ping does not come in on time, Healthchecks tells you by email, ntfy, Telegram, Discord, Slack and many more. It uses a built-in SQLite database, so it is one container with nothing else to set up.

Features

  • A ping URL for every job, with simple or cron schedules
  • Grace time before an alert goes out
  • Start, success and failure signals, and run times
  • Alerts to more than 25 services, plus webhooks
  • Projects, teams and read-only badges
  • A full API and Prometheus metrics

How to use

  1. Open Healthchecks from your dashboard.
  2. Sign in with the email and the password from the app's logs (the box marked CREDENTIALS).
  3. Click Add Check and set how often the job runs.
  4. Copy its ping URL into your job, like curl at the end of a script.
  5. Add where alerts go in Integrations.

Before you install

Set SITE_ROOT to http://[ZIMAOS-IP-ADDRESS]:6773 with your ZimaOS IP in place of [ZIMAOS-IP-ADDRESS]: the ping URLs your jobs call are made from it. The first account is ADMIN_EMAIL ([email protected] unless you change it) with a password made on first start, shown in the app's logs in the box marked CREDENTIALS and saved in /DATA/AppData/healthchecks/data/.admin_password. Email, the alert services and the other settings are in the Variables tab and are added in the app settings. It is ready in about a minute.

The settings in the first table are already in the app settings. To use any other one, open the app settings, add the variable with your value, save, and the app restarts with it. A setting you leave out uses its default.

In the app settings

VariableDefault valueDescription
TZ$TZYour time zone. It is filled in from your ZimaOS time zone.
SITE_ROOThttp://[ZIMAOS-IP-ADDRESS]:6773The address you open Healthchecks at. Replace [ZIMAOS-IP-ADDRESS] with your ZimaOS IP, like http://192.168.1.20:6773. The ping URLs your cron jobs call are made from it.
SITE_NAMEHealthchecksThe name shown at the top of the page and in alerts.
ADMIN_EMAIL[email protected]The email you sign in with. Only used when the first account is made.
ADMIN_PASSWORD—The first account's password. Leave it empty and one is made for you: it is shown in the app's logs, in the box marked CREDENTIALS. Only used when the first account is made.
REGISTRATION_OPENFalseSet to True so anyone who can open Healthchecks can sign up (sign-up needs email to be set up).

Server

VariableDefault valueDescription
ALLOWED_HOSTS*The names Healthchecks answers to, comma separated. * allows any.
PING_ENDPOINT—The start of ping URLs. Leave it out to use SITE_ROOT/ping/.
PING_BODY_LIMIT10000How much of a ping's body to keep, in bytes.
SITE_LOGO_URL—A link to your own logo.
SECRET_KEY—The key sessions are signed with. It is made on first start and kept in /data/secrets.env. Only set it to use your own.
REMOTE_USER_HEADER—Sign in from a header a proxy sets, like HTTP_REMOTE_EMAIL.
SECURE_PROXY_SSL_HEADER—Set to HTTP_X_FORWARDED_PROTO,https behind an https reverse proxy.
INTEGRATIONS_ALLOW_PRIVATE_IPSFalseSet to True so webhooks can call addresses on your own network.

Email (SMTP)

VariableDefault valueDescription
DEFAULT_FROM_EMAIL[email protected]The address emails are sent from.
EMAIL_HOST—Your email server, like smtp.gmail.com, for alerts and sign-in links.
EMAIL_PORT587Your email server port, usually 587 or 465.
EMAIL_HOST_USER—The user name for your email server.
EMAIL_HOST_PASSWORD—The password for your email server.
EMAIL_USE_TLSTrueUse STARTTLS (port 587).
EMAIL_USE_SSLFalseSet to True for SSL (port 465).
EMAIL_USE_VERIFICATIONTrueAsk people to confirm an email address before alerts go to it.
SMTPD_PORT—Set a port, like 2525, to accept pings by email (also publish it).

Alerts

VariableDefault valueDescription
APPRISE_ENABLEDFalseSet to True to send alerts through Apprise.
SHELL_ENABLEDFalseSet to True to run shell commands as alerts.
NTFY_SH_TOKEN—Your ntfy.sh access token.
TELEGRAM_BOT_NAMEExampleBotYour Telegram bot's name.
TELEGRAM_TOKEN—Your Telegram bot's token.
DISCORD_CLIENT_ID—Discord app client ID.
DISCORD_CLIENT_SECRET—Discord app client secret.
SLACK_CLIENT_ID—Slack app client ID (plain Slack webhooks work without it).
SLACK_CLIENT_SECRET—Slack app client secret.
MATRIX_HOMESERVER—Your Matrix server, like https://matrix.org.
MATRIX_USER_ID—The Matrix bot user, like @bot:matrix.org.
MATRIX_ACCESS_TOKEN—The Matrix bot's access token.
PUSHOVER_API_TOKEN—Your Pushover app token.
PUSHOVER_SUBSCRIPTION_URL—Your Pushover subscription URL.
SIGNAL_CLI_SOCKET—The signal-cli socket, for Signal alerts.
TWILIO_ACCOUNT—Twilio account SID, for SMS and calls.
TWILIO_AUTH—Twilio auth token.
TWILIO_FROM—The Twilio number to send from.
PROMETHEUS_ENABLEDTrueSet to False to hide the Prometheus metrics option.
docker-compose.yml
name: healthchecks

services:
  healthchecks:
    image: ghcr.io/hsinghhira/healthchecks:1.0.1
    container_name: healthchecks
    restart: unless-stopped
    stop_grace_period: 30s
    network_mode: bridge
    environment:
      - TZ=$TZ
      - SITE_ROOT=http://[ZIMAOS-IP-ADDRESS]:6773
      - SITE_NAME=Healthchecks
      - [email protected]
      - ADMIN_PASSWORD=
      - REGISTRATION_OPEN=False
    ports:
      - target: 8000
        published: "6773"
        protocol: tcp
    volumes:
      - type: bind
        source: /DATA/AppData/$AppID/data
        target: /data
        bind:
          create_host_path: true
    healthcheck:
      test: ["CMD", "/opt/healthchecks/fetchstatus.py"]
      interval: 30s
      timeout: 10s
      retries: 5
      start_period: 120s
    deploy:
      resources:
        limits:
          cpus: "1.00"
          memory: 512M
        reservations:
          cpus: "0.05"
          memory: 128M
    labels:
      icon: https://cdn.jsdelivr.net/gh/HSinghHira/IceStore@main/Apps/healthchecks/icon.png
    x-casaos:
      id: com.icestore.healthchecks
      envs:
        - container: TZ
          description:
            en_US: >-
              Your time zone. It is filled in from your ZimaOS time zone.
        - container: SITE_ROOT
          description:
            en_US: >-
              The address you open Healthchecks at. Replace
              [ZIMAOS-IP-ADDRESS] with your ZimaOS IP, like
              http://192.168.1.20:6773. The ping URLs your cron jobs call
              are made from it.
        - container: SITE_NAME
          description:
            en_US: >-
              The name shown at the top of the page and in alerts.
        - container: ADMIN_EMAIL
          description:
            en_US: >-
              The email you sign in with. Only used when the first account
              is made.
        - container: ADMIN_PASSWORD
          description:
            en_US: >-
              The first account's password. Leave it empty and one is made
              for you: it is shown in the app's logs, in the box marked
              CREDENTIALS. Only used when the first account is made.
        - container: REGISTRATION_OPEN
          description:
            en_US: >-
              Set to True so anyone who can open Healthchecks can sign up
              (sign-up needs email to be set up).
      ports:
        - container: "8000"
          description:
            en_US: Healthchecks web UI, ping URLs and API, published on host as 6773
      volumes:
        - container: /data
          description:
            en_US: >-
              The SQLite database with your checks and their history, and
              this install's own keys (secrets.env, .admin_password). Back
              it up.

x-casaos:
  id: com.icestore.healthchecks
  architectures:
    - amd64
    - arm64
  main: healthchecks
  author: HSinghHira
  category: Networking
  developer: Healthchecks.io
  icon: https://cdn.jsdelivr.net/gh/HSinghHira/IceStore@main/Apps/healthchecks/icon.png
  thumbnail: https://cdn.jsdelivr.net/gh/HSinghHira/IceStore@main/Apps/healthchecks/screenshot-1.png
  screenshot_link:
    - https://cdn.jsdelivr.net/gh/HSinghHira/IceStore@main/Apps/healthchecks/screenshot-1.png
    - https://cdn.jsdelivr.net/gh/HSinghHira/IceStore@main/Apps/healthchecks/screenshot-2.png
    - https://cdn.jsdelivr.net/gh/HSinghHira/IceStore@main/Apps/healthchecks/screenshot-3.png
  title:
    en_US: Healthchecks
  tagline:
    en_US: Cron job monitor that alerts you when a scheduled task stops checking in
  description:
    en_US: >-
      Healthchecks watches your scheduled jobs: backups, cron jobs, scripts.
      Each job calls its own ping URL when it runs. When a ping does not
      come in on time, Healthchecks tells you by email, ntfy, Telegram,
      Discord, Slack and many more. It uses a built-in SQLite database, so
      it is one container with nothing else to set up.


      **Features**


      - A ping URL for every job, with simple or cron schedules

      - Grace time before an alert goes out

      - Start, success and failure signals, and run times

      - Alerts to more than 25 services, plus webhooks

      - Projects, teams and read-only badges

      - A full API and Prometheus metrics


      **How to use?**


      1. Open Healthchecks from the ZimaOS dashboard.

      2. Sign in with the email and the password from the app's logs (the
         box marked CREDENTIALS).

      3. Click Add Check and set how often the job runs.

      4. Copy its ping URL into your job, like curl at the end of a
         script.

      5. Add where alerts go in Integrations.
  tips:
    before_install:
      en_US: >-
        1. Set SITE_ROOT: replace [ZIMAOS-IP-ADDRESS] with your ZimaOS IP.
           The ping URLs are made from it, so your other machines can reach
           them.


        2. More settings, like email and the alert services, are listed on
           the Healthchecks page at
           https://icestore.hsinghhira.me/app/healthchecks/ (Variables tab).
           You can add them now or later in the app settings.


        3. Start the installation. It is ready in about a minute.


        4. Open the app's logs. Find the box marked CREDENTIALS. It has the
           email and password.


        5. Open http://[ZIMAOS-IP-ADDRESS]:6773 and sign in.
  index: /
  port_map: "6773"
  scheme: http
  is_uncontrolled: false
  version: "v5.0.3"
  update_at: "2026-11-21"
  release_notes:
    en_US: |-
      - First IceStore release, on port 6773
      - Built on healthchecks/healthchecks v5.0.3, with SQLite as the database
      - Each install makes its own SECRET_KEY and admin password on first start; the login is in the CREDENTIALS box in the logs
      - Fixed: the admin account was not made on first start ("unrecognized arguments: --no-input --username admin").
      - The store now names the exact image version (1.0.1), so a new install downloads the fixed image instead of reusing an older one ZimaOS kept.
  repo: "https://github.com/healthchecks/healthchecks"
  support: "https://github.com/healthchecks/healthchecks/issues"
  docs: "https://healthchecks.io/docs/self_hosted_configuration/"

Install Healthchecks

Something not working with Healthchecks?

Report it so it gets fixed, or ask for an app that is not here yet.

More Networking apps

See all