Today one of our clients report that their shared ssl subdomain is not working - client claims it was working yesterday. Jodo support tell me
Currently,We are not offering the shared SSL for the Sub-domains.
typical useless answer without any explanation. When did you decided this? Why dont you tell your resellers about this change? Why not give some reasonable explanation - what cause this change?
I am tired of hearing bad news from you - you change data center for second time - all of our net sites stopped working because your panel changed asp.net version after migration, we had problem after problem - mysql databases encoding problems, asp.net write permissions not working after migration, control panel is so slow at night that it is practicaly unusable, we cant even use sql management studio to manage database remotely , etc.
This issue is coming due to the move to 2048bit SSL certs and Hsphere not wanting to accept it properly. We would recommend a move to a dedicated IP and then using StartSSL to make yourself a free certificate, it will be non shared, and also allow you to use your domain directly. Notice to all StartCom subscribers
There is apparently a problem with current Hsphere version and the SSL certificate used for Shared SSL feature. We need to forward this issue to Parallels for further investigation. This process can take much time.
As a convenient alternative we suggest you to try free SSL certificate from startssl.com.
It was announced in this that Shared SSL was not functional and being stopped for temporary. It is an hsphere issue and while there is some work on it by parallels introducing that into the mix of the migrations would be a very big challenge.
This should not have been a surprise, look on your mail of ‘important notes’ from April 20. Point number 6.
Shared SSL may not load after migrations due to incompatibilities with Hsphere, this is also impacting existing customers that make any change. This emails serves as notice of a temporary suspension of shared SSL services.