Umami

On a fresh MySQL deployment, the 05_add_visit_id migration fails, blocking all further migrations and startup.

Affects: self-hoster on MySQL

After updating to release 1.33 the Docker container fails to boot because npm-run-all cannot be found.

Affects: docker self-hoster

The user cannot open the Umami dashboard at all because a client-side formatjs error is thrown.

Affects: self-hoster

The user dislikes how analytics tools including Umami compute session duration: visitors who read one long article and leave count as a bounce, so duration cannot be measured for such sites.

Affects: publisher of long articles

In v3.0.1 the Last 24 hours and custom ranges shift timestamps by the timezone offset, so valid events fall outside the window; Realtime is correct and a UTC setting did not help.

Affects: self-hoster in a non-UTC timezone

Affects: Heroku deployer

Affects: self-hoster on Postgres

Affects: serverless deployers with large sites

Affects: docker self-hoster

Affects: arm64 self-hoster

Affects: Supabase and Vercel deployer

Affects: user tracking QR code scans

Affects: multi-site owner

Affects: self-hoster

Affects: new team creator

Affects: Vercel/Netlify with Supabase deployer

Affects: docker self-hoster

Affects: Postgres self-hoster

Affects: developer using the tracker API

Affects: self-hoster using pm2 and nginx

Affects: shared-hosting self-hoster

Affects: Railway self-hoster

Affects: Vercel deployer

Affects: new self-hoster

Affects: Heroku Postgres user

Affects: team migrating from Matomo

Affects: users from affected regions

Commenter highlights that the cloud version has an import feature that the self-hosted open-source version lacks, which matters when migrating from another analytics tool.

Affects: self-hoster migrating from Matomo

A user running a large site that bots crawl heavily would like Umami to track bot traffic so they can monitor it more closely.

Affects: operator of a 10m-page site

A self-hoster wants Umami to integrate with OIDC or a reverse-proxy auth check instead of its own non-bypassable login, so access can be managed in one place.

Affects: self-hoster with shared auth service

The requester wants Umami to read Cloudflare's visitor location headers to show cities and regions.

Affects: Cloudflare user

BASE_PATH is build-time only, so deploying Umami under a subpath requires maintaining a custom image rebuilt each release.

Affects: self-hoster behind reverse proxy

Affects: owner of multi-subdomain system

Affects: content site owner

Affects: docker-compose self-hoster

Affects: evaluator in European jurisdiction

Affects: solopreneur

Affects: team evaluating scale

Affects: JS and TypeScript developer

Affects: site owner with dynamic IP

A homelab user without public internet exposure cannot self-host Umami because it has to receive tracker requests from the internet, so they use a hosted pod instead.

Affects: homelab self-hoster

A government digital lead notes that self-hosted Umami avoids adblocker blocking by being loaded under a subdomain, unlike most SaaS analytics.

Affects: government digital service

A former user left Umami because after a pivot to cloud-first, self-hosting is no longer visible on the front page or mentioned on the pricing page.

Affects: self-hoster

After a server was compromised through a disclosed Next.js vulnerability, the author stopped running Umami even though the issue was patched, because it is built on Next.js.

Affects: self-hoster

A current user is considering switching to Plausible because of Umami's weak development quality, citing the site details page being broken for several days.