Hi everyone! First of all I must tell you what a great work the people from ispconfig are doing. And the “perfect server” howtos are awesome. Well, to the point: I recently upgraded a test server fom Ubuntu 12.04 (Server LTS) to Ubuntu 14.04 (Server LTS) and I ran in to a lot of problems, wich I mostly solved, but there is still the issue with updating all the scripts to Apache 2.4 compatible ones so I can dissable the “compat” module. As many before me I could not access the control panel, but with some debugging I managed to get access to it. To make it more readable I will try to make a list of the current sistuation. All the services are running, with a little help from the http://www.howtoforge.com/perfect-server-ubuntu-14.04-apache2-php-mysql-pureftpd-bind-dovecot-ispconfig-3 guide and a lot of debugging I managed to get the mailserver running again and most other services so also the apache in compat mode. I can access the Ispconfig control panel and all of my sites are working, but they are working with the “compat” module and using the old auth config style. Now, I get a little confused, since in the “apt-listchanges” mail I get after upgrade This means a lot of manual labour, and there is a script to help you with this, but I was better of by using the backup /etc/apache2/sites-* files to get things working. Now, the problems are the following. When I change the configuration of a site, it updates it to the new “Require All Granted” syntax, and I get the “access_compat:error **** AH01797: client denied by server configuration:” error. The same happens when I create a new site. Most of the theads in this and other forums puts focus on getting it running, but I want to keep my installation and make it wor without the mod_compat mode.. So these are my questions: Is there any real upgrade guide for this? Not only running “php -q update.php” but a guide thats really tells you what is going on so that ISPconfig can manage the sites as it should. Is it possible? According to the upgrade documentation from ubuntu all the vhost files must be named *.conf and then be included by a2ensite *.conf, Ispconfig names the symlinks in /etc/apache2/sites-enabled to [domain].[tld].vhost. Will this work outside the compat mode? I suppose so since there must be thousands of sites running this configuration. I understand that there must be a conflict in the configurations, I suppose that we can not mix the “allow, deny” syntax with the “require”. But it seems strange, is it possible to use the “require” syntax in the main configuration files and the “allow deny” in some vhost? Why is there else a compat mode? Well, I understand that this are not some simple questions, but I think that there are many uot there searshing for the same answers.. Ps. I am currently reding the apache documentation on access control and upgrading. http://httpd.apache.org/docs/current/howto/access.html http://httpd.apache.org/docs/2.4/upgrading.html But there is nothing about the .conf in this documents, ut will it work in a Ubuntu envirement or is this compiled in the binary?