Atomicorp

I must admit I'm a bit behind with the Plesk 10 release - I'm sticking to 8.6 for now.

I happened to come accross a few posts in the 10.x section of the Parallels forum that are worrying me. Can someone shed some light on this please?

I'm talking about this:
http://forum.parallels.com/showthread.php?p=450852
http://forum.parallels.com/showthread.php?t=111846
http://forum.parallels.com/showthread.php?t=112464

The implication seems to be that (for 10.2 at least) Parrallels ship custom Apache, PHP and OpenSSL for Centos 5.6, and that other versions can't be used.

That can't be right, surely? I must have misunderstood?

Faris.

faris wrote:I must admit I'm a bit behind with the Plesk 10 release - I'm sticking to 8.6 for now.

+1

You only get the custom httpd packages if you select you want Apache with SNI support in the Plesk installer, because the default repo packages don't have support for SNI.

And I guess you only get the custom PHP packages if you select PHP 5.3 in the Plesk installer. I recommend going with the regular PHP support and then upgrading to the PHP packages in Atomic.

Ah! SNI. Missed that. Hence the requirement for the custom OpenSSL too. Got it. Thanks Breun! So it isn't as bad as it looks.


Faris.

it also appears that Windows XP doesnt support SNI in its TLS stack - and based on the stats here
http://www.w3schools.com/browsers/browsers_os.asp

It would seem like almost half of web users (not counting people behind proxies or some wierd routing which may not support it also) wouldnt be able to use SNI - so at this point it still a mystery to me why anyone would want to use it at all with a risk that nearly half of your potential web traffic cant access your site in SSL.

*disclaimer - I realize those stats are not perfect and may not be 100% factual but should give a good overview

It would seem like almost half of web users (not counting people behind proxies or some wierd routing which may not support it also) wouldnt be able to use SNI - so at this point it still a mystery to me why anyone would want to use it at all with a risk that nearly half of your potential web traffic cant access your site in SSL.

Ditto. Its why we dont use it.

Oh sh*t ...
I installed on the new testing box with sni support. I just read all the issues with it !!! :/

The worst thing is that when I run the autoinstaller of plesk and I set normal apache it says you allready have the latest version.

Any advice on what I should do ?

Cant believe it ...

I removed http through yum which removed a ton of things.

Then I rerun plesk autoinstaller. Allthough everything seems to work fine I feel it takes longer to load a web page. Can you think of anything that might have gone bad ?

Update : Ahmm. When I shut down the firewall the problem goes away.
The same rules I have in the other box and there is no problem at all. Rules are simple. Port 80 accept ...
This is more weird than ever now ...

nobody wrote:I removed http through yum which removed a ton of things.

Then I rerun plesk autoinstaller.

I'd recommend just downgrading httpd itself next time, without removing and then reinstalling half of your setup.

breun wrote:

nobody wrote:I removed http through yum which removed a ton of things.

Then I rerun plesk autoinstaller.

I'd recommend just downgrading httpd itself next time, without removing and then reinstalling half of your setup.

I got pissed off and since this box was still in beta phase I reinstalled it. It actually takes less time than trying to debug parallels products