Updating gone wrong

[ElbeufTech]

Hi,

We've been trying to update Teampass from 3.2.1.5 to latest (using docker) and it results in the upgrade.php not existing, so it goes back to reinstalling a fresh Teampass.

Anyone has the solution for this ? I've tried what is shown in the documentation but I can't do anything.

[nilsteampassnet]

Hi @ElbeufTech,

Could you please open a dedicated issue for this? As this was posted in the Discussions section, tracking it via an issue makes it much easier to follow up.
When creating the issue, please include the details requested in the issue template, as well as the following information:

Before anything else: please do not complete the installation wizard against your existing database, and take a backup of the database and of the secrets volume/directory now. A fresh install would not reuse your current encryption key.

Your description and your screenshot point to two different situations (being sent to the installer vs. an HTTP 500 on /install/upgrade.php), so I need a bit more context to tell which one applies:

Image and upgrade procedure

• The image actually used by your stack: docker compose config | grep image
• The exact commands you ran to upgrade (pull, down/up, --force-recreate, …)

Persistence

• The volumes: section of your TeamPass service. In particular, are /var/www/html/storage/config and /var/www/html/secrets mounted (named volumes or bind mounts)? Were they already mounted on 3.2.1.5?

Logs

• The container startup log right after the upgrade: docker compose logs teampass | head -80
  (the lines showing Version:, "already configured" / "not configured yet", and the database upgrade / install directory messages are the important ones)
• The PHP error behind the HTTP 500: reload /install/upgrade.php, then run docker compose logs --tail 50 teampass

Feel free to mask passwords and hostnames.

Thanks!