dankhostself-host anything

changedetection.io with Docker Compose

changedetection.io: website change detection, web page monitoring, and website change alerts, for tracking content changes, price drops, restock alerts, and website defacement. In the project's words: changedetection.io repository README checked 2026-09-25

Runs on: amd64, arm64, arm/v7, arm/v8 from each image's registry manifest, checked 2026-09-25; a CPU counts only if every image has a build for it. Image by image

Add changedetection.io to the builder to use your own domain and combine it with other apps in one file.

What changedetection.io needs

Only figures changedetection.io's own documentation publishes, each linked to the page it is on. Where the project gives no number, this page does not invent one.

ResourceMinimumRecommended
RAMThe project publishes no figure
CPUThe project publishes no figure
DiskThe project publishes no figure

On top of this, Caddy (the reverse proxy in the file) is a single small container.

Which hardware changedetection.io has images for

Read from each image's manifest list in its registry (anonymous, read-only) when this page was built. An app counts for a CPU only if every one of its images lists it.

  • x86-64 PC or NAS (linux/amd64): every image has a build.
  • Raspberry Pi 4/5, 64-bit OS (linux/arm64): every image has a build.
  • Raspberry Pi 3 or Zero 2 W, 32-bit OS (linux/arm/v7): every image has a build.
ServiceImagePlatforms in the manifestDigestRegistryChecked
changedetectionghcr.io/dgtlmoon/changedetection.ioamd64, arm64, arm/v7, arm/v8sha256:096dae27b5d677b89f0e810fff95a70403271aa3ff3b6437952d2db9be7e74c5ghcr.io2026-09-25

A manifest says an image exists for a CPU, not how well changedetection.io runs on it: a build for arm64 or arm/v7 can still be too slow or need more memory than the board has. The RAM and disk changedetection.io publishes are in the table above and, for a whole set of apps against a Raspberry Pi, on Will it run on my machine?. A tag like latest can move to a new digest after the date checked.

docker-compose.yml

This is exactly what the builder writes for changedetection.io alone on example.org: the official definition with its published ports removed and Caddy added in front.

# docker-compose.yml built at dankhost.com for: changedetection.io
# Each app block is its official compose definition. Only the names were prefixed with
# the app slug (services, containers, volumes, bind folders, .env variables) so any set of
# apps can share one file; other differences are listed under "Changed:" in each block.
# Only Caddy publishes ports. Secrets live in .env next to this file.

services:
  # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ----
  # Source: https://caddyserver.com/docs/running (checked 2026-09-23)
  # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23)
  # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly.
  caddy:
    image: "caddy:2"
    container_name: "caddy"
    restart: "unless-stopped"
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - "./caddy:/etc/caddy"
      - "caddy-data:/data"
      - "caddy-config:/config"
    networks:
      proxy:
        ipv4_address: "172.30.0.2"

  # ---- changedetection.io (watch.example.org) ----
  # Source: https://github.com/dgtlmoon/changedetection.io/blob/master/docker-compose.yml (checked 2026-09-25)
  # Source: https://github.com/dgtlmoon/changedetection.io/wiki/Running-changedetection.io-behind-a-reverse-proxy (checked 2026-09-25)
  # Changed: Removed the '127.0.0.1:5000:5000' port; Caddy reaches changedetection:5000 on the proxy network.
  #          Turned on two of the file's commented options: BASE_URL, your https address (added to notification alerts), and USE_X_SETTINGS=1, which makes it respect the proxy's X-Forwarded headers.
  changedetection:
    image: "ghcr.io/dgtlmoon/changedetection.io"
    container_name: "changedetection"
    hostname: "changedetection"
    volumes:
      - "changedetection-data:/datastore"
    environment:
      BASE_URL: "https://watch.example.org"
      USE_X_SETTINGS: "1"
    restart: "unless-stopped"
    networks:
      proxy: {}

networks:
  # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact.
  # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's
  # ipv4_address and in every trusted-proxy value to a free 172.x.0 range.
  proxy:
    ipam:
      config:
        - subnet: "172.30.0.0/24"
          ip_range: "172.30.0.128/25"
          gateway: "172.30.0.1"

volumes:
  caddy-data:
  caddy-config:
  changedetection-data:

Caddyfile save as caddy/Caddyfile

Caddy gets and renews the HTTPS certificate for watch.example.org by itself once the DNS record points at your server and ports 80 and 443 reach it.

