cd /usr/local/directadmin/custombuild
./build update
./build roundcube
/var/www/html/roundcubemail-1.5.1/config/config.inc.php
<?php
/*
+-----------------------------------------------------------------------+
| Local configuration for the Roundcube Webmail installation. |
| |
| This is a sample configuration file only containing the minimum |
| setup required for a functional installation. Copy more options |
| from defaults.inc.php to this file to override the defaults. |
| |
| This file is part of the Roundcube Webmail client |
| Copyright (C) The Roundcube Dev Team |
| |
| Licensed under the GNU General Public License version 3 or |
| any later version with exceptions for skins & plugins. |
| See the README file for a full license statement. |
+-----------------------------------------------------------------------+
*/
$config = [];
// Database connection string (DSN) for read+write operations
// Format (compatible with PEAR MDB2): db_provider://user:password@host/database
// Currently supported db_providers: mysql, pgsql, sqlite, mssql, sqlsrv, oracle
// For examples see http://pear.php.net/manual/en/package.database.mdb2.intro-dsn.php
// NOTE: for SQLite use absolute path (Linux): 'sqlite:////full/path/to/sqlite.db?mode=0646'
// or (Windows): 'sqlite:///C:/full/path/to/sqlite.db'
$config['db_dsnw'] = 'mysql://da_roundcube:password@localhost/da_roundcube';
chown webapps:webapps /var/www/html/roundcube -R
# deny webserver access to this directory
<ifModule mod_authz_core.c>
Require all denied
</ifModule>
<ifModule !mod_authz_core.c>
Deny from all
</ifModule>
find /etc -name "*roundcube*"
I fixed it! After building again, I opened /var/www/html/roundcube/config/config.inc.php, used the content from config.inc.php.sample and pasted the code generated in the building log to replace the dummy text with this part;
$config['db_dsnw'] = 'mysql://da_roundcube:XXXXX@localhost/da_roundcube';
I totally don't understand was going wrong, but it did the trick. Roundcube is loading again.
Yes because in post #5 it was confirmed that the file had this information. So I presumed the correct password was present.If I run into it similarly I'll make sure to open a ticket with them.