Hello, I’ve installed passbolt and on the installation wizard on step 3 when I have to create a GPG Key, I will get the message “The data entered are not correct: The public key cannot be used to encrypt.; The private key cannot be used to decrypt. Please note that passbolt does not support GPG key protected with a secret.”
Nginx Logs, System Healthcheck, Timezone and the Console Logs looks fine. I tried with different Browsers on different devices.
I’ve tried reinstalling the whole server, which has no effect on this error.
Can you help me? Or am I just too dump to set it up right?
I just tried to on ubuntu using CE installation scripts and I could not reproduce the issue. So this is an issue specific to your setup.
We have seen this issue before when the server and client time are not in sync. This error can happen when the client (browser) clock is ahead of the server. Can you double check you have NTP installed on the server and that the clock is set correctly?
Have played a litele did the install on ubuntu/centos/debian. It Allways stalls when we come to the Create a new GPG key for your server page.
““The data entered are not correct: The public key cannot be used to encrypt.; The private key cannot be used to decrypt. Please note that passbolt does not support GPG key protected with a secret.””
I am experiencing this on a fresh Ubuntu 18.04 install.
So far:
There was no MTA installed, but once installed I see there is a MySQL error being repeatedly reported Exception: SQLSTATE[HY000] [1045] Access denied for user ''@'localhost' (using password: NO) in [/var/www/passbolt/vendor/cakephp/cakephp/src/Database/Driver.php, line 92] But I can log into mariadb fine with the user/password combo being used in the wizard.
I’m using Firefox83 and the console is complaining about an inline script on the page, but I cannot find one yet
Coincidentally, my client machine was set to the wrong timezone, but its time was set to the correct time in a different timezone - so essentially putting it three hours into the future. The server was rebooted but otherwise nothing else changed. So it appears it was a timezone problem again. Working okay now.