The Perfect Server - OpenSUSE 13.1 x86_64 (Apache2, Dovecot, ISPConfig 3)

Version 1.0
Author: Falko Timme, updated by Srijan Kishore
Last edited 18/Mar/2014

This is a detailed description about how to set up an OpenSUSE 13.1 64bit (x86_64) server that offers all services needed by ISPs and hosters: Apache web server (SSL-capable) with PHP, CGI and SSI support, Postfix mail server with SMTP-AUTH, TLS and virtual mail users, BIND DNS server, Pureftpd FTP server, MySQL server, Dovecot POP3/IMAP, Quota, Firewall, Mailman, etc. Since version 3.0.4, ISPConfig comes with full support for the nginx web server in addition to Apache; this tutorial covers the setup of a server that uses Apache, not nginx.

I will use the following software:

  • Web Server: Apache 2.4 with PHP 5
  • Database Server: MySQL
  • Mail Server: Postfix with virtual users
  • DNS Server: BIND
  • FTP Server: pureftpd
  • POP3/IMAP: Dovecot
  • Webalizer and AWStats for web site statistics

In the end you should have a system that works reliably and is easily manageable with the ISPConfig 3 control panel. The following guide is for the 64bit version of OpenSUSE.

I want to say first that this is not the only way of setting up such a system. There are many ways of achieving this goal but this is the way I take. I do not issue any guarantee that this will work for you!

Notice: This guide is for ISPConfig 3.0.1 or newer. It is not suitable for ISPConfig 2.x!

 

1 Requirements

To install such a system you will need the following:

 

2 Preliminary Note

In this tutorial I use the hostname server1.example.com with the IP address 192.168.2.249 and the gateway 192.168.2.254. These settings might differ for you, so you have to replace them where appropriate.

 

3 The Base System

Boot from your OpenSUSE 13.1 DVD and select Installation:

Select your language, keyboard layout and accept the licence terms:

The installer analyzes your hardware and builds the software repository cache:

Select New Installation:

Select the region and timezone:

We select Other > Minimal Server Selection (Text Mode) here as we want to install a server without X-Window desktop. The X-Window system is not necessary to run the server and would slow down the system. We will do all administration tasks on the shell or through an SSH connection, e.g. via PuTTY from a remote desktop.

Click on Edit Partition Setup... to change the proposed partitions. As this is a server setup, we need a large /srv partition instead of the /home partition:

Share this page:

5 Comment(s)

Add comment

Comments

From: at: 2014-06-20 09:57:37

You might want to check your ISO link its pointing to 12.2

From: Md. Mohib Billah at: 2015-01-20 11:25:31

Change:

 

 zypper install http://download.opensuse.org/repositories/server:/php/openSUSE_13.1/x86_64/suphp-0.7.1-5.3.x86_64.rpm

to

zypper install http://download.opensuse.org/repositories/server:/php/openSUSE_13.1/x86_64/suphp-0.7.1-5.9.x86_64.rpm

From: Keith Ostertag at: 2015-01-21 23:11:27

Thank you so much for taking the time to create this tutorial! I am a beginner, and there is much here for me to explore and learn.

I used these instructions with OpenSUSE 13.2 with only minor and easy to determine changes (at least during the install I had no obvious errors).

From: Rex at: 2015-03-09 21:33:59

I have problems with amavis, exact install procedure listed here, when i start amavis:

Mar 09 23:33:09 s1 systemd[1]: Starting Amavisd-new Virus Scanner interface...Mar 09 23:33:09 s1 echo[2144]: Starting virus-scanner (amavisd-new):Mar 09 23:33:10 s1 amavis[2148]: starting. /usr/sbin/amavisd at linux-jfp8.site amavisd-new-2.8.1 (20130628), Unicode aware, LC_CTYPE="en_US.UTF-8", LANG="POSIX"Mar 09 23:33:11 s1 amavis[2149]: (!)Net::Server: 2015/03/09-23:33:11 Can't connect to TCP port 10024 on ::1 [Cannot assign requested address]\n  at line 68 in file /usr/lib/perl5/vendor_perl/5.18.1/Net/Server/Proto/TCP.pmMar 09 23:33:11 s1 systemd[1]: PID file /var/spool/amavis/amavisd.pid not readable (yet?) after start.Mar 09 23:33:11 s1 systemd[1]: amavis.service never wrote its PID file. Failing.Mar 09 23:33:11 s1 systemd[1]: Failed to start Amavisd-new Virus Scanner interface.Mar 09 23:33:11 s1 systemd[1]: Unit amavis.service entered failed state.

any ideeas? 

From: CBHedricks at: 2015-03-15 22:32:10

ClamAV may not work properly unless /var/run/clamav/ has the same group / user assigned as the user listed for ClamAV.  On my installation the user and group is listed as vscan.  Chown the location to the right group and user it works correctly.