# Caddyfile built at dankhost.com. Save it as ./caddy/Caddyfile next to docker-compose.yml.
# Caddy gets and renews a Let's Encrypt certificate for each name below by itself,
# once the DNS records point at this server and ports 80 and 443 reach it.

# changedetection.io
watch.example.org {
	reverse_proxy changedetection:5000
}

Already running nginx, Nginx Proxy Manager, Caddy or Traefik? The reverse-proxy settings changedetection.io needs, for all four, each cited to changedetection.io's own docs.

.env

changedetection.io needs no secret here; the builder adds nothing you have to fill in by hand.

# .env for changedetection.io, from dankhost.com/app/changedetection/. Nothing here is secret.
# Keep this file private (chmod 600).
# None of the chosen apps needs a variable here.

Changes from the official file

Besides prefixing every service, container, volume, folder and variable with changedetection (so any set of apps can share one file), these are all the differences from what the project documents:

  • Removed the '127.0.0.1:5000:5000' port; Caddy reaches changedetection:5000 on the proxy network.
  • Turned on two of the file's commented options: BASE_URL, your https address (added to notification alerts), and USE_X_SETTINGS=1, which makes it respect the proxy's X-Forwarded headers.

Notes for changedetection.io behind the proxy

  • changedetection.io has no password until you set one. Open https://watch.example.org at once and set one in its settings; until then anyone who finds the address can use it.
  • This file has no browser container, so pages are fetched with plain HTTP requests. Pages that need JavaScript need the optional Playwright/sockpuppetbrowser service from the repository's docker-compose.yml.

How to run it

  1. At your DNS provider, add an A record named watch on your domain pointing at the server's public IP address, and forward TCP 80, TCP 443 and UDP 443 to it.
  2. Save the three files in one folder: docker-compose.yml and .env side by side, the Caddyfile at ./caddy/Caddyfile. Replace example.org with your domain in the Caddyfile, the compose file and the .env, or let the builder do it.
  3. Nothing in .env needs filling in; chmod 600 .env all the same.
  4. Start it:
    docker compose up -d
    docker compose logs -f caddy   # watch the certificate arrive
  5. Open the new address (watch. plus your domain) in a browser and follow the notes above.

Back it up

changedetection.io publishes no backup procedure for the Docker setup. Everything, watches, history and settings, is in the /datastore volume; the copy below follows Docker's generic method with the app stopped.

Below is the BACKUP.md the builder writes next to the compose file above: which of its folders and volumes hold data, what to copy with which container stopped, and a restore check. Pick more apps in the builder and it covers them all in one file.

# BACKUP.md built at dankhost.com for: changedetection.io

What to copy from the docker-compose.yml built with this file, the database dump each project documents (rewritten for the service names in that file), what to copy with which container stopped, and how to check the result. Run every command in the folder that holds docker-compose.yml.

The folders are owned by the containers' users: put sudo in front of tar if it says "Permission denied". Named volumes live under /var/lib/docker/volumes, not next to the compose file, so they are copied through a throwaway ubuntu container (Docker's documented --volumes-from method). tar makes a full copy each run; for large folders an incremental tool (restic, borg, rsync) saves time and space.

Never run "docker compose down -v" on this file: it deletes the named volumes of every app in it.

## Before you start

    BACKUP=/mnt/backup/selfhost   # change this: a disk or machine other than this server's system disk
    mkdir -p "$BACKUP"

## Every time: the three stack files

    tar czf "$BACKUP/stack-files.tar.gz" docker-compose.yml .env caddy

.env holds the database passwords and secret keys the apps were set up with; keep this archive as private as the data.

## Caddy (the reverse proxy)

Caddy's docs: 'The data directory must not be treated as a cache.' It holds the TLS certificates and their private keys; without it Caddy has to ask Let's Encrypt for every certificate again.

- caddy-data (named volume, /data in caddy)
  BACK UP: TLS certificates, private keys, OCSP staples.
- caddy-config (named volume, /config in caddy)
  SKIP: the last active configuration, kept for 'caddy run --resume', which this setup does not use: it starts from the Caddyfile.
- ./caddy (/etc/caddy in caddy)
  IN stack-files.tar.gz: the Caddyfile, copied with the stack files above.

Copy (Caddy keeps serving while you copy):

    docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu tar cvf /backup/caddy-data.tar /data

