I recently restored our database from backup and whenever we land on the landing page we are presented the recovery wizard> recovery works sigh out and go to log in again have to recover again.
Hi @ganosh Welcome to the forum!
Please provide version details for OS, passbolt, browser extension, php, NGINX, and run the healthcheck if you can, thanks.
[PASS] PHP version 7.4.3.
[PASS] PCRE compiled with unicode support.
[PASS] The temporary directory and its content are writable and not executable.
[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.
[PASS] The application config file is present
[PASS] The passbolt config file is present
[PASS] Debug mode is off.
[PASS] Cache is working.
[PASS] Unique value set for security.salt
[PASS] Full base url is set to https://*****
[PASS] App.fullBaseUrl validation OK.
[PASS] /healthcheck/status is reachable.
[PASS] SSL peer certificate validates
[PASS] Hostname is matching in SSL certificate.
[WARN] Using a self-signed certificate
[HELP] Check Passbolt Help | Troubleshoot SSL
[PASS] The application is able to connect to the database
[PASS] 26 tables found
[PASS] Some default content is present
[PASS] The database schema up to date.
[PASS] PHP GPG Module is installed and loaded.
[PASS] The environment variable GNUPGHOME is set to /var/lib/passbolt/.gnupg.
[PASS] The directory /var/lib/passbolt/.gnupg containing the keyring is writable by the webserver user.
[PASS] The server OpenPGP key is not the default one
[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 (or environment variables) 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.
[PASS] The server public key format is Gopengpg compatible.
[PASS] The server private key format is Gopengpg compatible.
[FAIL] Could not connect to passbolt repository to check versions It is not possible check if your version is up to date.
[HELP] Check the network configuration to allow this script to check for updates.
[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] All email notifications will be sent.
[PASS] The JWT Authentication plugin is enabled
[PASS] The /etc/passbolt/jwt/ directory is not writable.
[PASS] A valid JWT key pair was found
Never mind the migration portion. Fresh install on the same server I am getting the same issue, blank database new keys.
log into mysql drop tables
is there another component or files I need to remove for this to stop?
The extension does not display the sign-in form if the url is not recognized as the one used to setup/recover an account.
Can you confirm that your
/etc/passbolt/passbolt.conf doesn’t contain an
App.fullBaseUrl with a trailing slash.
Could you provide us with the browser extension debug log:
New tab > go to chrome://extensions > look for passbolt card > details > inspect views section > click index.html > unfold and copy errors under console tab
New tab > go to about:debugging#/runtime/this-firefox > look for passbolt card > Click inspect > unfold and copy errors under console tab
There is no /etc/passbolt/passbolt.conf
I have passbolt.php on a hunch I added the missing trailing “/” and now it works as expected
after one last recovery in both firefox and edge was needed
I also removed the “/” and it is now working as expected.
@ganosh Good to hear! That’s correct - he meant