Hi! Its been more than five months since i started using ispconfig3 and im really happy but...there is a monster in the story (muaahhaha) APACHE2 Why..if any user/client of ISPConfig3 makes something wrong every client must be punish O_O. E.g. If someone install bad an SSL (someone copied the Certificate Issuer into SSL Bundle) apache will refuse to start. Why that kind of things happen ? is there a solution ?.
Thats a problem of apache in general, instead of skipping a invalis ssl cert, it just hangs. ISPConfiog 3.0.4.6 catckes most issues that can cause apache to afila nd rolls back the configuration in this case, the only missing part is SSL rollback which has been implemented in 3.0.5. Apache is not fault tolerant when it comes to ssl certs and a apache config test succeeds in this case while it should fail as apache wont start later. Update to ispconfig 3.0.5 when it is released. We implemented a config rollback for ssl certs.
