We will secure MySQL installation by running mysql_secure_installation.
Enter root password that we set on installation:
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
In order to log into MySQL to secure it, we'll need the current
password for the root user. If you've just installed MySQL, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.
Enter current password for root (enter for none):
OK, successfully used password, moving on...
Since we already have a root password set, answer this part with n:
Setting the root password ensures that nobody can log into the MySQL
root user without the proper authorisation.
You already have a root password set, so you can safely answer 'n'.
Change the root password? [Y/n] n
Remove the anonymous user to improve security. This will make sure people or application have correct username and password to login to MySQL. Answer with Y.
By default, a MySQL installation has an anonymous user, allowing anyone
to log into MySQL without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
Remove anonymous users? [Y/n] Y
We also want remove the root login from remote machine. Answer with Y:
Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n] Y
Previously the test database was created automatically by the MySQL installation, but MySQL 5.6 does not create test database. We can still choose Y, it will throw error but that's fine.
By default, MySQL comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.
Remove test database and access to it? [Y/n] Y
- Dropping test database...
ERROR 1008 (HY000) at line 1: Can't drop database 'test'; database doesn't exist
... Failed! Not critical, keep moving...
- Removing privileges on test database...
The last step is to reload MySQL privilege table:
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
Reload privilege tables now? [Y/n] Y
All done! If you've completed all of the above steps, your MySQL
installation should now be secure.
Thanks for using MySQL!
Create a Database for Doorgets
Now we have a secure MySQL installation, time to create database and user for doorgets itself.
Login to MySQL using root credential.
$ mysql -u root -p
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 58
Server version: 5.6.30-0ubuntu0.14.04.1 (Ubuntu)
Copyright (c) 2000, 2016, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
Create new database named doorgets using command below
mysql> CREATE DATABASE doorgets DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;
Query OK, 1 row affected (0.00 sec)
Create a user for Doorgets
The database for doorgets is ready, let's create a username and password and grant privileges to doorgets database.
Don't forget to change the password doorgets123secret below with better password.
mysql> GRANT ALL PRIVILEGES ON `doorgets`.* TO 'doorgets'@'localhost' IDENTIFIED BY 'doorgets123secret';
Query OK, 0 rows affected (0.00 sec)
We need to run FLUSH PRIVILEGES command so that the privileges table will be reloaded by MySQL and we can use new credential.
A secure connection is now a requirement for web application. The last step that we will do in this tutorial is changing the connection to only use https. We assume that you already have SSL certificate and private key.
Let's create new apache virtual host configuration on /etc/apache2/sites-available/doorgets-ssl.conf with contents below. Don't forget to change:
# Uncomment the following directive when using client certificate authentication
# HSTS (mod_headers is required) (15768000 seconds = 6 months)
Header always set Strict-Transport-Security "max-age=15768000"
# intermediate configuration, tweak to your needs
SSLProtocol all -SSLv2 -SSLv3
We will also disable doorgets http only virtual host and enable the new virtual host config.
The new virtual host configuration need Apache mod_ssl and mod_headers modules. We need to enable those modules.
$ sudo a2enmod ssl
$ sudo a2enmod headers
Now, restart Apache 2 service so it will reload its configuration. We need to restart instead of reload since we enable new module.
$ sudo service apache2 restart
We need to change the config file. Open config/config.php.
Find the line:
Now when we access our doorGets site we will always use the https connection.
In this tutorial we learned how to install doorgets on Ubuntu 14.04.
We installed all the prerequisites, created a user and database on MySQL for doorGets and also configured Apache 2 virtual hosts to be able to serve doorgets. We also configured https settings for doorgets so we run doorGets securely, this increases people''s confidence in performing a transaction on our e-store.
If you find your cPanel disk space filling up, or an email address has hit its disk space quota, cPanel has a helpful built in Email Disk Usage tool. This will provide you with a simple to understand breakdown of how much disk space each folder for a particular email...
Although WHM will normally automatically keep itself up to date, you may want to manually check for server updates / push through an update that is pending, or it may be that you have automatic updates switched off on your cPanel server. In this guide we will show you how...
You may sometimes need to manually adjust the PHP settings on your cPanel server – for example if a site is hitting the PHP memory, or file size upload limit. WHM allows you to quickly change the settings of any PHP version installed on the server when needed, using the...