# Users/Recover failed with internal Error **URL:** \ **Category:** Installation Issues\ **Created:** [May 28, 2018, 2:26pm UTC](https://community.passbolt.com/t/users-recover-failed-with-internal-error/724 "2018-05-28T14:26:31Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![vig](https://avatars.discourse-cdn.com/v4/letter/v/8797f3/32.png) [@vig](https://community.passbolt.com/u/vig)\ **Post date:** [May 28, 2018, 2:26pm UTC](https://community.passbolt.com/t/users-recover-failed-with-internal-error/724/1 "2018-05-28T14:26:31Z")
![Screenshot_20180528_162748](https://canada1.discourse-cdn.com/flex031/uploads/passbolt/original/1X/ae0c9f04dede2848dd4794cba4fca1fd77f2908f.png) Hi all, I’ve just finished to install the 2.0.7 passbolt version on a new server. I restore the database from the 1.6.9 , and follow the Upgrade Tutorial. > ## Healthcheck shell Environment [PASS] PHP version 7.0.27-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 [PASS] Debug mode is off. [PASS] Cache is working. [PASS] Unique value set for security.salt [PASS] Full base url is set to [https://myserver.fr](https://myserver.fr) [PASS] App.fullBaseUrl validation OK. [PASS] /healthcheck/status is reachable. SSL Certificate [PASS] SSL peer certificate validates [PASS] Hostname is matching in SSL certificate. [WARN] Using a self-signed certificate Database [PASS] The application is able to connect to the database [PASS] 23 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 public key can be used to sign a message. [PASS] The public key 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.0.7). [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. No error found. Nice one sparky! \< Unfortunately, i can’t recover any account, with error message " You are not authorized to access that location , An internal error has occured" . Can’t understand what’s happening ? Cheers Val ---
**Author:** ![remy](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.passbolt.com/remy/32/17_2.png) [@remy](https://community.passbolt.com/u/remy)\ **Post date:** [May 28, 2018, 2:40pm UTC](https://community.passbolt.com/t/users-recover-failed-with-internal-error/724/2 "2018-05-28T14:40:32Z")
Can you check if there is more information in logs/error.log (from your passbolt directory). Check also if the database table encoding / collation is set properly, this is a common issue with the upgrade: > [@Error after upgrade from 1.6.10 to 2.0.7](https://community.passbolt.com/t/error-after-upgrade-from-1-6-10-to-2-0-7/661): > > Checklist [x] I have read intro post: [About the Installation Issues category](https://community.passbolt.com/t/about-the-installation-issues-category/12) [x] I have read the tutorials, help and searched for similar issues [x] I provide relevant information about my server (component names and versions, etc.) [x] I provide a copy of my logs and healthcheck [x] I describe the steps I have taken to trouble shoot the problem [x] I describe the steps on how to reproduce the issue Hi. I’ve just upgrade my passbolt from 1.6.10 to 2.0.7. I’m running it on Debian 8, Apache… ---
**Author:** ![vig](https://avatars.discourse-cdn.com/v4/letter/v/8797f3/32.png) [@vig](https://community.passbolt.com/u/vig)\ **Post date:** [May 28, 2018, 2:52pm UTC](https://community.passbolt.com/t/users-recover-failed-with-internal-error/724/3 "2018-05-28T14:52:51Z")
Hi Remy, Thank you for your very quick reply. logs are speaking ! 2018-05-28 14:05:40 Error: [InvalidArgumentException] Invalid header value type; must be a string or numeric; received boolean Request URL: /healthcheck/status.json 2018-05-28 14:07:13 Error: [PDOException] SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘Gpgkeys.armored\_key’ in ‘field list’ Request URL: /auth/verify.json?api-version=v1 2018-05-28 14:10:15 Error: [PDOException] SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘Gpgkeys.armored\_key’ in ‘field list’ Ok , errors with the database. As “JPMDWX” I’ve dropped my schema and imported it again from backup. Then, I ran the migration script and now is working fine!! Thanks a lot for all your help!!! Best regards ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex031/uploads/passbolt/original/2X/b/bee7d3f9329f668000d46e9fcb2e5db1e9d31348.svg) [@system](https://community.passbolt.com/u/system)\ **Post date:** [June 2, 2018, 3:01pm UTC](https://community.passbolt.com/t/users-recover-failed-with-internal-error/724/4 "2018-06-02T15:01:06Z")
Closed on June 2, 2018, 3:01pm UTC This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.