Could not verify server key. Decryption failed

I have installed Passbolt on a Debian 9 server. My healtcheck is clean (details below). I get this error message when I try to make my first login to passbolt:

Could not verify server key. Decryption failed.

If I list my keys as the www-data user, I can see the one I have created with gpg. I have NOT set a passphrase for my current key (since it is defined like that in the tutorial). Although this is not my first key, since I have first time I have accidentically created my key with a passphrase, so I had to reset that. What I did is: cleaned up the keyrings and keys (removed the gnupg folder and removed the keys manually with the gpg --delete-keys). I am just mentioning this intermezzo, because it might have fucked up something.

So anyways, any help would be appreciated, I have read many posts but can’t advance from now on on my own.

Environment info:
– Debian 9.5
– Apache/2.4.25
– MariaDB 10.1.26-MariaDB-0+deb9u1 Debian 9.1
– PHP 7.0.30-0+deb9u1 (cli)
– Passbolt 2.3.0

Healthcheck:

 Healthcheck shell
---------------------------------------------------------------

 Environment

 [PASS] PHP version 7.0.30-0+deb9u1.
 [PASS] PCRE compiled with unicode support.
 [PASS] The temporary directory and its content are writable.
 [PASS] The public image directory and its content are writable.
 [PASS] The logs directory and its content are writable.
 [PASS] GD or Imagick extension is installed.
 [PASS] Intl extension is installed.
 [PASS] Mbstring extension is installed.

 Config files

 [PASS] The application config file is present
 [PASS] The passbolt config file is present

 Core config

 [FAIL] Debug mode is on.
  [HELP] Set debug = false; in config/passbolt.php
 [PASS] Cache is working.
 [PASS] Unique value set for security.salt
 [PASS] Full base url is set to https://kibupass.app
 [PASS] App.fullBaseUrl validation OK.
 [PASS] /healthcheck/status is reachable.

 SSL Certificate

 [PASS] SSL peer certificate validates
 [PASS] Hostname is matching in SSL certificate.
 [PASS] Not using a self-signed certificate

 Database

 [PASS] The application is able to connect to the database
 [PASS] 18 tables found
 [PASS] Some default content is present
 [PASS] The database schema up to date.

 GPG Configuration

 [PASS] PHP GPG Module is installed and loaded.
 [PASS] The server gpg key is not the default one
 [PASS] The environment variable GNUPGHOME is set to /var/www/.gnupg.
 [PASS] The directory /var/www/.gnupg containing the keyring is writable by the webserver user.
 [PASS] The public key file is defined in config/passbolt.php and readable.
 [PASS] The private key file is defined in config/passbolt.php and readable.
 [PASS] The server key fingerprint matches the one defined in config/passbolt.php.
 [PASS] The server public key defined in the config/passbolt.php is in the keyring.
 [PASS] There is a valid email id defined for the server key.
 [PASS] The public key can be used to encrypt a message.
 [PASS] The private key can be used to sign a message.
 [PASS] The public and private keys can be used to encrypt and sign a message.
 [PASS] The private key can be used to decrypt a message.
 [PASS] The private key can be used to decrypt and verify a message.
 [PASS] The public key can be used to verify a signature.

 Application configuration

 [PASS] Using latest passbolt version (2.3.0).
 [PASS] Passbolt is configured to force SSL use.
 [PASS] App.fullBaseUrl is set to HTTPS.
 [PASS] Selenium API endpoints are disabled.
 [PASS] Search engine robots are told not to index content.
 [PASS] Registration is closed, only administrators can add users.
 [PASS] Serving the compiled version of the javascript app
 [PASS] All email notifications will be sent.

  1 error(s) found. Hang in there!

I would like to mark this as solved.

I assume the problem was that the chrome plugin had the previous key cached maybe and I had to recover my account. After that, it worked.

@bigbadvolf yes that’s correct, performing a recover update the server key. Nice one figure it out!

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.