API v2 not compatible with browser extension v4 anymore - help to upgrade API needed

Installation Issues
1

Hi,

We were running Passbolt 2.7.1 via digital ocean image. Recently as you may know chrome update broke the web UI. We got around by downgrading the extension to an older version suggested on this forum.
Now, we’re trying to upgrade Passbolt digital ocean image v 2.7.1 to the latest Passbolt on docker.

Here are the steps I followed

  • I took a database dump as suggested in the upgrade guide
  • I copied files from /var/www/passbolt/config/gpg serverkey_private.asc serverkey.asc
  • I copied the server fingerprint from /var/www/passbolt/config/passbolt.php
  • I have the email attached to the key, which I got from gpg serverkey_private.asc command

I followed the upgrade guide for docker and came up with the below compose file

version: '3.9'
services:
  db:
    image: mariadb:10.10
    restart: unless-stopped
    environment:
      MYSQL_RANDOM_ROOT_PASSWORD: "true"
      MYSQL_DATABASE: "passbolt"
      MYSQL_USER: "passbolt"
      MYSQL_PASSWORD: "P4ssb0lt"
    volumes:
      - database_volume:/var/lib/mysql
      - ./db.sql:/docker-entrypoint-initdb.d/dump.sql

  passbolt:
    image: passbolt/passbolt:latest
    restart: unless-stopped
    depends_on:
      - db
    environment:
      APP_FULL_BASE_URL: [redact]
      DATASOURCES_DEFAULT_HOST: "db"
      DATASOURCES_DEFAULT_USERNAME: "passbolt"
      DATASOURCES_DEFAULT_PASSWORD: "P4ssb0lt"
      DATASOURCES_DEFAULT_DATABASE: "passbolt"
      PASSBOLT_GPG_SERVER_KEY_FINGERPRINT: "[redact]"
      PASSBOLT_KEY_EMAIL: "[redact]"
      EMAIL_TRANSPORT_DEFAULT_CLASS_NAME: "Smtp"
      EMAIL_DEFAULT_FROM: "[redact]"
      EMAIL_TRANSPORT_DEFAULT_HOST: "[redact]"
      EMAIL_TRANSPORT_DEFAULT_PORT: "587"
      EMAIL_TRANSPORT_DEFAULT_USERNAME: "[redact]"
      EMAIL_TRANSPORT_DEFAULT_PASSWORD: "[redact]"

    volumes:
      - ./gpg:/etc/passbolt/gpg
      - jwt_volume:/etc/passbolt/jwt
      - ./certs/certificate.key:/etc/ssl/certs/certificate.key:ro
      - ./certs/certificate.crt:/etc/ssl/certs/certificate.crt:ro
    command:
       [
         "/usr/bin/wait-for.sh",
         "-t",
         "0",
         "db:3306",
         "--",
         "/docker-entrypoint.sh"
       ]
    ports:
      - 80:80
      - 443:443

volumes:
  database_volume:
  jwt_volume:

But after running the above compose file, the old user can not still open the web ui but a new user (created after the upgrade) can do everything without any problems.

Please advise what we may be doing wrong? How can this be fixed?

This is what old user sees

image
image1919×904 5.88 KB

2

Hello @shahidcodes, welcome to the forum!

Does the old users have tried to clear their browser cache after the migration ?

3

I am one of the old users, I deleted everything for our passbolt domain from dev console > application and clear site data from settings

4

Can you share any logs from the passbolt container?
Migrating the gpg keys are not mendatory since in the v2 we were not storing anything in the database using the server gpg key so you can remove the PASSBOLT_GPG_SERVER_KEY_FINGERPRINT env variable.
Yourself and your users will see a message to indicate that the server keys changed but that is ok.

I am asking for the logs of the passbolt container because I want to know if the migrations (database modification) were executed

5

Any news @shahidcodes ?