Resolved Domain name issue -- certificate for a domain uses server domain. But can't see how or why

[MHC_1]

Server operating system version

Ubuntu 22

Plesk version and microupdate number

Obsidian v18.0.61

We have multiple domains on the server.

One domain works fine and has the certificate set up and the domain loads correctly with the correct certificate for the correct URL.

Another domain says the certificate is invalid because somehow the certificate is loaded for the Plesk Server domain rather than the website domain.

The "SSL It!" / Lets Encrypt are both set up the same so from the Plesk interface I can't see why it's different and can;t see how to resolve this.

Pictures below:

ERRORS on browser (2





Certificate set up on Plesk:



Another website on the same server using the same certification system (SSL it!):





Why is this different? How can we fix this so all domains on the server work like the DESG?

The cause may be related to this bug? --> Resolved - SSL It - HSTS appearing twice in headers ? Any help appreciated.

BONUS QUESTION:

Also, bonus question; How can we manually set the HSTS on a domain to zero to force the HSTS refresh (eg "Strict-Transport-Security: max-age=0") ? Plesk doesn't give this option and can't find the relevant lines in .htaccess or in any of the httpd.conf.

 

[Kaspar@Plesk]

Hi, is the right certificate selected in the hosting settings of the domain?

As for setting HSTS max age, you can click the slides icon to configure this (although the minimum available option is 1 minute).

 

[MHC_1]

Hi, is the right certificate selected in the hosting settings of the domain?
View attachment 26577
As for setting HSTS max age, you can click the slides icon to configure this (although the minimum available option is 1 minute).

Hello
Yes the correct certificate is set here (NB: This is Hosting & DNS --> Hosting Settings ) for all domains.

re: HSTS yes, but this isn't really configurable more that it gives a few (3) basic options, not involving setting age=0. But I've found the issue with HSTS was it was being set twice by WP.

 

[MHC_1]

(original post deleted as incorrect).

Issue remains.

 

[Kaspar@Plesk]

If you are positive the right certificate has been selected in the hosting settings, you can run the repair utility via command line to see if that fixes the issue.

plesk repair web example.com -sslcerts -y
(replace example.com with your domain)

 

[MHC_1]

If you are positive the right certificate has been selected in the hosting settings, you can run the repair utility via command line to see if that fixes the issue.

plesk repair web example.com -sslcerts -y
(replace example.com with your domain)

Thanks. This ha been done.



Should I await any sort of propagation?

Clearing web history and cache on browsers results in no change at the browser end. Same issue remains.

 

[Kaspar@Plesk]

Should I await any sort of propagation?

Any repairs should be instant, although a browser restart might be needed to clear cache.

Since the repair utility did not found any errors I am not sure what is causing the issue. I recommend opening a ticket with our support team and let them investigate the issue on your server. To sign-in to support and open a ticket go to https://support.plesk.com.

If you got your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative to get support directly from Plesk: https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk

 

[MHC_1]

Further to the above,
Today we have this issue when trying to reissue a certificate on the same server:

Could not obtain directory: cURL error 35: error:0A000126:SSL routines::unexpected eof while reading (see libcurl - Error Codes) for https://acme-v02.api.letsencrypt.org/directory

While using SSL It!

 

[Kaspar@Plesk]

There currently seems to be an issue with (re)issuing certificates. We are investigating this issue. More info:

Issue - SSL create and renew errors on random domains / possibly a Let's Encrypt issue, but maybe only in combination with Plesk

We are seeing some random create and renewal errors of Let's Encrypt as described in https://community.letsencrypt.org/t/failed-reissue-on-plesk-due-to-could-not-obtain-directory-curl-error-35-encountered-end-of-file/221455/3 This only occurs on some domain names while other domains on the...

talk.plesk.com

 

[MHC_1]

Reissuing the certificate again after the Let's Encrypt issue cleared seems to have resolved this issue. Thanks.