SSL certificate problems

[Pauli Jokela]

Hey all,

I'll go right out and tell you the domains I currently use with Plesk, as it'll be easier that way.
I'm trying to use the same SSL certificate for both Plesk and my main domain/site, just can't seem to do it.

I'm running Plesk on a GoDaddy VPS, which for some reason restores it's hostname back to the original everytime I change it.

So, the problem is that I've set up a certificate for didstopia.com, but at the moment https://didstopia.com does NOT have a valid certificate, while https://didstopia.com:8443 does.

Thing is, I set didstopia.com's SSL certificate as the default one, as I can't seem to change any of my domain's certificates, none.

The domain/hostname that the VPS keeps resetting to is ip-97-74-126-69.ip.secureserver.net, so for example, if I log out of https://didstopia.com:8443, I'll be redirected to https://ip-97-74-126-69.ip.secureserver.net:8443.

Same thing kinda happens when I log in to Plesk, as the top of the page is using the right (didstopia.com's certificate) while the bottom is using the self-signed certificate.

Either Plesk is royally screwed on this box, or I've missed something.

I appreciate all the help, so please, even if it's just a tip, share it with me.

 

[Yeolegood]

You need to check that domain specified uses dedicated IP address and not shared one.
In case these requirements are met but the issue is still there, it most likely means that changes for some reason were not applied. Please run websrvmng --reconfigure-vhost --vhost-name=<domain.tld>
binary is located in %plesk_bin% on Windows OSor in /usr/local/psa/admin/sbin on Linux OSes.

 

[Pauli Jokela]

I've tried reconfiguring the virtual host now, let's see if that helps.

Also, I had forgotten about the exclusive/dedicated IP address part, that's now fixed too.

I'm now able to choose SSL certificates for the domain didstopia.com, but, can I use one SSL certificate for all https traffic on didstopia.com aswell as Plesk? Since Plesk seems to be able to use the same SSL certificate, but it also seems to be using it's own self-generated cert.

You'll notice it if you try to visit https://didstopia.com:8443, how the actual index part of the site is using the correct SSL certificate, but the content (lower) part isn't.

 

[Pauli Jokela]

Oh, one more thing.

I noticed that it's the port 11444 that's using the self-generated SSL certificate, but obviously, it should be using the one that I've specified for Plesk, no?

See here: https://didstopia.com:11444/

 

[Pauli Jokela]

Bumping this up, since this is rather crucial for my business.

 

[Denis Sirochenko]

Hello Pauli,

TCP 11444 port is used by Single Sign-On service in Plesk 9.2.1. The folowing Knowledge Base article contains some information on the subject:

[How to] How to install custom SSL certificate on SSO server?
http://kb.odin.com/en/6138

Regards,
Denis

 

[Pauli Jokela]

Still no replies, so I'll just post an update to this.

Now, it would seem that the "Secure Control Panel" button sets the specified SSL cert as the default for the web-interface on port 8443, but NOT on the relay port 11444. This is either a bug, or I'm doing something wrong here?

Is there a way to manually swap out the self-signed certificate with my own, so that I can finally secure Plesk and get things started?

 

[Pauli Jokela]

Solved the SSL problems!

I fixed it, finally!

I'll put up the solution here for anyone who's also experiencing this problem.

All I had to do was run these commands to get the certs and correct hostnames working:

/usr/local/psa/bin/server_pref --update -hostname <new hostname>
/usr/local/bin/sso -s -server https://<new hostname>:11443 -url https://<new hostname>:11444

Easy as pie, just wish I'd known about that before. FYI, I also disabled SSO completely (/usr/local/bin/sso --disable).