{"id":552,"date":"2020-04-04T03:18:00","date_gmt":"2020-04-03T19:18:00","guid":{"rendered":"http:\/\/www.sysadmindayph.com\/blog\/?p=552"},"modified":"2020-04-04T03:18:03","modified_gmt":"2020-04-03T19:18:03","slug":"installing-linux-apache-mysql-php-lamp-stack-on-ubuntu-18-04-on-an-aws-ec2-instance","status":"publish","type":"post","link":"https:\/\/www.sysadmindayph.com\/blog\/installing-linux-apache-mysql-php-lamp-stack-on-ubuntu-18-04-on-an-aws-ec2-instance\/","title":{"rendered":"Installing Linux, Apache, MySQL, PHP (LAMP) stack on Ubuntu 18.04 – on an AWS EC2 Instance"},"content":{"rendered":"\n

<\/p>\n\n\n\n

Step 1 \u2014 Installing Apache<\/p>\n\n\n\n

Install Apache using Ubuntu\u2019s package manager, apt<\/code>:<\/p>\n\n\n\n

sudo apt update\nsudo apt install apache2<\/code><\/pre>\n\n\n\n
Test after staring service – systemctl start apache2<\/p>\n\n\n\n
http://your_server_ip<\/code><\/pre>\n\n\n\n
How To Find your Server\u2019s Public IP Address<\/p>\n\n\n\n
ip addr show eth0 | grep inet | awk ‘{ print $2; }’ | sed ‘s\/\\\/.*$\/\/’<\/p>\n\n\n\n
<\/p>\n\n\n\n
Step 2 \u2014 Installing MySQL<\/p>\n\n\n\n
Again, use apt<\/code> to acquire and install this software:<\/p>\n\n\n\n
sudo apt install mysql-server<\/code><\/pre>\n\n\n\n
sudo mysql_secure_installation\n<\/code><\/pre>\n\n\n\n
This will ask if you want to configure the\u00a0VALIDATE PASSWORD PLUGIN<\/code>.<\/p>\n\n\n\n
If you prefer to use a password when connecting to MySQL as root<\/strong>, you will need to switch its authentication method from auth_socket<\/code> to mysql_native_password<\/code>. To do this, open up the MySQL prompt from your terminal:<\/p>\n\n\n\n
sudo mysql\n<\/code><\/pre>\n\n\n\n
Next, check which authentication method each of your MySQL user accounts use with the following command:<\/p>\n\n\n\n
SELECT user,authentication_string,plugin,host FROM mysql.user;\n<\/code><\/pre>\n\n\n\n
Output+------------------+-------------------------------------------+-----------------------+-----------+\n| user             | authentication_string                     | plugin                | host      |\n+------------------+-------------------------------------------+-----------------------+-----------+\n| root             |                                           | auth_socket           | localhost |\n| mysql.session    | *THISISNOTAVALIDPASSWORDTHATCANBEUSEDHERE | mysql_native_password | localhost |\n| mysql.sys        | *THISISNOTAVALIDPASSWORDTHATCANBEUSEDHERE | mysql_native_password | localhost |\n| debian-sys-maint | *CC744277A401A7D25BE1CA89AFF17BF607F876FF | mysql_native_password | localhost |\n+------------------+-------------------------------------------+-----------------------+-----------+\n4 rows in set (0.00 sec)\n<\/code><\/pre>\n\n\n\n
In this example, you can see that the root<\/strong> user does in fact authenticate using the auth_socket<\/code> plugin. To configure the root<\/strong> account to authenticate with a password, run the following ALTER USER<\/code> command. Be sure to change password<\/code> to a strong password of your choosing:<\/p>\n\n\n\n
ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';\n<\/code><\/pre>\n\n\n\n
Then, run FLUSH PRIVILEGES<\/code> which tells the server to reload the grant tables and put your new changes into effect:<\/p>\n\n\n\n
FLUSH PRIVILEGES;\n<\/code><\/pre>\n\n\n\n
Check the authentication methods employed by each of your users again to confirm that root<\/strong> no longer authenticates using the auth_socket<\/code> plugin:<\/p>\n\n\n\n
SELECT user,authentication_string,plugin,host FROM mysql.user;\n<\/code><\/pre>\n\n\n\n
Output+------------------+-------------------------------------------+-----------------------+-----------+\n| user             | authentication_string                     | plugin                | host      |\n+------------------+-------------------------------------------+-----------------------+-----------+\n| root             | *3636DACC8616D997782ADD0839F92C1571D6D78F | mysql_native_password | localhost |\n| mysql.session    | *THISISNOTAVALIDPASSWORDTHATCANBEUSEDHERE | mysql_native_password | localhost |\n| mysql.sys        | *THISISNOTAVALIDPASSWORDTHATCANBEUSEDHERE | mysql_native_password | localhost |\n| debian-sys-maint | *CC744277A401A7D25BE1CA89AFF17BF607F876FF | mysql_native_password | localhost |\n+------------------+-------------------------------------------+-----------------------+-----------+\n4 rows in set (0.00 sec)\n<\/code><\/pre>\n\n\n\n
You can see in this example output that the root<\/strong> MySQL user now authenticates using a password. Once you confirm this on your own server, you can exit the MySQL shell:<\/p>\n\n\n\n
exit\n<\/code><\/pre>\n\n\n\n
At this point, your database system is now set up and you can move on to installing PHP, the final component of the LAMP stack.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Step 3 \u2014 Installing PHP<\/p>\n\n\n\n
<\/p>\n\n\n\n
Once again, leverage the apt<\/code> system to install PHP. In addition, include some helper packages this time so that PHP code can run under the Apache server and talk to your MySQL database:<\/p>\n\n\n\n
sudo apt install php libapache2-mod-php php-mysql\n<\/code><\/pre>\n\n\n\n
This should install PHP without any problems. We\u2019ll test this in a moment.<\/p>\n\n\n\n
In most cases, you will want to modify the way that Apache serves files when a directory is requested. Currently, if a user requests a directory from the server, Apache will first look for a file called index.html<\/code>. We want to tell the web server to prefer PHP files over others, so make Apache look for an index.php<\/code> file first.<\/p>\n\n\n\n
To do this, type this command to open the dir.conf<\/code> file in a text editor with root privileges:<\/p>\n\n\n\n
sudo nano \/etc\/apache2\/mods-enabled\/dir.conf\n<\/code><\/pre>\n\n\n\n
It will look like this:\/etc\/apache2\/mods-enabled\/dir.conf<\/p>\n\n\n\n
<IfModule mod_dir.c>\n    DirectoryIndex index.html index.cgi index.pl index.php index.xhtml index.htm\n<\/IfModule>\n<\/code><\/pre>\n\n\n\n
Move the PHP index file (highlighted above) to the first position after the DirectoryIndex<\/code> specification, like this:\/etc\/apache2\/mods-enabled\/dir.conf<\/p>\n\n\n\n
<IfModule mod_dir.c>\n    DirectoryIndex index.php index.html index.cgi index.pl index.xhtml index.htm\n<\/IfModule>\n<\/code><\/pre>\n\n\n\n
When you are finished, save and close the file by pressing\u00a0CTRL+X<\/code>. Confirm the save by typing\u00a0Y<\/code>\u00a0and then hit\u00a0ENTER<\/code>\u00a0to verify the file save location.<\/p>\n\n\n\n
check Apache’s config file for syntax error:<\/p>\n\n\n\n
apachectl configtest<\/p>\n\n\n\n
After this, restart the Apache web server in order for your changes to be recognized. Do this by typing this:<\/p>\n\n\n\n
sudo systemctl restart apache2\n<\/code><\/pre>\n\n\n\n
You can also check on the status of the apache2<\/code> service using systemctl<\/code>:<\/p>\n\n\n\n
sudo systemctl status apache2\n<\/code><\/pre>\n\n\n\n
Sample Output\u25cf apache2.service - LSB: Apache2 web server\n   Loaded: loaded (\/etc\/init.d\/apache2; bad; vendor preset: enabled)\n  Drop-In: \/lib\/systemd\/system\/apache2.service.d\n           \u2514\u2500apache2-systemd.conf\n   Active: active (running) since Tue 2018-04-23 14:28:43 EDT; 45s ago\n     Docs: man:systemd-sysv-generator(8)\n  Process: 13581 ExecStop=\/etc\/init.d\/apache2 stop (code=exited, status=0\/SUCCESS)\n  Process: 13605 ExecStart=\/etc\/init.d\/apache2 start (code=exited, status=0\/SUCCESS)\n    Tasks: 6 (limit: 512)\n   CGroup: \/system.slice\/apache2.service\n           \u251c\u250013623 \/usr\/sbin\/apache2 -k start\n           \u251c\u250013626 \/usr\/sbin\/apache2 -k start\n           \u251c\u250013627 \/usr\/sbin\/apache2 -k start\n           \u251c\u250013628 \/usr\/sbin\/apache2 -k start\n           \u251c\u250013629 \/usr\/sbin\/apache2 -k start\n           \u2514\u250013630 \/usr\/sbin\/apache2 -k start\n<\/code><\/pre>\n\n\n\n
Press\u00a0Q<\/code>\u00a0to exit this status output.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Step 4 \u2014 Setting Up Virtual Hosts (Recommended)<\/h2>\n\n\n\n
When using the Apache web server, you can use virtual hosts<\/em> (similar to server blocks in Nginx) to encapsulate configuration details and host more than one domain from a single server. We will set up a domain called your_domain<\/strong>, but you should replace this with your own domain name<\/strong>. To learn more about setting up a domain name with DigitalOcean, see our Introduction to DigitalOcean DNS<\/a>.<\/p>\n\n\n\n
Apache on Ubuntu 18.04 has one server block enabled by default that is configured to serve documents from the \/var\/www\/html<\/code> directory. While this works well for a single site, it can become unwieldy if you are hosting multiple sites. Instead of modifying \/var\/www\/html<\/code>, let\u2019s create a directory structure within \/var\/www<\/code> for our your_domain<\/strong> site, leaving \/var\/www\/html<\/code> in place as the default directory to be served if a client request doesn\u2019t match any other sites.<\/p>\n\n\n\n
Create the directory for your_domain<\/strong> as follows:<\/p>\n\n\n\n
sudo mkdir \/var\/www\/your_domain\n<\/code><\/pre>\n\n\n\n
Next, assign ownership of the directory with the $USER<\/code> environment variable:<\/p>\n\n\n\n
sudo chown -R $USER:$USER \/var\/www\/your_domain\n<\/code><\/pre>\n\n\n\n
The permissions of your web roots should be correct if you haven\u2019t modified your unmask<\/code> value, but you can make sure by typing:<\/p>\n\n\n\n
sudo chmod -R 755 \/var\/www\/your_domain\n<\/code><\/pre>\n\n\n\n
Next, create a sample index.html<\/code> page using nano<\/code> or your favorite editor:<\/p>\n\n\n\n
nano \/var\/www\/your_domain\/index.html\n<\/code><\/pre>\n\n\n\n
Inside, add the following sample HTML:\/var\/www\/your_domain\/index.html<\/p>\n\n\n\n
<html>\n    <head>\n        <title>Welcome to Your_domain!<\/title>\n    <\/head>\n    <body>\n        <h1>Success!  The your_domain server block is working!<\/h1>\n    <\/body>\n<\/html>\n<\/code><\/pre>\n\n\n\n
Save and close the file when you are finished.<\/p>\n\n\n\n
In order for Apache to serve this content, it\u2019s necessary to create a virtual host file with the correct directives. Instead of modifying the default configuration file located at \/etc\/apache2\/sites-available\/000-default.conf<\/code> directly, let\u2019s make a new one at \/etc\/apache2\/sites-available\/your_domain.conf<\/code>:<\/p>\n\n\n\n
sudo nano \/etc\/apache2\/sites-available\/your_domain.conf\n<\/code><\/pre>\n\n\n\n
Paste in the following configuration block, which is similar to the default, but updated for our new directory and domain name:\/etc\/apache2\/sites-available\/your_domain.conf<\/p>\n\n\n\n
<VirtualHost *:80>\n    ServerAdmin webmaster@localhost\n    ServerName your_domain\n    ServerAlias www.your_domain\n    DocumentRoot \/var\/www\/your_domain\n    ErrorLog ${APACHE_LOG_DIR}\/error.log\n    CustomLog ${APACHE_LOG_DIR}\/access.log combined\n<\/VirtualHost>\n<\/code><\/pre>\n\n\n\n
Notice that we\u2019ve updated the DocumentRoot<\/code> to our new directory and ServerAdmin<\/code> to an email that the your_domain<\/strong> site administrator can access. We\u2019ve also added two directives: ServerName<\/code>, which establishes the base domain that should match for this virtual host definition, and ServerAlias<\/code>, which defines further names that should match as if they were the base name.<\/p>\n\n\n\n
Save and close the file when you are finished.<\/p>\n\n\n\n
Let\u2019s enable the file with the a2ensite<\/code> tool:<\/p>\n\n\n\n
sudo a2ensite your_domain.conf\n<\/code><\/pre>\n\n\n\n
Disable the default site defined in 000-default.conf<\/code>:<\/p>\n\n\n\n
sudo a2dissite 000-default.conf\n<\/code><\/pre>\n\n\n\n
Next, let\u2019s test for configuration errors:<\/p>\n\n\n\n
sudo apache2ctl configtest\n<\/code><\/pre>\n\n\n\n
You should see the following output:<\/p>\n\n\n\n
OutputSyntax OK\n<\/code><\/pre>\n\n\n\n
Restart Apache to implement your changes:<\/p>\n\n\n\n
sudo systemctl restart apache2\n<\/code><\/pre>\n\n\n\n
Apache should now be serving your domain name. You can test this by navigating to http:\/\/your_domain<\/code>, where you should see something like this:<\/p>\n\n\n\n
\"Apache<\/figure>\n\n\n\n
With that, you virtual host is fully set up. Before making any more changes or deploying an application, though, it would be helpful to proactively test out your PHP configuration in case there are any issues that should be addressed.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Step 5 \u2014 Testing PHP Processing on your Web Server<\/p>\n\n\n\n
Create the file at the web root you created in the previous step by running:<\/p>\n\n\n\n
sudo nano \/var\/www\/your_domain\/info.php\n<\/code><\/pre>\n\n\n\n
This will open a blank file. Add the following text, which is valid PHP code, inside the file:info.php<\/p>\n\n\n\n
<\/p>\n\n\n\n
<?php\nphpinfo();\n?><\/code><\/pre>\n\n\n\n
<\/p>\n\n\n\n
How to solve the phpmyadmin not found issue 404 <\/h3>\n\n\n\n
Create a link in \/var\/www<\/code> like this:<\/p>\n\n\n\n
sudo ln -s \/usr\/share\/phpmyadmin \/var\/www\/<\/code><\/p>\n\n\n\n
Note: since 14.04 you may want to use \/var\/www\/html\/<\/code> instead of \/var\/www\/<\/code><\/em><\/p>\n\n\n\n
If that’s not working for you, you need to include PHPMyAdmin inside apache configuration.<\/p>\n\n\n\n
Open apache.conf<\/code> using your favorite editor, mine is vim<\/code> \ud83d\ude42<\/p>\n\n\n\n
sudo vim \/etc\/apache2\/apache2.conf<\/code><\/p>\n\n\n\n
Then add the following line:<\/p>\n\n\n\n
Include \/etc\/phpmyadmin\/apache.conf<\/code><\/p>\n\n\n\n
For Ubuntu 15.04 and 16.04<\/strong><\/p>\n\n\n\n
  • sudo ln -s \/etc\/phpmyadmin\/apache.conf \/etc\/apache2\/conf-available\/phpmyadmin.conf<\/code><\/li>
  • sudo a2enconf phpmyadmin.conf<\/code><\/li>
  • sudo service apache2 reload<\/code><\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
    Step 1 \u2014 Installing Apache Install Apache using Ubuntu\u2019s package manager, apt: Test after staring service – systemctl start apache2 How To Find your Server\u2019s Public IP Address ip addr show eth0 | grep inet | …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[53],"tags":[],"class_list":["post-552","post","type-post","status-publish","format-standard","hentry","category-apache"],"_links":{"self":[{"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/posts\/552","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/comments?post=552"}],"version-history":[{"count":1,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/posts\/552\/revisions"}],"predecessor-version":[{"id":553,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/posts\/552\/revisions\/553"}],"wp:attachment":[{"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/media?parent=552"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/categories?post=552"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/tags?post=552"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}