Resolved Certificate issue

[Sahi]

Server operating system version

CentOS 7.9.2009

Plesk version and microupdate number

18.0.43

Hello,

I'm pretty new with Plesk and just running the webserver for hobby.

I have got a few domains running. All the domains have got valid certificates with let's encrypt, but only the first one registered with the IP adres get me a Completely save closed lock in the browser.
With some use of google i got to this: How to secure many domains at once with Let’s Encrypt certificates in Plesk? - Support Cases from Plesk Knowledge Base

But i can not find the Hosting plans in bij Plesk Dashboard.

 

[Kaspar]

Can you explain how you've setup your domains? Are the domains that do not show the "lock" in your browser aliases of the other domain? Or all domains separate websites?

 

[Sahi]

Hello Rasp,

Most of the domains are main domains.

 

[Kaspar]

That's good to know. What happens if you try to re-issue the Let's Encrypt certificates manually? Are there any errors?

 

[Sahi]

There are no errors.

When i click the Reissue button i can choose a certificate. At the bottom i click"Install a free basic certificate provided by Let's Encrypt
Usually when i renew i change the DNS record (_acme-challenge) where my domains are issued. (Didn't bother for this, think i should fix this by running a internal DNS)

I think the problem is having multiple domains on 1 IP. I have to issue one certificate for all domains at once. But do not know how.

 

[Bitpalast]

"Completely save closed lock in the browser." + "There are no errors. ... When i click the Reissue button"
= There is no issue with the certificate but with the website content. Probably some resources are addressed by http and not https links. For such pages, the browser will display a certificate warning that the site is not secure. But this is not caused by the certificate but by the http resources, e.g. css, js, images (internal or external sources alike). You can check this on Why No Padlock?

 

[Sahi]

Hello Peter,

This is the result


So everything seems fine!

 

[Bitpalast]

So the bottom line is that you have issued a certificate for the domain, the "WhyNoPadlock" test passes, yet the browser still displays a broken lock? Can you click on the lock and view details why the browser thinks that SSL is broken on the domain?

 

[Sahi]

Okay,
So this just happened:
Ik was changing my language to make a pritscreen.
In Chrome i had a sign it had to be updated.
So after changing language i updated chrome. And after that my padlock was closed!

Issue solved. (But strange)