Testing: Update to v4 crashes, on RaspberryPi4

It could be that the issue came from upgrading PHP. Did you have to do so?

In any case you can check this post:

I edtited the nginx config file as follows:
sudo nano /etc/nginx/sites-enabled/nginx-passbolt.conf

and changed that line

fastcgi_pass unix:/run/php/php8.2-fpm.sock;

to ensure that the php version was correct.
The php version is displayed by running
php -v

I run on PHP 8.2.6, so it needed unix:/run/php/php8.2-fpm.sock;

After that, restart nginx
sudo systemctl restart nginx

and the 502 disapeared. Does this fix the issue on your side?

We released v4.0.2, so you may want to set back /etc/apt/sources.list.d/passbolt.sources to stable.

1 Like

Hello @pabloelcolombiano. Thanks for the update. Updating the line to fastcgi_pass unix:/run/php/php8.2-fpm.sock; did the trick. I did indeed updated php to 8.2 because passbolt v4 works only with newer php v8 as described in the update guide.

I suggest updating the documentation on this, so future updates are being done without this complication. Or even better, if it is possible to make it a part of the update, to use php v8 as dependency and change the config files of passbolt as described above.

I am sorry for the late response. I was on vacation.


Just a note for verification of php version support in case others are following, v4 Release Notes say:

Passbolt now requires a minimum of PHP 7.4 to run, but also supports PHP 8.2, which means faster performance and security. The browser extension is also getting a bit of love with some much needed maintenance to Manifest v3 and it requires at least a Passbolt API v3 to run.


I just wanted to give a feedback.
I “unhold” the package and it went through the update-process without incident.

I had no additional error.

1 Like