I installed the SSL certificate on my website via plesk, and now the website with HTTPS appears so so bugged 
https://postleet.com/
Hi @unaisanchez
there are some errors - https://check-your-website.server-daten.de/?q=postleet.com
Your certificate has only one domain name
CN=postleet.com
08.05.2019
06.08.2019
expires in 90 days postleet.com - 1 entry
so your www version isn't secure.
You have created too much certificates with both domain names:
| Issuer | not before | not after | Domain names | LE-Duplicate | next LE |
|---|---|---|---|---|---|
| CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-05-08 08:43:59 | 2019-08-06 08:43:59 | postleet.com | ||
| 1 entries | duplicate nr. 3 | ||||
| CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-05-08 08:41:04 | 2019-08-06 08:41:04 | postleet.com | ||
| 1 entries | duplicate nr. 2 | ||||
| CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-05-08 08:37:39 | 2019-08-06 08:37:39 | postleet.com | ||
| 1 entries | duplicate nr. 1 | ||||
| CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-05-05 16:26:04 | 2019-08-03 16:26:04 | postleet.com, www.postleet.com | ||
| 2 entries | duplicate nr. 5 | next Letsencrypt certificate: 2019-05-10 19:50:56 | |||
| CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-05-05 16:06:42 | 2019-08-03 16:06:42 | postleet.com, www.postleet.com | ||
| 2 entries | duplicate nr. 4 | ||||
| CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-05-05 15:37:46 | 2019-08-03 15:37:46 | postleet.com, www.postleet.com | ||
| 2 entries | duplicate nr. 3 | ||||
| CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-05-05 14:22:06 | 2019-08-03 14:22:06 | postleet.com, www.postleet.com | ||
| 2 entries | duplicate nr. 2 | ||||
| CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-05-03 19:50:56 | 2019-08-01 19:50:56 | postleet.com, www.postleet.com | ||
| 2 entries | duplicate nr. 1 |
Next 2019-05-10.
And you have a redirect https -> http, that's bad.
| Domainname | Http-Status | redirect | Sec. | G |
|---|---|---|---|---|
| • http://www.postleet.com/ | ||||
| 82.223.2.121 | 302 | http://postleet.com | 0.123 | D |
| • http://postleet.com | 200 | 0.233 | H | |
| • http://postleet.com/ | ||||
| 82.223.2.121 | 200 | 0.240 | H | |
| • https://postleet.com/ | ||||
| 82.223.2.121 | 302 | http://postleet.com | 0.810 | F |
| • https://www.postleet.com/ | ||||
| 82.223.2.121 | 302 | http://postleet.com | 0.544 | N |
| Certificate error: RemoteCertificateNameMismatch |
Where are these correct certificates? Use one of these, then your www version is secure.
And remove the redirect https -> http.
The reason that the site appears “bugged” is mixed content blocking. Browsers now refuse to load some HTTP resources inside an HTTPS site. But the HTML source of this page has HTTP resources that will be blocked when the site is loaded over HTTPS, like
<link rel="stylesheet" href="http://postleet.com/themes/wowonder/stylesheet/welcome.css">
<link rel="stylesheet" href="http://postleet.com/themes/wowonder/stylesheet/font-awesome-4.7.0/css/font-awesome.min.css">
These (and everything else that says http:// within the page) should be changed to https:// or simply // (which uses the same scheme that the current page was loaded with).
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.