Getting updates
Update a self-hosted Umami installation from source or with Docker, and refresh PostgreSQL statistics after a major upgrade.
Source code#
Make sure you are in the Umami project directory before running these commands.
Pull the latest changes from the Git repository:
Install any new or updated dependencies:
Rebuild the project:
Finally, restart the application:
If you are using a process manager like PM2, restart the process instead:
Docker#
Pull the latest image:
Then restart your container to use the new image.
If you are using Docker Compose, pull the latest image and recreate the containers:
Upgrading to v3.5.0#
Check the following before you upgrade to v3.5.0:
- Set
APP_SECRET. Umami no longer falls back toDATABASE_URLwhenAPP_SECRETis missing, and will not start without it. The bundled Docker Compose file also refuses to start without it. If you never set it, see APP_SECRET for how to keep existing logins and sessions working. - Use Node.js 20.19 or newer. Node.js 22 LTS is recommended. This only applies when installing from source. The Docker image includes its own Node.js.
- Password changes have moved from Settings > Profile to Settings > Security.
- The default password must be replaced. If the
adminaccount still uses the default password, you are asked to change it the next time you log in. - The public
/api/configendpoint has been removed.
This release adds the 27_add_error_tracking PostgreSQL migration for error tracking.
It runs automatically during pnpm build and when the Docker container starts.
Refresh database statistics after upgrading#
Major upgrades (such as moving to v3) run schema migrations that can leave PostgreSQL's query planner with stale statistics, making dashboard queries slower than expected on large instances. Run ANALYZE to refresh them:
This is safe to run on a live database and completes quickly. Afterward, dashboard queries should return to their expected speed.