Try or ByeTry or Bye

Self-Hosted Plausible CE Not Recording Pageviews

Workaround available Self-hosted (Docker) Updated October 21, 2026

Quick answer

After a Community Edition upgrade, pageviews can stop because ClickHouse migrations or settings didn't apply. Check the plausible and ClickHouse container logs, back up, and follow each major version's upgrade notes; rolling back restores logging while you fix it.

Most likely fix: Read the logs.

Symptoms

Dashboard shows no new visits after an upgrade, ClickHouse logs show missing-column errors, or the container restarts.

Why it happens

  • Skipped or failed migrations between major versions
  • ClickHouse version or configuration not matching the release (v3 uses ClickHouse 24.12 and CLICKHOUSE_SKIP_USER_SETUP=1 in its compose file)
  • Old hosting repo layout instead of the community-edition compose setup
  • Proxy not forwarding the visitor IP

How to fix it

Try these in order — the most common fix is first.

  1. 1. Read the logs

    1. Run docker compose logs plausible
    2. Check the ClickHouse container logs with docker compose logs
    3. Look for migration or missing-column errors

  2. 2. Upgrade in stages with backups

    1. Back up Postgres and ClickHouse volumes
    2. Upgrade one major version at a time following the release notes
    3. Use the community-edition compose file for the target version
    4. Check health after each step

  3. 3. Roll back if needed

    1. Restore the previous image tag and your backups
    2. Confirm pageviews log again
    3. Retry the upgrade after fixing the config

This guide also covers

  • plausible self hosted not working
  • plausible ce upgrade clickhouse error
  • plausible community edition not recording

Still not working?

If Plausible Analytics keeps failing, you're not alone. See every Plausible Analytics problem users report or the alternatives people switch to.

Other Plausible Analytics errors