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
When spinning up a Laravel project, the following error appears in the Laravel log:
1. PLATFORM_PROJECT_ENTROPY must be a 32+ char base64 encoded string
production.ERROR: The only supported ciphers are AES-128-CBC and AES-256-CBC with the correct key lengths. {"exception":"[object] (RuntimeException(code: 0): The only supported ciphers are AES-128-CBC and AES-256-CBC with the correct key lengths. at /app/vendor/laravel/framework/src/Illuminate/Encryption/Encrypter.php:43)
Updating the hard coded value of PLATFORM_PROJECT_ENTROPY in integrations/lando-platformsh/lib/run.js with a base64 encoded 32 character string resolves it however we need to determine if it's OK to hard code or if we need to use or generate it another way.
On the first time the site is started, it complains that the redis extension is not installed. The line exists in the php.ini file at the root of the project however and a lando restart resolves the issue.
I suspect a race condition where the extension definition is not in place before the first start of the appserver.
The text was updated successfully, but these errors were encountered:
When spinning up a Laravel project, the following error appears in the Laravel log:
1. PLATFORM_PROJECT_ENTROPY must be a 32+ char base64 encoded string
Updating the hard coded value of
PLATFORM_PROJECT_ENTROPY
inintegrations/lando-platformsh/lib/run.js
with a base64 encoded 32 character string resolves it however we need to determine if it's OK to hard code or if we need to use or generate it another way.2. Redis extension missing on first start
On the first time the site is started, it complains that the redis extension is not installed. The line exists in the
php.ini
file at the root of the project however and alando restart
resolves the issue.I suspect a race condition where the extension definition is not in place before the first start of the appserver.
The text was updated successfully, but these errors were encountered: