I'm trying to find why ISPCONFIG is generating Vhosts without the SSL Engine Parameters. I've a unique Domain per IP for SSL, I've selected (Create Certificate) and ISPCONFIG is creating them under /var/www/domain.com/ssl It seems to be fine but still when ISPCONFIG re-generates the VHOST information it does not add SSL. I see on vhosts.conf.master <tmpl_if name='ssl_enabled'> <IfModule mod_ssl.c> So it seems that it checks for a template named: "ssl_enabled". Does anybody knows how can I debug the template generation ? Having 443 open but without the vhosts assigned generates the error: "SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long)", seem many people complaining about that.
I have exactly the same problem on an ISPConfig3 server. An Unique IP-address, a brand new SSL-certicate, but the SSL-Engine parameters are not generated!
This means that the ssl file was not generated correctly and ispconfig does not put the ssl part in as apache wont start anymore aftrewards. Recreate the ssl cert in ispconfig and check the entrys that you have made. Do not enter any special chars or characters like "umlauts" or accents.
