Resolved SQL Issue - Lets Encrypt

[mattd29]

I have secured my Plesk panel and master domain under one SSLfrom GoDaddy and that works great now I have another domain that I added and used Let's Encrypt to secure it now when I browse to their https page it shows invalid cert and shows the one relating to my master domain for plesk control panel is that right ?

So Site A is master and its xyz.co.uk:8443 and identifies as xyz.co.uk
Site B is abc.co.uk:8443 and identifies as xyz.co.uk

This causes site B to look insecure, also lets encrypt certs appear to have no CSR and only partial certificate entries when you view their details.

This also breaks TLS/SSL mail from being sent or received at site B as it see's Site As cert and rejects it.

 

[Bitpalast]

Have you selected the "Let's Encrypt" certificate from the SSL drop down box in SSL configuration of that domain?

 

[mattd29]

Have you selected the "Let's Encrypt" certificate from the SSL drop down box in SSL configuration of that domain?

Yes when you go to abc.co.uk the SSL works, when you go to abc.co.uk:8443 it fails and looks at certificate for xyz.co.uk marking it as insecure as it doesn't match the domain.

 

[Bitpalast]

Isn't port 8443 reserved for Plesk panel? You are using two different domains to access Plesk panel on the same host? The behavior you are describing is correct, as only the Plesk host domain ought to be accessible with a cert on port 8443, but not an additional client domain. The host will return the host domain's cert if queried on port 8443.

When you access your client domain on port 443 (or https://abc.co.uk), do you still receive an SSL error?

 

[mattd29]

Isn't port 8443 reserved for Plesk panel? You are using two different domains to access Plesk panel on the same host? The behavior you are describing is correct, as only the Plesk host domain ought to be accessible with a cert on port 8443, but not an additional client domain. The host will return the host domain's cert if queried on port 8443.

When you access your client domain on port 443 (or https://abc.co.uk), do you still receive an SSL error?

No so I assume it works fine, can I set the place holder pages so that they show the right 8443 URL for the plesk panel, as every new site shows their own hostname:8443 to access it.

 

[Bitpalast]

What you are seeking is a frame redirect for the default page. You could try to create an inline frame for this. Your placeholder page should consist of a single inline frame, frame source https://xyz.co.uk:8443. This will leave your domain URL intact (displays in the browser's URL input line) while it displays the Plesk login page inside the frame. I have not tried that, it could be that the Plesk login page escapes a frameset. Don't know.

 

[mattd29]

What you are seeking is a frame redirect for the default page. You could try to create an inline frame for this. Your placeholder page should consist of a single inline frame, frame source https://xyz.co.uk:8443. This will leave your domain URL intact (displays in the browser's URL input line) while it displays the Plesk login page inside the frame. I have not tried that, it could be that the Plesk login page escapes a frameset. Don't know.

Thanks for your help! Since joining here I have found the forum really useful