You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run Passbolt 4.9.1 server as a Docker container.
I want to disable SMTP configuration UI because I want to (re)configure as code the configuration on startup. So, I set PASSBOLT_PLUGINS_SMTP_SETTINGS_ENABLED=false environment variable as documented on https://www.passbolt.com/docs/hosting/configure/environment-reference/. SMTP configuration UI is well disabled.
But Passbolt API Status page could not be displayed anymore with this environment variable due to a "Could not validate entity smtpSettings." error.
A follow-up ticket was created on the internal tracker: PB-35690
Best regards
cedricalfonsi
changed the title
"Could not validate entity smtpSettings." on API status page when PASSBOLT_PLUGINS_SMTP_SETTINGS_ENABLED=false
[PB-35690] "Could not validate entity smtpSettings." on API status page when PASSBOLT_PLUGINS_SMTP_SETTINGS_ENABLED=false
Dec 12, 2024
Hi,
I run Passbolt 4.9.1 server as a Docker container.
I want to disable SMTP configuration UI because I want to (re)configure as code the configuration on startup. So, I set PASSBOLT_PLUGINS_SMTP_SETTINGS_ENABLED=false environment variable as documented on https://www.passbolt.com/docs/hosting/configure/environment-reference/. SMTP configuration UI is well disabled.
But Passbolt API Status page could not be displayed anymore with this environment variable due to a "Could not validate entity smtpSettings." error.
https://myhost/healthcheck.json?api-version=v2 returns a JSON with the only
smtpSettings.isEnabled
property but the entity requires["isEnabled", "areEndpointsDisabled", "errorMessage", "source", "isInDb"]
properties (see https://github.com/passbolt/passbolt_styleguide/blob/v4.9.1/src/shared/models/entity/healthcheck/associations/smtpSettingsEntity.js#L34).Healthcheck JSON :
Javascript stacktrace :
Regards.
The text was updated successfully, but these errors were encountered: