# Root Role doesn't existe

**URL:** <https://community.passbolt.com/t/root-role-doesnt-existe/8064>\
**Category:** Installation Issues\
**Created:** [July 20, 2023, 10:21am UTC](https://community.passbolt.com/t/root-role-doesnt-existe/8064 "2023-07-20T10:21:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![inas](https://avatars.discourse-cdn.com/v4/letter/i/ad7895/32.png) [@inas](https://community.passbolt.com/u/inas)\
**Post date:** [July 20, 2023, 10:21am UTC](https://community.passbolt.com/t/root-role-doesnt-existe/8064/1 "2023-07-20T10:21:42Z")

</div>

Hello everyone,  
Actually, I’ve been reading this documentation ([Understanding the Passbolt rights model](https://community.passbolt.com/t/understanding-the-passbolt-rights-model/172)) and I’ve tried to check my database and didn’t find the root role in

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/passbolt/original/2X/b/bf9d8bd7c2fa55e01eca6ac10ec9a33f3bc22e73.png)

And I want how can I add it and solve this issues, or is it normal to not having a root role now.

---

<div class="post-metadata">

**Author:** ![pabloelcolombiano](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.passbolt.com/pabloelcolombiano/32/5864_2.png) [@pabloelcolombiano](https://community.passbolt.com/u/pabloelcolombiano)\
**Post date:** [July 20, 2023, 10:24am UTC](https://community.passbolt.com/t/root-role-doesnt-existe/8064/2 "2023-07-20T10:24:25Z")

</div>

Hello @inas ,

yes it is normal not to have the `root` role in the `roles` table. If you are seeing a FAIL in the healtchcheck, you are probaby using the 4.1.0 version. Upgrading to 4.1.1 would fix the healtchcheck.

---

<div class="post-metadata">

**Author:** ![inas](https://avatars.discourse-cdn.com/v4/letter/i/ad7895/32.png) [@inas](https://community.passbolt.com/u/inas)\
**Post date:** [July 20, 2023, 10:28am UTC](https://community.passbolt.com/t/root-role-doesnt-existe/8064/3 "2023-07-20T10:28:16Z")

</div>

Yes I use 4.1.1 version, and that was the healthchek :

> Environment
> 
> [PASS] PHP version 8.1.2-1ubuntu2.13.  
> [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.
> 
> 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://10.254.61.74](https://10.254.61.74)  
> [PASS] App.fullBaseUrl validation OK.  
> [PASS] /healthcheck/status is reachable.
> 
> SSL Certificate
> 
> [FAIL] SSL peer certificate does not validate  
> [FAIL] Hostname does not match when validating certificates.  
> [WARN] Using a self-signed certificate  
> [HELP] Check [Passbolt Help | Troubleshoot SSL](https://help.passbolt.com/faq/hosting/troubleshoot-ssl)  
> [HELP] cURL Error (60) SSL certificate problem: self-signed certificate
> 
> Database
> 
> [PASS] The application is able to connect to the database  
> [PASS] 32 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 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 server OpenPGP key is not the default one  
> [PASS] The public key file is defined in /var/www/passbolt/config/passbolt.php and readable.  
> [PASS] The private key file is defined in /var/www/passbolt/config/passbolt.php and readable.  
> [PASS] The server key fingerprint matches the one defined in /var/www/passbolt/config/passbolt.php.  
> [PASS] The server public key defined in the /var/www/passbolt/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.
> 
> Application configuration
> 
> [PASS] Using latest passbolt version (4.1.1).  
> [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.  
> [INFO] The Self Registration plugin is enabled.  
> [INFO] Registration is closed, only administrators can add users.  
> [PASS] The deprecated self registration public setting was not found in /var/www/passbolt/config/passbolt.php.  
> [WARN] Host availability checking is disabled.  
> [HELP] Make sure this instance is not publicly available on the internet.  
> [HELP] Or set the PASSBOLT\_EMAIL\_VALIDATE\_MX environment variable to true.  
> [HELP] Or set passbolt.email.validate.mx to true in /var/www/passbolt/config/passbolt.php.  
> [PASS] Serving the compiled version of the javascript app.  
> [WARN] Some email notifications are disabled by the administrator.
> 
> JWT Authentication
> 
> [PASS] The JWT Authentication plugin is enabled  
> [PASS] The /var/www/passbolt/config/jwt/ directory is not writable.  
> [PASS] A valid JWT key pair was found
> 
> SMTP Settings
> 
> [PASS] The SMTP Settings plugin is enabled.  
> [PASS] SMTP Settings coherent. You may send a test email to validate them.  
> [PASS] The SMTP Settings source is: database.  
> [WARN] The SMTP Settings plugin endpoints are enabled.  
> [HELP] It is recommended to disable the plugin endpoints.  
> [HELP] Set the PASSBOLT\_SECURITY\_SMTP\_SETTINGS\_ENDPOINTS\_DISABLED environment variable to true.  
> [HELP] Or set passbolt.security.smtpSettings.endpointsDisabled to true in /var/www/passbolt/config/passbolt.php.
> 
> [FAIL] 2 error(s) found. Hang in there!

---

<div class="post-metadata">

**Author:** ![pabloelcolombiano](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.passbolt.com/pabloelcolombiano/32/5864_2.png) [@pabloelcolombiano](https://community.passbolt.com/u/pabloelcolombiano)\
**Post date:** [July 20, 2023, 10:31am UTC](https://community.passbolt.com/t/root-role-doesnt-existe/8064/4 "2023-07-20T10:31:56Z")

</div>

It looks all good, as far as the `roles` is concerned 🙂
