This guide will give you an overview for the most common server options in existence and will outline some administration and security guidelines.



What is a server?

In essence, a server is a computer that runs services that involve clients working on remote locations. All computers run services of some kind, for example: when using Arch as a desktop you will have a network service running to connect to a network. A server will, however, run services that involve external clients, for example: a web server will run a web site to be viewed via the Internet or elsewhere on a local network.

Arch Linux as a server OS

You may have seen the comments or claims: Arch Linux was never intended as a server operating system! This is correct: there is no server installation disc available, per se, such as those you may find for other distributions. This is because Arch Linux comes as a minimal (but solid) base system, with very few desktop or server features pre-installed. This does not mean Arch Linux is a bad server system; quite the contrary. Arch's core installation is a secure and capable foundation. Since only a small number of features come pre-installed, this core installation can easily be used as a basis for a Linux server. All the popular server software (Apache, MySQL/MariaDB, PHP, Samba, and plenty more) are available in the official repository, and even more are available on the AUR. The wiki also contains much detailed documentation regarding how to get set up with this software.


For using Arch Linux on a server, you will need to have an Arch Linux installation ready.

In most GNU/Linux server operating systems, you have two options:

  • A 'text' version of the OS (where everything is done from the command line)
  • A GUI version of the OS (where you get a desktop interface, such as GNOME/KDE, etc).
Note: If you have services on your server that need to be administered using a GUI and cannot be done remotely, you must choose the second option.

For the installation of Arch Linux, please refer to the Installation guide and General recommendations articles, but do not go any further than this section unless you require a GUI.

For remote access to this server, you need a static IP address/ domain name, or something like No-Ip or FreeDNS.

Basic set-up

So what is a "basic" set-up:

  • Remote access to the server.

We want to be able to remotely log-on to our server to perform several administrative tasks. When your server is located elsewhere or does not have a monitor attached: removing or adding files, changing configuration options and server rebooting are all tasks which are impossible to do without a way to log on to your server remotely. SSH nicely provides this functionality.

  • Your Arch Linux server.
  • A http server (Apache), required for serving web pages.
  • A database server (MySql/MariaDB), often required for storing data of address book-, forum- or blog scripts.
  • The PHP scripting language, a highly popular internet scripting language used in blogs, forums, content management systems and many other web-scripts.

As the bold letters suggest, there is a name for this combination of applications: LAMP.

The following sections will guide you through the installation and configuration of the above mentioned basic set-up features.


You may choose from several HTTP servers, for example:

  • Apache — A high performance Unix-based HTTP server. || apache
  • Hiawatha — Secure and advanced webserver. || hiawatha
  • Lighttpd — A secure, fast, compliant and very flexible web-server. || lighttpd
  • nginx — Lightweight HTTP server and IMAP/POP3 proxy server. || nginx
  • Webfs — Simple and instant http server for mostly static content. || webfs

See also w:Comparison of web server software.


SSH stands for Secure Shell. SSH enables you to log on to your server through an SSH client, presenting you with a recognizable terminal-like interface. Users available on the system can be given access to log on remotely though SSH, thereby enabling remote administration of your server.

The Arch wiki SSH page covers Installation and Configuration nicely.


A LAMP server is a reasonably standard web server.

There are often disputes as to what the 'P' stands for, some people say it is PHP some people say it is Perl while others say it is Python. For the purposes of this guide I am going to make it PHP, although there are some nice Perl and Python modules for Linux so you may wish to install Perl or Python as well.

Having said that, it is by no means simple so there may be a lot to take in here.

Please refer to the LAMP wiki page for instructions on installation and configuration.

Additional web-services


Please refer to pages in Category:Mail server for instructions on mail server installation and configuration.


FTP stands for File Transfer Protocol. FTP is a service that can provide access to the file system from a remote location through an FTP client (FileZilla, gftp, etc.) or FTP-capable browser. Through FTP, you are able to add or remove files from a remote location, as well as apply some chmod commands to these files to set certain permissions.

FTP access will be related to user accounts available on the system, allowing simple rights management. FTP is a much used tool for adding files to a web server from a remote locations.

There are several FTP daemons available. See List of applications#FTP servers for a list of them.

There is also the option of FTP over SSH, or SFTP.


DAViCal is a server implementing the CalDAV and CardDAV protocol for calendar, reminder, and contact sharing.


WebDAV(Web Distributed Authoring and Versioning) is an extension of HTTP 1.1. It contains a set of concepts and accompanying extension methods to allow read and write across the HTTP 1.1 protocol. Instead of using NFS or SMB, WebDAV offers file transfers via HTTP.


ReadyMedia (previously MiniDLNA) is server software with the aim of being fully compliant with DLNA/UPnP clients to serves media files (music, pictures, and video) to clients on a network.

Web cache

Squid is a caching proxy for the Web supporting HTTP, HTTPS, FTP, and more. It reduces bandwidth and improves response times by caching and reusing frequently-requested web pages. Squid has extensive access controls and makes a great server accelerator.

Local Network Services


Avahi is a free Zero-configuration networking (zeroconf) implementation, including a system for multicast DNS/DNS-SD service discovery. It allows programs to publish and discover services and hosts running on a local network with no specific configuration. For example you can plug into a network and instantly find printers to print to, files to look at and people to talk to.

CUPS (printing)

CUPS, or Common UNIX Printing System, can provide a central point via which a number of users can print. For instance, you have several (say 3) printers and several people on a local network that wish to print. You can either add all these printers to every user's computer, or add all printers to a server running CUPS, and then simply adding the server to all clients. This allows for a central printing system that can be online 24/7, which is especially nice for printers that do not have networking capabilities.

Please refer to the CUPS wiki page for instructions on installation and configuration.


Note: dhcp v4 does not currently work due to IPv6 issues, this part of the guide will be written when that issue is resolved.

Samba (Windows-compatible file and printer sharing)

Samba is an open-source implementation of the SMB/CIFS networking protocols, effectively allowing you to share files and printers between Linux and Windows systems. Samba can provide public shares or require several forms of authentication.

Please refer to the Samba wiki page for instructions on installation and configuration.


Category:Domain Name System contains many implementations of the Domain Name System (DNS) protocols.



Refer to Firewalls for details regarding available firewall software.

Protecting SSH

Allowing remote log-on through SSH is good for administrative purposes, but can pose a threat to your server's security. Often the target of brute force attacks, SSH access needs to be limited properly to prevent third parties gaining access to your server. See Secure Shell#Protection for how to configure it.


Please refer to the SELinux wiki page for instructions on installation and configuration.

Administration and maintenance


SSH is the Secure SHell, it allows you to remotely connect to your server and administer commands as if you were physically at the computer. Combined with Screen, SSH can become an invaluable tool for remote maintenance and administration while on-the-move. Please note that a standard SSH install is not very secure and some configuration is needed before the server can be considered locked-down. This configuration includes disabling root log-in, disabling password-based log-in and setting up firewall rules. In addition, you may supplement the security of your SSH daemon by utilizing daemons, such as sshguard or fail2ban, which constantly monitor the log files for any suspicious activity and ban IP addresses with too many failed log-in attempts.

X Forwarding is forwarding your X session via SSH so you can log in to the desktop GUI remotely. Use of this feature will require SSH and an X server to be installed on the server. You will also need to have a working X server installed on the client system you will be using to connect to the server with. More information can be found in the X Forwarding section of the SSH guide.

Local Package Repositories

Repose can be used to create a package repository for a local server cluster where packages must be tested for quality and reliability before undergoing deployment into a production environment.

See also