Checklist
[YES ] I have read intro post: https://community.passbolt.com/t/about-the-installation-issues-category/12
[ YES] I have read the tutorials, help and searched for similar issues
[ YES] I provide relevant information about my server (component names and versions, etc.)
[ YES] I provide a copy of my logs and healthcheck
[ YES] I describe the steps I have taken to trouble shoot the problem
[ YES] I describe the steps on how to reproduce the issue
Hello Community,
I have a strange issue. I installed Passbolt on Ubuntu 24.04.02 LTS. After eleminating all Healthcheck errors on bash, I ran into the Problem that the Administration Site ends up in a blank site. Everything is working properly except this issue. We had in our company passbolt already working but with an to old ubuntu and passbolt version. So I decided to set everything on a new vm with a fresh up-to-date install. I could migrate the database. I could use the SSL Certificate and all user could access the site without any problems. I think I configured the conf files as good as I can. The site
Just for a bit of context: usually the browser extension is the one that displays the pages we can see when we browse Passbolt (like the resource workspace, the user workspace etc). There is an exception though for a few pages where this is the API that serves the pages (like the MFA page which is the default page displayed with this version when reaching the admin workspace).
Now, what I see is that the server responds with 404 showing that the files are not existing. If you install the API with the package manager and all it should be fine, the files should be there. I wonder however if the nginx configuration is pointing at the right folder.
Did you changed anything regarding the configuration, like the subfolder where the instance should be served (for passbolt.php config file or the nginx config file)?
Also, I see in your pictures that a mfa page is served with a 200. Can you click on this element in the list and share with us the content of the tab response and headers please?
Hi Guys,
thank you very much for your diagnosis. You are absolutely right. Yes, I changed something in the configuration of nginx. I am such a fool.
I changed in the folder sites-enabled the config nginx-passbolt.conf. The line where you define the root website folder, I changed it from /usr/share/php/passbolt/webroot to /usr/share/php/passbolt and that was causing the fault. I changed it because I couldn’t at first open the initial passbolt website. I tried lots of things. After I read your post it was clear to me that I was the issue.
I changed it back to webroot and now it’s working as it should.
Thank you again so much.
