Archive for the ‘ISPConfig 3’ Category

A copy of a incoming email can be sent to a second email address by adding a cc command to the "Custom Rules" field of the mailbox in ISPConfig.

ISPConfig supports sieve as well as maildrop filter rules. The rule language depends on the LDA / POP3 / IMAP-Daemon that you use on your server. If you use courier, then the filter language is maildrop. When dovecot is installed, then the filter language is ieve.

Example in maildrop syntax:

To send a copy to the email address info@example.tld, add the following code at the beginning of the custom rules field.

cc '!info@example.tld'

Example in sieve syntax:

redirect 'info@example.tld';
keep;

If you get the following error message in Ubuntu when you use PHP based shell scripts:

PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20060613+lfs/htscanner.so' - /usr/lib/php5/20060613+lfs/htscanner.so: cannot open shared object file: No such file or directory in Unknown on line 0

Then edit the file /etc/php5/cli/php.ini:

vi /etc/php5/cli/php.ini

and remove the lines:

[htscanner]
Extension = "htscanner.so"
config_file = ".htaccess"
default_docroot = "/var/www"

As the htscanner module works only for scripts within webservers but not for commandline scripts.

Postfix: “queue file write error”

Friday, August 21, 2009 posted by admin

If you get an error like:

Aug 21 12:41:03 webb4 postfix/sendmail[11234]: fatal: web1_user(12967): queue file write error

in your mail log, then the vale for message_size_limit in postfix main.cf is too low. Edit postfix main.cf:

vi /etc/postfix/main.cf

and set the message size limit to a higher value. E.g.

mesage_size_limit = 900000000

and restart postfix:

/etc/init.d/postfix restart

If there is no message_size_limit set in main.cf, just add the line.

If you run a joomla or wordpress installation with mod_php, the following settings in the vhost configuration file or the "Apache directives" field in ISPConfig can be used to set stricter securitypolicys. This helps limit the impact of a possible hack to this websiteand protect the other sites on the server.

php_admin_value disable_functions "show_source system shell_exec passthru exec phpinfo popen proc_open"
php_admin_flag allow_url_fopen Off
php_admin_value session.save_path "/var/www/webXXX/phptmp/"
php_admin_value open_basedir "/var/www/webXXX/:/tmp"

Explanation

disable_functions disables functions that have a potential security impact e.g. because they allow the execution of external applications.

allow_url_fopen disables the ablity to open files via an URL.

session.save_path sets the path were php stores its session files. For ISPConfig 2, the path is e.g. "/var/www/webXXX/phptmp/" and for ISPConfig 3 the path is like "/var/www/clients/client1/web1/tmp/" If you dont use ISPConfig, set this path to a directory which is writable for the webserver user. the directory should be unique for every website.

open_basedir sets the path were php scripts are allowed to open files. For ISPConfig 2, the path is like  "/var/www/webXXX/" and for ISPConfig 3 the path is like "/var/www/clients/client1/web1/" If you dont use ISPConfig, set this path to a the root directory of this vhost. With :/tmp we allow php scripts to use also the /tmp directory of the server.

Fail2ban uses iptables by default to block incoming connections when they exceed the max.  login retrys. The iptables rules used by fail2ban might conflict with the firewall rules, so it might be nescessary to reconfigure fail2ban to use the route command for blocking incoming connections.

To reconfigure fail2ban for using the route command instead of iptables, edit or create the route.conf file:

vi /etc/fail2ban/action.d/route.conf

And insert the following lines:

# Fail2Ban configuration file

[Definition]
actionban = ip route add unreachable <ip>
actionunban = ip route del unreachable <ip>

Then add or change the banaction in the jail.local file in the [DEFAULT] section to "route":

vi /etc/fail2ban/jail.local

And add or edit these lines:

# Fail2Ban configuration file

[DEFAULT]

banaction = route

Webalizer stats only showing 1 or 2 days?

Monday, August 17, 2009 posted by admin

If webalizer statistics of your website are only showing the last 1 or two days instead of all days since the website has been created, you have to activate incremental processing in the webalizer configuration file (/etc/webalizer.conf or /etc/webalizer/webalizer.conf depending on the Linux distribution).

vi /etc/webalizer/webalizer.conf

Change the line:

# Incremental     yes

to:

Incremental     yes

Where can I request ISPConfig features?

Thursday, August 6, 2009 posted by Till

Please post feature requests to the ISPConfig bugtracking system:

http://bugtracker.ispconfig.org

Where can I report bugs in ISPConfig?

Tuesday, August 4, 2009 posted by Till

Please report bugs in ISPConfig to the bugtracking system:

http://bugtracker.ispconfig.org

Enable SSL for the ISPConfig 3 Controlpanel Login

Monday, August 3, 2009 posted by Till

Hint: The procedure that is described below is for ISPConfig versions < 3.0.3. For newer ispconfig versions, use the builtin ssl certificate creation function of the ispconfig updater instead. The steps below should only be used to manually create a new SSL certificate in case that you can not run the updater on your installation.

The ISPConfig controlpanel login is running on http by default. This short tutorial shows you how to enable SSL encryption (https) vor the ispconfig vhost.

1) Make the directory for the SSL certificate:

mkdir /usr/local/ispconfig/interface/ssl
cd /usr/local/ispconfig/interface/ssl

2) Create the SSL certificate files

openssl genrsa -des3 -out ispserver.key 4096
openssl req -new -key ispserver.key -out ispserver.csr
openssl x509 -req -days 3650 -in ispserver.csr \
-signkey ispserver.key -out ispserver.crt
openssl rsa -in ispserver.key -out ispserver.key.insecure
mv ispserver.key ispserver.key.secure
mv ispserver.key.insecure ispserver.key

3) Enable the mod_ssl module

a2enmod ssl

4) Edit th ISPConfig vhost file

vi /etc/apache2/sites-available/ispconfig.vhost

and insert the following lines insert the fallowing lines between the "<VirtualHost ....></VirtualHost>" tags:

SSLEngine On
SSLCertificateFile /usr/local/ispconfig/interface/ssl/ispserver.crt
SSLCertificateKeyFile /usr/local/ispconfig/interface/ssl/ispserver.key

5) Restart apache2

/etc/init.d/apache2 restart

The ISPConfig controlpanel login is now reachable on port 8080 by https.