So after a server update, it seemed that there were some unintentional changes. And unfortunately backups weren’t working. Go figure. Lessons learnt there.
Anyway, so randomly, well not so after some investigation. Our public/private key had expired. Due to following instructions for setup back in 2017. Anyway, so we extended the expired public key etc to no longer expire. Removed the .gnupg directory from the web servers home directory, and reinitialized it with the new key without the expiry.
Anyway, now I can’t recover my account. I can initiate my account recovery, but I can’t actually recover my account. When I select my correct private key, it doesn’t recognize the account.
Any hints? Or is it possible to just create a new account and reassign everything to it?
We had the same issue. I believe the “This key doesn’t match any account.” is a bug in the Chrome extension (I have at least one report that the Firefox extension wasn’t affected by this). As far as I understand it. the extension is supposed to query the server whether the key belongs to a known user in the database, but as far as I could tell, it didn’t actually query the server. There was no request in the Chrome inspector, and no request in the server’s access.log.
The workaround is to reinstall the extension; the recovery worked afterwards. Make sure you have your passbolt_private.asc key backup ready before you remove the extension, because uninstalling the extension without having a backup will make you lose your private key.