Update fails in updateing apache2.conf
When I ran the update (from 2.1.0 to 2.1.1) the setup added ISPCONFIG settings to apache2.conf without deleting the old information. In my case it created errors with the virtual name servers.
After removing the old settings manualy the problem was over.
Can in the future the update procedure detect this? Also creating the ssl certificates is unnecessary because they are already available when doing an update.
A lot of more config files are changed. This means that I have to correct al changes manually! This isn't good!
Last edited by joostvdl; 18th November 2005 at 15:21.