The Perfect Server - CentOS 6.4 x86_64 (Apache2, Dovecot, ISPConfig 3) - Page 5

17 Install BIND

We can install BIND as follows:

yum install bind bind-utils

Next open /etc/sysconfig/named...

vi /etc/sysconfig/named

... and make sure that the ROOTDIR=/var/named/chroot line is comment out:

# BIND named process options
# ~~~~~~~~~~~~~~~~~~~~~~~~~~
# Currently, you can use the following options:
# ROOTDIR="/var/named/chroot"  --  will run named in a chroot environment.
#                            you must set up the chroot environment
#                            (install the bind-chroot package) before
#                            doing this.
#       NOTE:
#         Those directories are automatically mounted to chroot if they are
#         empty in the ROOTDIR directory. It will simplify maintenance of your
#         chroot environment.
#          - /var/named
#          - /etc/pki/dnssec-keys
#          - /etc/named
#          - /usr/lib64/bind or /usr/lib/bind (architecture dependent)
#         Those files are mounted as well if target file doesn't exist in
#         chroot.
#          - /etc/named.conf
#          - /etc/rndc.conf
#          - /etc/rndc.key
#          - /etc/named.rfc1912.zones
#          - /etc/named.dnssec.keys
#          - /etc/named.iscdlv.key
#       Don't forget to add "$AddUnixListenSocket /var/named/chroot/dev/log"
#       line to your /etc/rsyslog.conf file. Otherwise your logging becomes
#       broken when rsyslogd daemon is restarted (due update, for example).
# OPTIONS="whatever"     --  These additional options will be passed to named
#                            at startup. Don't add -t here, use ROOTDIR instead.
# KEYTAB_FILE="/dir/file"    --  Specify named service keytab file (for GSS-TSIG)
# DISABLE_ZONE_CHECKING  -- By default, initscript calls named-checkzone
#                           utility for every zone to ensure all zones are
#                           valid before named starts. If you set this option
#                           to 'yes' then initscript doesn't perform those
#                           checks.

Make a backup of the existing /etc/named.conf file and create a new one as follows:

cp /etc/named.conf /etc/named.conf_bak
cat /dev/null > /etc/named.conf
vi /etc/named.conf

