It seems that all-of-a-sudden, checking the SSL box in any given website's configuration has no effect when ISPConfig rewrites the website's vhost configuration file (in /etc/apache2/sites-available/example.com.vhost). The `webdomain`.`ssl` value for the website in question is indeed "y", yet the updated vhost file, which has a correct/current modification time after making the change, does not contain any of the required SSL directives. It seems that simply saving any given website's configuration causes the vhost file to lose any previously-defined SSL settings. I discovered this issue because I went to change a configuration option unrelated to SSL, clicked the "Save" button, and then noticed that SSL was no longer operational on the site in question. What might be happening here? ISPConfig 3.0.4.2 on Ubuntu 10.04.1
Updating ISPConfig to 3.0.4.3 did not resolve the issue. For what it's worth, I have a development server that is configured more or less identically and the issue does not seem to occur there.
This thread pointed me in the right direction: http://www.howtoforge.com/forums/showthread.php?t=54612 As it turns-out, a valid SSL certificate was not present in /var/www/example.com/ssl. To enable customers who do not wish to purchase their own SSL certificates to use our shared certificate, I normally create symbolic links to the applicable files in the given website's "ssl" directory. I simply forgot to do that here. My bad!