Jitsi releases often, and the Docker images make upgrading easy to do and easy to get wrong. The rule that prevents most breakage: the compose files and the image tags must come from the same release.
1. Read the release notes
Check the docker-jitsi-meet release notes for the target stable-NNNNN tag. Look for renamed or removed variables and changed defaults.
2. Back up
cd /opt/jitsi-meet
tar czf ~/jitsi-backup-$(date +%F).tgz .env docker-compose.yml *.yml config/On a cloud server, a disk snapshot is even better.
3. Download the new release’s files
NEW=stable-NNNNN # the release you are moving to
BASE=https://raw.githubusercontent.com/jitsi/docker-jitsi-meet/$NEW
curl -fsSLO $BASE/docker-compose.yml
curl -fsSL -o env.example.new $BASE/env.example
# Only if you use them:
curl -fsSLO $BASE/jibri.yml
curl -fsSLO $BASE/jigasi.yml4. Compare settings
diff <(grep -oE '^#?[A-Z_]+=' env.example.new | tr -d '#' | sort -u) \
<(grep -oE '^[A-Z_]+=' .env | sort -u)Lines only in the new example are new settings; decide whether you need them. Then pin the images:
JITSI_IMAGE_VERSION=stable-NNNNN5. Pull and restart
docker compose pull
docker compose down
docker compose up -d
docker compose psAdd -f jibri.yml and your other overlays to every command if you use them.
6. Test
- Three people in one room, cameras and screen share.
- A host login, if you use authentication or JWT.
- A short recording and a transcript, if enabled.
- Branding still applied (hard-refresh the browser).
7. Roll back if needed
docker compose down
tar xzf ~/jitsi-backup-YYYY-MM-DD.tgz
docker compose up -dBecause the old compose file still names the old tag, this returns you exactly to where you were.
Staying current without the work
Our platform pins every server to a tested release (currently stable-11031) and moves to newer ones only after they pass our deployment tests. If you run your own servers, our support plans include upgrades done and verified for you.