Restore check:

    tar tf "$BACKUP/caddy-data.tar" > /dev/null && echo OK
    docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu bash -c "cd /data && tar xvf /backup/caddy-data.tar --strip 1"

Sources:
- Caddy docs: Conventions, Data directory: https://caddyserver.com/docs/conventions#data-directory (checked 2026-09-24)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-09-24)

## changedetection.io

changedetection.io publishes no backup procedure for the Docker setup. Everything, watches, history and settings, is in the /datastore volume; the copy below follows Docker's generic method with the app stopped.

What this compose mounts:
- changedetection-data (named volume, /datastore in changedetection)
  BACK UP: the whole datastore: watches, their snapshot history and settings.

1. Stop changedetection. Stopping it keeps the datastore from changing mid-copy.

    docker compose stop changedetection

2. Copy while changedetection is stopped:

    docker run --rm --volumes-from changedetection -v "$BACKUP":/backup ubuntu tar cvf /backup/changedetection-data.tar /datastore

3. Start it again:

    docker compose start changedetection

Restore check:

    tar tf "$BACKUP/changedetection-data.tar" > /dev/null && echo OK

Put a copy back (with changedetection stopped):

    docker run --rm --volumes-from changedetection -v "$BACKUP":/backup ubuntu bash -c "cd /datastore && tar xvf /backup/changedetection-data.tar --strip 1"

Stop it, put the changedetection-data volume back, start it.

Sources:
- changedetection.io repository: docker-compose.yml (BASE_URL, USE_X_SETTINGS): https://github.com/dgtlmoon/changedetection.io/blob/master/docker-compose.yml (checked 2026-09-25)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-09-25)

Update it

What docker compose pull does depends only on how each image line in the compose file above is tagged. For changedetection.io as this page writes it:

ServiceImageHow it is pinnedWhat docker compose pull does
caddycaddy:2Major version only (tag 2)Takes the newest image tagged 2: minor and patch releases of 2, never 3. A new major version needs a tag edit.
changedetectionghcr.io/dgtlmoon/changedetection.ioNot pinned: no tag, which means latestMoves to the newest image published as latest, which can be a new major version.

What changedetection.io's docs say about updating

changedetection.io's README, section "Updating changedetection.io", gives a docker run procedure (pull the image, kill and remove the old container, run it again) and, for Docker Compose, one line:

docker compose pull && docker compose up -d
  • That is the same pull and up -d as the steps below. The watches and their history are in the changedetection-data volume, so they stay when the container is replaced. The README sends you to the project's wiki for more.

Source: changedetection.io README: Updating changedetection.io checked 2026-10-01

The steps

  1. Back up first, as in Back it up above. An update can migrate changedetection.io's data on its first start; the copy is the way back.
  2. Download the new images. Running containers are not touched yet:
    docker compose pull
  3. Recreate the containers whose image changed. Volumes and bind-mounted folders stay as they are:
    docker compose up -d
  4. Watch changedetection.io start (Ctrl+C stops following the log, not the app):
    docker compose logs -f changedetection
  5. Optional: remove the old images the pull left without a tag. This covers every stack on the machine, not only this one:
    docker image prune

Docker's reference for these commands: Docker docs: docker compose pull checked 2026-09-30; Docker docs: docker compose up (recreates changed containers, keeps volumes) checked 2026-09-30; Docker docs: docker image prune checked 2026-09-30

Locked out? Reset the admin password

Removes the password, so you can set a new one in the Settings tab. changedetection.io has one optional password for the whole instance, not user accounts.

  1. Put a file called removepassword.lock in the data directory (/datastore in this file): Source: changedetection.io wiki: Password protection (Password reset) read 2026-10-03
    docker compose exec changedetection touch /datastore/removepassword.lock
  2. Restart it. It comes back with no password, open to anyone who reaches the address, so set a new one in Settings straight away. Source: changedetection.io wiki: Password protection (Password reset) read 2026-10-03; Docker docs: docker compose restart read 2026-10-03
    docker compose restart changedetection

Run the commands in the folder that holds docker-compose.yml. docker compose exec runs the command in the container that is already running: Docker docs: docker compose exec read 2026-10-03

Sources

Every page below was fetched on the date shown.

Add changedetection.io to the builder All one hundred apps

Made with AI tools. ยท Privacy