Problem with SSL and Plesk 11

[DanielRamos]

Hi all

First of all, english is not my native language, sorry for any mistake.
My problem is not new, I think.
I spent a entire day researching about this, read a LOT of topics on this forum and google, and couldnt solve the problem,
so.. i´m here asking for help.

The server is a CentOS 6.3 running Plesk 11.0.9 with Update #49 on Amazon EC2.

The thing is:
I installed a Godaddy SSL standard certificate through plesk.
The certificate is for a single domain (installed for a subdomain only "ssl.mydomain.com", not the main domain), and seems to be correctly installed.

Using http://ssl.mydomain.com the page opens with no problem, but when I use https://ssl.mydomain.com, the connection is refused.
After some search, I figured out that is related to nginx.
So, I disabled nginx and I could open https page, looks like the certificate is not verified, but its another problem that I´ll check later.
"Solve" one problem but... all other domains and subdomains opens with the default plesk page, exactly this problem: http://kb.parallels.com/en/115806.

I don´t know if I didnt understand the proposed solution, or it´s not working for me.

The Address from the Non-authoritative answer returned by nslookup command to my ssl.mydomain.com, is the same IP address configured in the domain´s hosting setup (the dedicated ip address).
Is as it should be, right?

Everything is in the same plesk server, there is no reason to have any domain with different IP..

Anyway, the solution tells me: "..re-assign the domain to this IP address..", so, I went to the domain´s Web Hosting Access panel, and clicked on save with no change (the domains´s ip is already the dedicated ip that should be), but no effect.

All this to try disable nginx, since I know that nginx is causing trouble with https..
But the best of the worlds, would be to have nginx working with ssl.

I read something about ssl issues with nginx, but should be fixed on earlier updates...

I did the famous command:
/usr/local/psa/admin/bin/httpdmng --reconfigure-all

And nothing..

Some additional information:
The main domain data, was imported from a plesk 8.6 at mediatemple, but the subdomain where the ssl is installed, is new, was not imported.
I dont know if there is any configuration that could be imported and causing this behavior, or it´s just the nginx that is buggy.

With exception of this, everything else works very well.

I´ll apreciate any help.

Thanks

Daniel

 

[AdamSa12]

I have a simmilar problem... did you solved your problem? Is SSL working on your server?

 

[DanielRamos]

No.. I gave up.
In my case, I just needed ssl for a facebook tab page, that requires the content accessible through https.
I solved using heroku to host the content, if I use their subdomain, I can use https.

If I really need ssl on my server, I think I'll need to use another server..

;/

 

[devaspora]

The good ole Plesk team really cares for its customers. Very bad support Plesk; quite shameful.

 

[Faris Raouf]

This is a user-to-user forum. You need to raise a ticket if you want official parallels support.

Any user who can help and has time to do so will reply to the message. Unfortunately it looks like nobody had time on this occasion, especially as it seems to be quite a complicated issue with multiple possible causes, including possibly a problem with the certificate itself.

 

[devaspora]

Yes, I have to put in a $50+ ticket to try to fix a software bug that Plesk QA team could not originally find. That is what I call great consumer support.

 

[Faris Raouf]

But any issue identified as a bug is refunded. Or was it more complicated than that? i.e. they could not find the cause of the problem?

 

[devaspora]

That is regardless of the fact that charging for support pertaining to product issues shows poor consumer service and a disregard for the consumer. Support and product reliability is the biggest reason people put down the money for a cPanel license.