This is the second time I have tried to install Passbolt and keep getting stuck at the same issue. Everything seems to be set up properly but right now I am just getting the Apache default page. I am pretty confident it has to do with my apache setup (I am fairly new to web servers) but I do already have another website up and running on my local network so I know the web server is setup at least somewhat properly. My other site running on the server is http as well. The first time I did the installation I was able to get to the plugin page by forcing my url to /index.php but have not been able to do that with this second try which gives me a “requested url not found” error. I followed the Debian 9 install guide.
I am using an Apache web server on Ubuntu 16.04. My database is setup on a separate server than the web server. I am including my health check, site-available conf file, passbolt.php file (The relevant parts at least).
Here is my health check
www-data@localhost:~/passbolt$ ./bin/cake passbolt healthcheck
5 error(s) found. Hang in there!
‘App’ => [
// A base URL to use for absolute links.
// The url where the passbolt instance will be reachable to your end users.
// This information is need to render images in emails for example
‘fullBaseUrl’ => ‘http:// passbolt. company. com’,
// Database configuration. 'Datasources' => [ 'default' => [ 'host' => 'Host_IP', //'port' => 'non_standard_port_number', 'username' => 'passbolt', 'password' => 'Password', 'database' => 'passbolt', ], ], // Email configuration. 'EmailTransport' => [ 'default' => [ 'host' => 'localhost', 'port' => 25, 'username' => 'user', 'password' => 'secret', // Is this a secure connection? true if yes, null if no. 'tls' => null, //'timeout' => 30, //'client' => null, //'url' => null, ], ], 'Email' => [ 'default' => [ // Defines the default name and email of the sender of the emails. 'from' => ['passbolt@your_organization.com' => 'Passbolt'], //'charset' => 'utf-8', //'headerCharset' => 'utf-8', ], ], 'passbolt' => [ // GPG Configuration. // The keyring must to be owned and accessible by the webserver user. // Example: www-data user on Debian 'ssl' => [ 'force' => false, ], 'gpg' => [ // Tell GPG where to find the keyring. // If putenv is set to false, gnupg will use the default path ~/.gnupg. // For example : // - Apache on Centos it would be in '/usr/share/httpd/.gnupg' // - Apache on Debian it would be in '/var/www/.gnupg' // - Nginx on Centos it would be in '/var/lib/nginx/.gnupg' // - etc. //'keyring' => getenv("HOME") . DS . '.gnupg', // // Replace GNUPGHOME with above value even if it is set. //'putenv' => false, // Main server key. 'serverKey' => [ // Server private key fingerprint. 'fingerprint' => 'BFB16DDEBD66416F45F9BF5DBAFB708A7B77F58A', //'public' => CONFIG . 'gpg' . DS . 'serverkey.asc', //'private' => CONFIG . 'gpg' . DS . 'serverkey_private.asc', ],
ServerName http:// passbolt. company. com
<Directory /var/www/passbolt> Options FollowSymLinks AllowOverride All Require all granted </Directory> </VirtualHost>
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 1527/mysqld tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1217/sshd tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 1553/postgres tcp 0 480 10.x0.x8.x1:22 10.x0.x8.x1:60437 ESTABLISHED 2104/sshd: user1 tcp6 0 0 :::80 :::* LISTEN 1561/apache2 tcp6 0 0 :::22 :::* LISTEN 1217/sshd tcp6 0 0 ::1:5432 :::* LISTEN 1553/postgres tcp6 0 0 :::443 :::* LISTEN 1561/apache2 udp 0 0 0.0.0.0:68 0.0.0.0:* 981/dhclient udp6 0 0 ::1:41058 ::1:41058 ESTABLISHED 1553/postgres
Not sure where to turn to now. Let me know if any other files are need or any other information. Thanks in advance!
*Edit: I added the spaces in the url because I am a new user. The real files do not have the spaces.
[x] I have read intro post: About the Installation Issues category
[x] I have read the tutorials, help and searched for similar issues
[x] I provide relevant information about my server (component names and versions, etc.)
[x] I provide a copy of my logs and healthcheck
[x] I describe the steps I have taken to trouble shoot the problem
[x] I describe the steps on how to reproduce the issue