This is a post I made on parallels forum. If I can get this resolved, I’ll share the solution:

http://forum.parallels.com/showthread.php?p=432805&posted=1#post432805

parallels, upgrading to 10 is a mess!!!!!!!!!!!!!!!!!!!!!!! I’ve been running plesk since version 6 and have had a few problem when upgrading. Nothing to the extent of this mess I’m experiencing with my painful upgrade to v10.x! You’re seriously sucking days out of my life trying to get apache2 to remain running after ANY changes are made to a domain. I.e., adding a sub-domain, enabling SSL, etc… things my “customers” not “clients” (that’s an entirely different rant) can do in their new convuluted, messed up, wtf were you thinking parallels – control panel! Thanks for taking a crap on my server.

I regress… From my apache2 error logs i believe something has to be happening with the SSL certs.

So, I disabled SSL from every domain, turned off Horde and AtMail (they both use SSL), removed all certificates and made a self-signed certificate for my server. And voila, I was able to restart apache inside Plesk. As soon as I enable SSL on a domain the ball of apache2 wax melts all over the server and I have to start plesk. I wrote a shell script “apache2-restart.sh” because I have to do this process everytime I make a change

apache2-restart.sh
Quote:
/etc/init.d/apache2 stop
#
# restart – because Parallels blew up Apache
#

# sleep
sleep 5

# kill running instances
killall apache2

# start apache
/etc/init.d/apache2 start
after you make your script. make sure you chmod +x to the file to make it executable.

Quote:
chmod +x apache2-restart.sh
sometimes I have to run the script twice because of the fail to bind to port error appears…

that should save you a few keystrokes. If I was good at writing shell scripts maybe I could write a cron job to check if Apache is running properlly and restart. The problem is the pid / apache2 daemon are actually running but all sites are down………………..

so, what is SSL doing?

Quote:
[Wed Dec 15 20:52:36 2010] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!!
After google’n this one for a while. I believe the vhost config should not include the port “:443” for the virtual domain

These are samples I’ve found…
incorrect conf
Quote:

ServerName www.domain.com:443
DocumentRoot /home/directory/html
SSLEnable
SSLCertificateFile /www.domain.crt
SSLCertificateKeyFile /www.domain.key

The VirtualHost example below is the correct method of using an SSL enabled VHost. As you can see :443 has been removed from the ServerName parameter.

Quote:

ServerName www.domain.com
DocumentRoot /home/directory/html
SSLEnable
DocumentRoot /home/directory/html
SSLEnable
SSLCertificateFile /www.domain.crt
SSLCertificateKeyFile /www.domain.key

instead of the VirtualHost IP, maybe use the domain?

Quote:

ServerName domain.com
DocumentRoot /home/directory/html
SSLEnable
DocumentRoot /home/directory/html
SSLEnable
SSLCertificateFile /www.domain.crt
SSLCertificateKeyFile /www.domain.key

As pschneider pointed out, I’ve also modified these files to remove the port :443

Quote:
I have modified some of the template-files in “/usr/local/psa/admin/conf/templates/default/” and “/etc/apache2/ports.conf”
However, I *HAVE NOT HAD SUCCESS* changing these files and rebuilding / reconfigure the domain using httpdmng in your_psa/admin/bin/

I’m wondering if anyone else could shed light? Also, what OS are you having difficulty with? I’m on ubuntu 8.04 LTS.

Thanks!