Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
Could you explain more what you mean by "not fully secure in google chrome"? Is there a message on a browser? What version of chrome and on what system (android, iOS, ...).
As background, on Sept 30 a Lets Encrypt root certificate expired and has caused various issues. Your server is sending a proper Lets Encrypt "short chain" as is common with IIS now. Earlier, your server would have sent the "long chain" for best compatibility with older android systems. Below are a couple links with details. We will need more info about your specific problem to assist more. Thanks
thanks so much for your reply, please look at the ssllabs report where you can see that there is an issue with TLS support and thats why we dont get an A grade
Oh, I guess you are concerned with this line then? Not sure what this has to do with chrome but ...
This server supports TLS 1.0 and TLS 1.1. Grade capped to B. MORE INFO »
Just follow that link for MORE INFO (also shown below) and it explains you should remove support for older TLS versions from your server config. I do not know how to do that for IIS but maybe someone else will assist if you do not know how.
OK, well, this is a forum to help with Lets Encrypt certificates. Questions about configuring your server for TLS with Plesk is best addressed to your hosting company GoDaddy.
It has nothing to do with the certificate. I realize GoDaddy / Plesk may have it setup so they are configured at the same time but the certificate is not involved in the TLS versions used by your server. Maybe try a forum with GoDaddy experts using IIS to see what they have done. Or, try to see what is different about your other GoDaddy setups and apply that here.
I would like to concur with my fellow volunteer @MikeMcQ: TLS certificates can be used by any TLS protocol, be it the older SSLv3, TLSv1.0, TLSv1.1 or TLSv1.2 and newer. The certificate has no influence over the TLS protocol version used! This is a webserver configuration issue.
Also, I'm not sure how the grade B cap due to enabled older TLS protocol versions relates to the site not working in Chrome: I don't see the relationship to be honest, so perhaps you can clarify what the main goal is here: Chrome support or SSLLabs grade support?
It's your server, you can make it do whatever you want it to.
You just have to ask the right question (in the right place).
So far you haven't asked the right question nor have they been in the right place.
That said, @griffin has gone above and beyond to read through the lines and provide you with the right answer to a question you haven't yet asked.
Which is what? Then "What is the right question?"
Well, it's not a Plesk related question nor setting, it is a Windows OS question/setting.
To which the answer should be: You can Enable/Disable TLS protocols within Win2019.
[which can be easily done by using the Nartac product IISCrypto - link provided above]