// named.conf
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
// server as a caching only nameserver (as a localhost DNS resolver only).
// See /usr/share/doc/bind*/sample/ for example named configuration files.
options {
        listen-on port 53 { any; };
        listen-on-v6 port 53 { any; };
        directory       "/var/named";
        dump-file       "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
        memstatistics-file "/var/named/data/named_mem_stats.txt";
        allow-query     { any; };
        recursion no;
        allow-recursion { none; };
logging {
        channel default_debug {
                file "data/";
                severity dynamic;
zone "." IN {
        type hint;
        file "";
include "/etc/named.conf.local";

Create the file /etc/named.conf.local that is included at the end of /etc/named.conf (/etc/named.conf.local will later on get populated by ISPConfig if you create DNS zones in ISPConfig):

touch /etc/named.conf.local

Then we create the startup links and start BIND:

chkconfig --levels 235 named on
/etc/init.d/named start


18 Install Webalizer, And AWStats

Webalizer and AWStats can be installed as follows:

yum install webalizer awstats perl-DateTime-Format-HTTP perl-DateTime-Format-Builder


19 Install Jailkit

Jailkit is needed only if you want to chroot SSH users. It can be installed as follows (important: Jailkit must be installed before ISPConfig - it cannot be installed afterwards!):

cd /tmp
tar xvfz jailkit-2.15.tar.gz
cd jailkit-2.15
make install
cd ..
rm -rf jailkit-2.15*


20 Install fail2ban

This is optional but recommended, because the ISPConfig monitor tries to show the log:

yum install fail2ban

We must configure fail2ban to log to the log file /var/log/fail2ban.log because this is the log file that is monitored by the ISPConfig Monitor module. Open /etc/fail2ban/fail2ban.conf...

vi /etc/fail2ban/fail2ban.conf

... and comment out the logtarget = SYSLOG line and add logtarget = /var/log/fail2ban.log:

# Option:  logtarget
# Notes.:  Set the log target. This could be a file, SYSLOG, STDERR or STDOUT.
#          Only one log target can be specified.
# Values:  STDOUT STDERR SYSLOG file  Default:  /var/log/fail2ban.log
#logtarget = SYSLOG
logtarget = /var/log/fail2ban.log

Then create the system startup links for fail2ban and start it:

chkconfig --levels 235 fail2ban on
/etc/init.d/fail2ban start


21 Install rkhunter

rkhunter can be installed as follows:

yum install rkhunter


22 Install Mailman

Since version 3.0.4, ISPConfig also allows you to manage (create/modify/delete) Mailman mailing lists. If you want to make use of this feature, install Mailman as follows:

yum install mailman

Before we can start Mailman, a first mailing list called mailman must be created:

/usr/lib/mailman/bin/newlist mailman

[root@server1 tmp]# /usr/lib/mailman/bin/newlist mailman
Enter the email of the person running the list:
 <-- admin email address, e.g.
Initial mailman password: <-- admin password for the mailman list
To finish creating your mailing list, you must edit your /etc/aliases (or
equivalent) file by adding the following lines, and possibly running the
`newaliases' program:

## mailman mailing list
mailman:              "|/usr/lib/mailman/mail/mailman post mailman"
mailman-admin:        "|/usr/lib/mailman/mail/mailman admin mailman"
mailman-bounces:      "|/usr/lib/mailman/mail/mailman bounces mailman"
mailman-confirm:      "|/usr/lib/mailman/mail/mailman confirm mailman"
mailman-join:         "|/usr/lib/mailman/mail/mailman join mailman"
mailman-leave:        "|/usr/lib/mailman/mail/mailman leave mailman"
mailman-owner:        "|/usr/lib/mailman/mail/mailman owner mailman"
mailman-request:      "|/usr/lib/mailman/mail/mailman request mailman"
mailman-subscribe:    "|/usr/lib/mailman/mail/mailman subscribe mailman"
mailman-unsubscribe:  "|/usr/lib/mailman/mail/mailman unsubscribe mailman"

Hit enter to notify mailman owner...
 <-- ENTER

[root@server1 tmp]#

Open /etc/aliases afterwards...

vi /etc/aliases

... and add the following lines:

mailman:              "|/usr/lib/mailman/mail/mailman post mailman"
mailman-admin:        "|/usr/lib/mailman/mail/mailman admin mailman"
mailman-bounces:      "|/usr/lib/mailman/mail/mailman bounces mailman"
mailman-confirm:      "|/usr/lib/mailman/mail/mailman confirm mailman"
mailman-join:         "|/usr/lib/mailman/mail/mailman join mailman"
mailman-leave:        "|/usr/lib/mailman/mail/mailman leave mailman"
mailman-owner:        "|/usr/lib/mailman/mail/mailman owner mailman"
mailman-request:      "|/usr/lib/mailman/mail/mailman request mailman"
mailman-subscribe:    "|/usr/lib/mailman/mail/mailman subscribe mailman"
mailman-unsubscribe:  "|/usr/lib/mailman/mail/mailman unsubscribe mailman"



afterwards and restart Postfix:

/etc/init.d/postfix restart

Now open the Mailman Apache configuration file /etc/httpd/conf.d/mailman.conf...

vi /etc/httpd/conf.d/mailman.conf

... and add the line ScriptAlias /cgi-bin/mailman/ /usr/lib/mailman/cgi-bin/. Comment out Alias /pipermail/ /var/lib/mailman/archives/public/ and add the line Alias /pipermail /var/lib/mailman/archives/public/:

#  httpd configuration settings for use with mailman.
ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/
ScriptAlias /cgi-bin/mailman/ /usr/lib/mailman/cgi-bin/
<Directory /usr/lib/mailman/cgi-bin/>
    AllowOverride None
    Options ExecCGI
    Order allow,deny
    Allow from all

#Alias /pipermail/ /var/lib/mailman/archives/public/
Alias /pipermail /var/lib/mailman/archives/public/
<Directory /var/lib/mailman/archives/public>
    Options Indexes MultiViews FollowSymLinks
    AllowOverride None
    Order allow,deny
    Allow from all
    AddDefaultCharset Off
# Uncomment the following line, to redirect queries to /mailman to the
# listinfo page (recommended).
# RedirectMatch ^/mailman[/]*$ /mailman/listinfo

Restart Apache:

/etc/init.d/httpd restart

Create the system startup links for Mailman and start it:

chkconfig --levels 235 mailman on
/etc/init.d/mailman start

After you have installed ISPConfig 3, you can access Mailman as follows:

You can use the alias /cgi-bin/mailman for all Apache vhosts (please note that suExec and CGI must be disabled for all vhosts from which you want to access Mailman!), which means you can access the Mailman admin interface for a list at http://<vhost>/cgi-bin/mailman/admin/<listname>, and the web page for users of a mailing list can be found at http://<vhost>/cgi-bin/mailman/listinfo/<listname>.

Under http://<vhost>/pipermail/<listname> you can find the mailing list archives.

Share this page:

50 Comment(s)

Add comment


From: Brett at: 2013-07-08 09:23:26

I spent an afternoon following the guide to the letter, after trying previously, and ended up with a partially working server. Second time round, I realised the problem wasn't me.

Once you get to the end, exhausted and excited... go back and read the comments to figure out issues with Dovecot setup, Postfix setup, Pro-FTP, SSL certificates to name a few. If you're here like I was (because you NEED a guide for this stuff) consider yourself warned.

A sincere thanks to the Falko who put this guide together. Please work out the niggling bugs and it'll be worthy of the title 'Perfect Server'. Some of them are just a copy and paste from the comments into the guide so that they're not missed.

From: at: 2013-11-22 02:08:53


Here is the guide on how to make this setup to serve ASP.NET pages.

Kind regards,

From: at: 2014-03-06 19:40:22

I have installed this tutorial with Centos 6.5!

 One problem: You must uninstall eaccelerator... or delete file eaccelerator.ini from /etc/php.d becaouse it will not work with fasctgi (for Ispconfig)

few hours to discover the problem....




From: Anonymous at: 2013-10-09 11:09:26

A minimal install of CentOS does not include system-config-network. If network settings were not specified during the installer config, the network will need to be brought up with ip addr and ip route commands or by editing config files.

From: at: 2014-06-05 09:53:51

You can always install them using the following command.

yum install -y  system-config-firewall-tui system-config-network-tui

From: Anonymous at: 2013-03-15 19:22:23

rpm --import ??


From: Paolo at: 2013-03-15 20:16:03

Pay attention: to have a correct SASL authentication, add the following to the service auth section of /etc/dovecot/conf.d/10-master.conf

  unix_listener auth-master {

    mode = 0660
    user = vmail
    group = vmail

 ans check in every file in the /etc/dovecot/conf.d/ directory for the new correct path of dovecot.conf and dovecot-sql.conf

From: bkraul at: 2013-06-10 16:52:47

Paolo, could you please explain what you mean in your last statement,

check in every file in the /etc/dovecot/conf.d/ directory for the new correct path of dovecot.conf and dovecot-sql.conf?

What is the path changed from and to? I can't find any reference on this page pointing to a path change for the conf files. Thanks!

From: rod at: 2013-11-03 14:24:21

SquirrelMail will not login, found on web need the two following lines added to your instructions

ln -s /etc/dovecot/dovecot-sql.conf /etc/dovecot-sql.conf
ln -s /etc/dovecot/dovecot.conf /etc/dovecot.conf


And nice instructions!

From: at: 2014-02-04 21:12:36

Such a wonderful & complete tutorial.

I followed every step of it. Now my VPS is up and running perfectly. During the installation I got only 2 errors. I have posted it at expecting a fix.

 Thank you Falco Timme.


From: Anonymous at: 2013-05-10 21:14:14

That's it. You can now try to connect using your FTP client; however, you should configure your FTP client to use TLS. Followed STEP by STEP and can't FTP

connects ok takes root & password and shows the certificate (by not showing the details I added)

then keep gettingwhen waiting for folders to show

Critical Error

Cannot connect to server

From: at: 2013-05-29 18:54:20

the Link for wget

is broken but I was able to use this zip file:


The folder /linux changed for /unix and it looks like they didn't update the path


From: LinuxMan at: 2013-07-20 00:34:46

You can actually use the following link to get mod_ruby..



From: Diego at: 2013-09-23 14:04:25

Then we create the system startup links for Apache and start it:

chkconfig --levels 235 httpd on
/etc/init.d/httpd start

Now you can direct your browser to or and log in with the user name root and your new root MySQL password.

I did all the same with this guide, but i got error: 



You don't have permission to access /phpmyadmin on this server.

How could i fix it, please?

It only works at local remote with

From: Sofd at: 2014-03-19 10:23:31

Edit your httpd.conf file as follows:

# nano /etc/httpd/conf/httpd.conf

Add the following lines here:

<Directory "/usr/share/phpmyadmin">
    Order allow,deny
    Allow from all

Issue the following command:

# service httpd restart

If your problem is not solved then disable your SELinux.

From: Anonymous at: 2014-06-06 01:01:49


 I found that I had several NameVirtualHost for the same ports (*80 and *443). I removed NameVirtualHost from /etc/httpd/conf/sites-available/ispconfig.conf and restarted apache with no error.

From: Anonymous at: 2013-10-06 11:25:33

hello, i've following all of thats tutorial. at the beginning there is no problem with my SFTP, when i finished install my Centos, i can use SSH and SFTP. but after i install the other software like this tutorial said, and i finished following this tutorial, why my root and other user cannot connect via SFTP and FTP?

my root still can access ssh.

any solution?

From: pd at: 2013-10-23 15:24:50

Can you tell my, why the version of su_php is not compatilbe with ispconfig?

From: Anonymous at: 2013-11-23 00:08:48

-> Finished Dependency Resolution
Error: Package: amavisd-new-2.8.0-4.el6.noarch (epel)
           Requires: /etc/clamd.d
           Available: clamd-0.98-2.el6.x86_64 (epel)
               Not found
           Installed: clamd-0.98-2.el6.rf.x86_64 (@rpmforge)
               Not found


 yum install amavisd-new spamassassin clamav clamd unzip bzip2 unrar perl-DBD-mysql --disablerepo=epel

From: Anonymous at: 2014-01-17 22:54:00

In step 13 before you can run mysql_secure_installation, mysql must be running. To start it running type: /sbin/service mysqld start You will see output like this: Initializing MySQL database: Installing MySQL system tables... OK Filling help tables... OK To start mysqld at boot time you have to copy support-files/mysql.server to the right place for your system PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! To do so, start the server, then issue the following commands: /usr/bin/mysqladmin -u root password 'new-password' /usr/bin/mysqladmin -u root -h test.centos6564.home password 'new-password' Alternatively you can run: /usr/bin/mysql_secure_installation which will also give you the option of removing the test databases and anonymous user created by default. This is strongly recommended for production servers. See the manual for more instructions. You can start the MySQL daemon with: cd /usr ; /usr/bin/mysqld_safe & You can test the MySQL daemon with cd /usr/mysql-test ; perl Please report any problems with the /usr/bin/mysqlbug script! [ OK ] Starting mysqld: [ OK ]

From: 2 thingies at: 2014-02-21 17:03:36

I was stuck at 

 ./configure --prefix=/usr --sysconfdir=/etc --with-apr=/usr/bin/apr-1-config --with-apxs=/usr/sbin/apxs --with-apache-user=apache --with-setid-mode=owner --with-php=/usr/bin/php-cgi --with-logfile=/var/log/httpd/suphp_log --enable-SUPHP_USE_USERGROUP=yes

i was missing some packets so I did

yum groupinstall "Development Tools"

yum install apr apr-util apr-iconv apr-devel openssl-devel pcre httpd httpd-devel

 and only then i could go on


From: Martin Ledvina at: 2013-09-25 21:40:16

Always include a list of dependencies when installing outside of upstream providers:

Can't locate Date/ in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5) at /usr/local/ispconfig/server/scripts/vlogger line 148.
BEGIN failed--compilation aborted at /usr/local/ispconfig/server/scripts/vlogger line 148.
piped log program ' /usr/local/ispconfig/server/scripts/vlogger -s access.log -t "%Y%m%d-access.log" /var/log/ispconfig/httpd' failed unexpectedly

Which is a result of badly written requirements.

 How I diagnosed it:

yum whatprovides *Date/

yum install :perl-TimeDate-1.16-11.1.el6.noarch


From: at: 2013-10-10 09:56:37

Thank you. That's a great command to remember. Very helpful!

From: Natan at: 2013-11-01 12:33:37

Hi. I performed the settings as described on the website but can not access via ssh. I created customer - website - shell access in ISPConfig but can not login in PuTTY.
I'm testing the server in the local network with 2 computers (one windows 7 and centos 6.4). By Filezilla can access the sites via FTP tests normally, but SSH does not work.
Can you help me?

From: rlonghofer at: 2013-12-09 23:59:51

If you have done a minimual install of centos you need to also install jwhois otherwise you will not have any info in the emails from fail to ban on the ip address

From: at: 2013-03-21 20:22:37

Look out for this error! Mar 21 22:11:32 server1 clamd[18414]: Self checking every 600 seconds. Mar 21 22:11:33 server1 dovecot: master: Warning: Killed with signal 15 (by pid=18417 uid=0 code=kill) Mar 21 22:11:35 server1 dovecot: master: Dovecot v2.0.9 starting up (core dumps disabled) Mar 21 22:12:10 server1 postfix/smtpd[18526]: connect from localhost[::1] Mar 21 22:12:10 server1 dovecot: auth: Error: Can't open configuration file /etc/dovecot-sql.conf: No such file or directory Mar 21 22:12:10 server1 dovecot: master: Error: service(auth): command startup failed, throttling Mar 21 22:12:10 server1 dovecot: log: Error: service(auth): child 18528 returned error 89 (Fatal failure) Mar 21 22:12:10 server1 postfix/smtpd[18526]: fatal: no SASL authentication mechanisms Mar 21 22:12:11 server1 postfix/master[18347]: warning: process /usr/libexec/postfix/smtpd pid 18526 exit status 1 Mar 21 22:12:11 server1 postfix/master[18347]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling it happend to me both on 64Bit and 32Bit it stats that "/etc/dovecot-sql.conf" is not found thats true the file is in /etc/dovecot/dovecot-sql.conf open /etc/dovecot/dovecot.conf and replace. passdb { ## args = /etc/dovecot-sql.conf args = /etc/dovecot/dovecot-sql.conf driver = sql } userdb { ## args = /etc/dovecot-sql.conf args = /etc/dovecot/dovecot-sql.conf driver = sql } !!Allso the squirrelmail is configurated for courier but the Howto installs dovecot!! any ways keep it up..! nice work straightforward for newbie on CentOS

From: Kian Mayne at: 2013-05-25 12:05:37

Thank you so much, I wasn't eagle-eyed enough to notice the /etc/dovecot-sql.conf - /etc/dovecot/dovecot-sql.conf discrepancy!

 Dovecot is finally working :) Thanks a lot

From: at: 2013-07-27 19:06:22


 Thank you for this solution, it's been one week I am stuggling finally made it


From: Anonymous at: 2014-05-16 10:45:05

another solution

ln -s /etc/dovecot/dovecot-sql.conf /etc/dovecot-sql.conf

ln -s /etc/dovecot/dovecot.conf /etc/dovecot.conf

From: Anonymous at: 2013-12-16 06:16:25

Thank you!  I spent the last two hours trying to figure this out!  I appreciate you posting the fix!

From: almereyda at: 2013-12-30 21:49:49

Someone should file a bug report. Maybe I'll do that in the next days.

Because this fix did it for me, too, on a fresh install.

Still I'm wondering why ISPConfig is taking so long, as many bugs are already known and/or fixed.

Thanks for providing the solution, @psykosen.

From: andrewf at: 2013-04-02 13:58:08

I have been running a virtual server setup using your most excellent guides for a couple of years now (it was an open-suse, Apache, courier, ispconfig3 configuration) but one of the many sites I run may have been compromised today.

It was a Drupal site, and my "blind-panic"  response was to restore from the last known good DB backup which immediately resolved the problems on that specific site. As it is a security related site, it tends to be a target and I had noticed a concerted attempt to breach it over about a 3 hour period from the same IP address.

Anyway, what I would like to see added to the tutorial (and applicable to all of them), in a an approximate order of priority, is how to:

  1. Add Tripwire (or AFICK, etc) to the install/configuration
  2. Add mod_security and mod_evasive to the Apache setup
  3.  Add separate DB and mail servers, especially behind a DMZ.
  4. Configure partitions so your web sites were on a separate partition (disc/LVM) and the effect that has on quota configuration where file uploads are a major consideration else the DB files where it is mainly content driven, and hence the (typically) /var partition for MySQL databases, whether an "all in one" server or separated by role.
  5. Setup the email notifications (both local and via a 3rd party such as gmail) for all the alerting including rkhunter, clamav, and tripwire.
  6. Optimal configuration of Apache log files for use by AWStats

These are (I feel) pretty small changes to this "most excellent" tutorial, and given I run 18 web sites from 1 virtual server, + 10 other virtual development machines from Windows XP, through Win7 to Server 2008 R2 and Windows 8 all on a box with 2 Tb of disc and 16 Gb ram which cost me AU$800 to build, it is not a high-end system, but well within the reach of most people.

 I would be more than happy to help with the tutorial updates.


From: Anonymous at: 2014-12-09 18:23:41

Thanks for the additional info for further securing.

 +1 for adding it to the guide(s)

From: linuxuzerno1 at: 2013-05-26 15:15:36

SquirrelMail Configuration : Read: config.php
While we have been building SquirrelMail, we have discovered some
preferences that work better with some servers that don't work so
well with others. If you select your IMAP server, this option will
set some pre-defined settings for that server.
Please note that you will still need to go through and make sure
everything is correct. This does not change everything. There are
only a few settings that this will change.
Please select your IMAP server:
bincimap = Binc IMAP server
courier = Courier IMAP server
cyrus = Cyrus IMAP server
dovecot = Dovecot Secure IMAP server
exchange = Microsoft Exchange IMAP server
hmailserver = hMailServer
macosx = Mac OS X Mailserver
mercury32 = Mercury/32
uw = University of Washington's IMAP server
gmail = IMAP access to Google mail (Gmail) accounts
quit = Do not change anything

Command >> <-- dovecot

SquirrelMail Configuration : Read: config.php
While we have been building SquirrelMail, we have discovered some
preferences that work better with some servers that don't work so
well with others. If you select your IMAP server, this option will
set some pre-defined settings for that server.
Please note that you will still need to go through and make sure
everything is correct. This does not change everything. There are
only a few settings that this will change.
Please select your IMAP server:
bincimap = Binc IMAP server
courier = Courier IMAP server
cyrus = Cyrus IMAP server
dovecot = Dovecot Secure IMAP server
exchange = Microsoft Exchange IMAP server
hmailserver = hMailServer
macosx = Mac OS X Mailserver
mercury32 = Mercury/32
uw = University of Washington's IMAP server
gmail = IMAP access to Google mail (Gmail) accounts
quit = Do not change anything

Command >> courier

imap_server_type = courier
default_folder_prefix = INBOX.
trash_folder = Trash
sent_folder = Sent
draft_folder = Drafts
show_prefix_option = false
default_sub_of_inbox = false
show_contain_subfolders_option = false
optional_delimiter = .
delete_folder = true
Press enter to continue... <-- press ENTER

Ignore the second set of instructions! 

(unless they get deleted)

From: Jamie Bond at: 2013-08-15 23:16:05

Thank you for this very useful guide! Kind Regards.

From: at: 2013-09-06 18:24:40

 hello I just followed the tutorial for centos 6.4 but I have the page Defaux apache I can not have access to the page ispconfig 

From: ANRES at: 2013-12-17 22:15:09

I followed the manual but I can not enter ispconfig web site, enter the default can help me?


From: Gyrocode at: 2014-02-07 15:11:23

I went back and reviewed users' comments for previous versions of this tutorial. Here is what I found here.

php-eaccelerator conflicts with Apache and causes the error. It can be removed by running the following commands:

rpm -e php-eaccelerator
service httpd restart

From: Kaan Varol at: 2013-12-27 17:29:01

Thank You for this great tutorial. Much much appreciated.

From: Erik at: 2014-01-02 15:20:47

 First:  GREAT STUFF!  I really appreciate your work in this package and it really does KICK ASS!

 Second:  Postfix kept coming up with "fatal: open database /etc/postfix/virtual.db: No such file or directory" and was unable to start properly.

 The solution was "postmap /etc/postfix/virtual" to build the virtual.db then restart postfix.

Thanks again!

From: Anonymous at: 2014-02-06 22:00:32


              Hi , i have used 'Perfect server Centos 6.3 with Courier' with for Centos 6.5

The problem appears when i add a ssl website . The ssl certificate is working but the page still remains default Apache 2 . Doesn't change like when you add a http website with ispconfig 3, and because of that i cannot acces https pages , it tells me that it cannot be found.


Not Found

The requested URL /admin/ was not found on this server.

Apache/2.2.15 (CentOS) Server at Port 443

 The site is working fine when it is only with http

From: Thevan at: 2014-03-03 11:26:29


 Has followed the installation guide without any error, But when put for example  i am getting 


<title>400 Bad Request</title>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
Instead use the HTTPS scheme to access this URL, please.<br />
<blockquote>Hint: <a href=""><b></b></a></blockquote></p>
If put 
I am getting apache test page only 
Please advise 


From: Anonymous at: 2014-06-05 23:33:44

Same issue. when i go to my server with :8080, no response. Just apache test page. Please advise!!!!!!!

From: at: 2014-03-03 11:33:50

setup without any error , but when access

getting belwo page only 


<title>400 Bad Request</title>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
Instead use the HTTPS scheme to access this URL, please.<br />
<blockquote>Hint: <a href=""><b></b></a></blockquote></p>

Please help


From: faizan at: 2014-04-28 08:32:29

Dear All,

While i am running step 24.(entering url ) was generating error saying that..error 404 not found 

From: dendic at: 2014-04-29 12:43:35

I am a novice. What should I install with ISPConfig 3 if the web server is set by the existing farm servers.I already have separate mail server  in system farm  room. What do I need to install the software import the ispconfig 3  with already existing mail server '(postfix, dovecot, GetMail, mailman.squirellmail??)

 My aim is to this Web server set up several websites with which you could make several email addresses and email addresses that I cherish the already existing mail server in the server room.

From: dendic at: 2014-05-02 07:55:36

Can someone put an example configuration file  if I have to relayhost separate mail server system in the hall and I just need to add a (local) for option mydomain =    in etc/postfix/  

From: Lucasc at: 2014-10-06 19:00:22

I'm getting:


Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.


Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.


When trying to access:

 How to fix it, please?

 Thank you!

From: ed at: 2015-04-29 13:25:14

I have problem with send mail.All mails stoped in maildrop folder.i tryed root .. #echo "Test mail" | mail -s "test" but nothing.Whats wrong? :

alias_database = hash:/etc/postfix/aliasesalias_maps = hash:/etc/postfix/aliasesbody_checks = regexp:/etc/postfix/body_checksbroken_sasl_auth_clients = yescommand_directory = /usr/sbinconfig_directory = /etc/postfixcontent_filter = amavis:[]:10024daemon_directory = /usr/libexec/postfixdata_directory = /var/lib/postfixdebug_peer_level = 2header_checks = regexp:/etc/postfix/header_checkshome_mailbox = Mailboxhtml_directory = noinet_interfaces = allinet_protocols = ipv4mail_owner = postfixmail_spool_directory = /var/spool/mailmailbox_command = /usr/bin/procmail -Y -a $DOMAINmailq_path = /usr/bin/mailq.postfixmanpage_directory = /usr/share/manmime_header_checks = regexp:/etc/postfix/mime_header_checksmydestination =, localhost, localhost.localdomainmydomain = xxx.netmyhostname = = [::1]/128myorigin = xxx.netnested_header_checks = regexp:/etc/postfix/nested_header_checksnewaliases_path = /usr/bin/newaliases.postfixproxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virt ual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipien t_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonica l_maps $relocated_maps $transport_maps $mynetworksqueue_directory = /var/spool/postfixreadme_directory = /usr/share/doc/postfix-2.6.6/README_FILESreceive_override_options = no_address_mappingsrelay_domains = mysql:/etc/postfix/mysql-virtual_relaydomains.cfrelay_recipient_maps = mysql:/etc/postfix/mysql-virtual_relayrecipientmaps.cfrelayhost = $mydomainsample_directory = /usr/share/doc/postfix-2.6.6/samplessendmail_path = /usr/sbin/sendmail.postfixsendmail_path = /usr/sbin/sendmail.postfixsetgid_group = postdropsmtp_tls_security_level = maysmtpd_client_message_rate_limit = 100smtpd_client_restrictions = check_client_access mysql:/etc/postfix/mysql-virtual _client.cfsmtpd_recipient_restrictions = check_recipient_access mysql:/etc/postfix/mysql-v, permit_mynetworks, permit_sasl_authenticated, reject_unauth _destinationsmtpd_sasl_auth_enable = yessmtpd_sasl_authenticated_header = yessmtpd_sasl_path = private/authsmtpd_sasl_type = dovecotsmtpd_sender_restrictions = check_sender_access mysql:/etc/postfix/mysql-virtual _sender.cfsmtpd_tls_cert_file = /etc/postfix/smtpd.certsmtpd_tls_key_file = /etc/postfix/smtpd.keysmtpd_tls_security_level = maysmtpd_use_tls = yestransport_maps = hash:/var/lib/mailman/data/transport-mailman, proxy:mysql:/etc/ postfix/mysql-virtual_transports.cfunknown_local_recipient_reject_code = 550virtual_alias_domains =virtual_alias_maps = proxy:mysql:/etc/postfix/, prox y:mysql:/etc/postfix/, hash:/etc/mailman/virtual-mai lmanvirtual_gid_maps = static:5000virtual_mailbox_base = /var/vmailvirtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cfvirtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cfvirtual_transport = dovecotvirtual_uid_maps = static:5000


From: elvamo at: 2015-05-06 01:55:04

Im Finish tutorial but

How Update to:

Apache httpd 2.4.12 ReleasedPHP 5.4.40 ReleasedPHP 5.6.8 is availableMySQL-Versión: 5.1.73phpMyAdmin 4.4.5