Apache HTTP Server

From ArchWiki
Revision as of 11:21, 18 March 2010 by Dibblethewrecker (Talk | contribs) (PHP)

Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

This article describes how to set up the Apache web server on an Arch Linux system. It also tells how to optionally install PHP and MySQL and integrate these in the Apache server. This combination is commonly referred to as LAMP (Linux Apache MySQL PHP).

If you only need a web server for development and testing, Xampp might be a better and easier option.


# pacman -S apache php php-apache mysql

This document assumes you will install Apache, PHP and MySQL together. If desired however, you may install Apache, PHP, and MySQL separately and simply refer to the relevant sections below.

Note: New default user and group: Instead of group "nobody", apache now runs as user/group "http" by default. You might want to adjust your httpd.conf according to this change, though you may still run httpd as nobody.



For security reasons, as soon as Apache is started by the root user (directly or via startup scripts) it switches to the UID/GID specified in Template:Filename

  • Check for the existence of the http user by looking for http in the output of the following command:
 # cat /etc/shadow
  • Create the system user http if it does not exist already:
 # useradd -d /srv/http -r -s /bin/false -U http
This creates the http user with home directory Template:Filename, as a system account (-r), with a bogus shell (-s Template:Filename) and creates a group with the same name (-U). localhost.localdomain localhost
If you want a different hostname, append it to the end: localhost.localdomain localhost myhostname
 # Networking
  • Make sure the hostname appears in /etc/hosts or apache will fail to start. Alternatively, you can

edit Template:Filename and comment the following module:

 LoadModule unique_id_module        modules/mod_unique_id.so
  • Run the following in a terminal to start the HTTP server:
 # /etc/rc.d/httpd start
Apache should now be running. Test by visiting http://localhost/ in a web browser. It should display a simple Apache test page. If you receive a 403 Error, comment out the following line in Template:Filename:
Include conf/extra/httpd-userdir.conf
  • To start Apache automatically at boot, edit Template:Filename and add the httpd daemon:
 DAEMONS=(... httpd ...)
Or add this line to Template:Filename:
 /etc/rc.d/httpd start
 UserDir public_html
 <Directory /home/*/public_html>
   AllowOverride FileInfo AuthConfig Limit Indexes
   Options MultiViews Indexes SymLinksIfOwnerMatch ExecCGI
     Order allow,deny
     Allow from all
     Order deny,allow
     Deny from all
  • You must make sure that your home directory permissions are set properly so that Apache can get there. Your home directory and Template:Filename must be executable for others ("rest of the world"). This seems to be enough:
 $ chmod o+x ~
 $ chmod o+x ~/public_html

There may be some other, more-secure ways of setting the permissions by creating a special group and allowing only Apache and you to enter there.

Advanced Options

These options in Template:Filename might be interesting for you:

# Listen 80

This is the port Apache will listen to. For Internet-access with router, you have to forward the port.

# ServerAdmin sample@sample.com

This is the admin's email-address which can be found on error-pages e.g.

# DocumentRoot "/srv/http"

This is the directory where you should put your web pages. Change it, if you want to, but do not forget to change the

<Directory "/srv/http">

to whatever you changed your DocumentRoot to, or you will likely get a 403 error (lack of privileges) when you try to access the new document root. Do not forget to change the Deny from all line, otherwise you will get 403 error too.


PHP is practically available out of the box now.

Place this in the "LoadModule" list anywhere after Template:Codeline:
 LoadModule php5_module modules/libphp5.so
Place this at the end of the "Include" list:
 Include conf/extra/php5_module.conf
In order to load this file you need to enable Template:Codeline for your Template:Codeline. In the Template:Codeline section (or Template:Codeline) find the "Options" line and append "Includes" e.g.:
 Options Indexes FollowSymLinks Includes
Note: This will enable all Includes listed in Template:Filename. You may wish to check for unwanted Includes and comment them out.
Note: If you do not see Template:Filename in the Apache modules directory, you may have forgotten to install the php-apache package.
  • Restart the Apache service to make changes take effect:
 # /etc/rc.d/httpd restart
  • Remember to copy this file to ~/public_html if you permitted such a configuration.
If the PHP instruction is not executed (you see : <html>...</html>), check that you have added "Includes" to the "Options" line for your root directory.

Advanced options

 AddType application/x-httpd-php .php
 AddType application/x-httpd-php-source .phps
 DirectoryIndex index.php index.phtml index.html
  • If you want the libGD module, install php-gd package and uncomment in Template:Filename:
Note: php-gd requires libpng, libjpeg, and freetype2


Pay attention to which extension you uncomment, as this extension is sometimes mentioned in an explanatory comment before the actual line you want to uncomment.

  • If you want to display errors to debug your php code, change this line of Template:Filename:


  • If you want the mcrypt module, install php-mcrypt package and uncomment in Template:Filename:


  • Configure MySQL as described in MySQL.
Caution:Some users have reported typos on this line. Please make sure that it reads Template:Codeline and not Template:Codeline.
  • You can add minor privileged users for your web scripts by editing the tables found in the mysql database. You have to restart MySQL for changes to take effect. Do not forget to check the Template:Codeline table. If there is a second entry for root and your hostname is left with no password set, everybody from your host probably could gain full access. Perhaps see next section for these jobs.
  • Run in terminal:
 # /etc/rc.d/mysqld start
  • You may also need to restart Apache. Run in terminal:
 # /etc/rc.d/httpd restart
  • MySQL should now be running. Set the root password and test it by running:
 # mysqladmin -u root password password
 # mysql -u root -p
Type exit to exit from the CLI MySQL client
 DAEMONS=(... mysqld ...)

Or add this line to Template:Filename:

 /etc/rc.d/mysqld start
  • You can get the Template:Codeline message instantly whenever you try to connect to the MySQL daemon by TCP/IP. This is the TCP wrappers system (tcpd), which uses the hosts_access(5) system to allow or disallow connections.
  • If you are running into this problem, be sure to add this to your Template:Filename file:
 # mysqld : ALL : ALLOW
 # mysqld-max : ALL : ALLOW
 # and similar for the other MySQL daemons.
Note: The examples above are the simplest case, telling tcpd to allow connections from anywhere. You may wish to use a more-appropriate choice of permissible sources instead of 'ALL'. Just make sure that localhost and the IP address (numeric or DNS) of the interface by which you connect are specified.


Tip: You may want to install phpmyadmin to work with your databases.

See also

  • MySQL - Article for MySQL
  • Xampp - Self contained web-server that supports PHP, Perl, and MySQL

External links