Database setup

Akeeba Solo needs a database to store its configuration settings and a log of all backup attempts. Please provide the connection parameters to the database below. You may either use the same database as the site you want to back up, or a dedicated database just for Akeeba Solo (recommended).

This is usually MySQLi (with the trailing "i")

The host name or IP address of the database server (usually: localhost). Please note that localhost and 127.0.0.1 are very different as far as MySQL is concerned; you may have to try both to see which works with your database server. If your server is using a non-standard port, append it after the hostname prefixed with a colon, e.g. 127.0.0.1:1234 to use a database server on 127.0.0.1 listening to port 1234.

The username you use to connect to your database. Most hosts using cPanel, Plesk and other major hosting panels will give usernames like abcdef_username, where abcdef is your hosting control panel username. If unsure, please ask your host.

The password you use to connect to your database.

The name of your database. Most hosts using cPanel, Plesk and other major hosting panels will give database names like abcdef_username, where abcdef is your hosting control panel username. If unsure, please ask your host.

The common table name prefix of all database tables belonging to this Akeeba Solo installation. You may want to change it if you have multiple Akeeba Solo installations sharing the same database.

Should we connect to the database using an SSL certificate? This can be used instead of username and password authentication (encrypted connection with certificate authentication) or on top of username and password authentication (encrypted connection with password authentication). If you don't know what this means set this option to No and ignore the next few options as well.

Enter a list of encryption methods for connecting with SSL certificates, separated by colons. If left empty the default list (AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-CBC-SHA256:AES256-CBC-SHA384:DES-CBC3-SHA) will be used (recommended).

Absolute file path to the Certification Authority (CA) certificate PEM file of your database server, e.g. /home/myuser/ca.pem

Absolute file path to the private key PEM file of your database user, e.g. /home/myuser/myuser-key.pem

Absolute file path to the public key (certificate) PEM file of your database user, e.g. /home/myuser/myuser.pem

Set to Yes to verify the certificate the server sends back to us. This is verified against the Certification Authority (CA) file you specified. If you get connection errors set this to No; some setups (especially those generated by the mysql_ssl_rsa_setup) may disallow a connection if certification verification is enabled. If you enable verification and the CA file field is left blank the server's certificate will be checked against the Certification Authority files your server knows about, see the openssl.cafile and openssl.capath PHP options.