I downloaded and installed the Openproject 8.3.2.-0 bitnami stack on a virtual Ubuntu 16.04.6 LTS machine. So far everything seemed fine, installation was running smooth. So did the application that started automatically after the installation.
But when I tried to access Openproject through the browser afterwards I only get an error about the Phusion Passenger application server. It takes it quite a while so I guess this is timeout related.
It also tells me that something has been logged and an id which is created anew each time. I found something in the apache error_log:
Cannot checkout session because a spawning error occurred. The identifier of the error is c7eb3c88. Please see earlier logs for details about the error.
So I did go back a little and found this:
core online, PID 7261
[Fri May 10 16:08:18.703524 2019] [mpm_prefork:notice] [pid 7239] AH00163: Apache/2.4.39 (Unix) OpenSSL/1.0.2r SVN/1.11.1 PHP/7.2.17 Phusion_Passenger/6.0.1 configured -- resuming normal operations
[Fri May 10 16:08:18.703671 2019] [core:notice] [pid 7239] AH00094: Command line: '/opt/openproject-8.3.2-0/apache2/bin/httpd.bin -f /opt/openproject-8.3.2-0/apache2/conf/httpd.conf'
[ E 2019-05-10 16:08:20.7629 7261/T5 age/Cor/SecurityUpdateChecker.h:507 ]: Security update check failed: Problem with the SSL CA cert (path? access rights?) while connecting to https://securitycheck.phusionp assenger.com/v1/check.json ; this might happen if the nss backend is installed for libcurl instead of GnuTLS or OpenSSL. If the problem persists, you can also try upgrading or reinstalling Phusion Passenger ( next check in 24 hours)
[ E 2019-05-10 16:09:51.5476 7261/Tf age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /opt/openproject-8.3.2-0/apps/openproject/htdocs/: A timeout occurred while starting a preloa der process.
Error ID: c7eb3c88
Error details saved to: /tmp/passenger-error-xA31ZJ.html
This seems to be the root of the problem because all futuere errors look just the same as you can read in teh first quote. Thing is I never had this error with earlier versions of the bitnami stack. All worked fine. I also thought that the stack uses it's own enviroment so I can't figure out where this went wrong. It looks to me tha it has huge problems with the SSLcerts, yes? But how can that be after a fresh installation that completed without errors?