Not Secure Warning Started Today

Help
1

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.

My domain is: www.primarywebsitedesign.com

I ran this command: I ran the debugger and the Google transparency and they are both valid.

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

2 Likes
2

Hi @AaronHill, and welcome to the LE community forum :slight_smile:

Can you provide a screenshot of the message (that also contains the URL)?

2 Likes
3

lets-encrypt
lets-encrypt676Ă—633 44.2 KB

Thank you, sir! I haven't needed help before, so this is confusing to me. Thank you for the welcome.

This just started today. I recently did a redesign, if that helps, but didn't change any of the code, only cosmetic. I did change the name of the home page to landing, but that shouldn't affect the ssl, or at least I wouldn't think it would. The website is built on Wordpress, and I have deactivated all the plugins and cleared my cache and restarted my browser, but still get the same error message.

3 Likes
4

As an aside, the backend is still showing secure.
lets-encrypt-1

2 Likes
5

I can't put my finger on it (yet)...
But it seems to be related to some soft-failures. Like:

<div style="background-image:url(http://primarywebsitedesign.com/wp-content/uploads/2019/07/sarah-profile.jpg)" class="et_pb_testimonial_portrait"></div>
<div style="background-image:url(http://primarywebsitedesign.com/wp-content/uploads/2019/07/jeff-profile.jpg)" class="et_pb_testimonial_portrait"></div>
<div style="background-image:url(http://primarywebsitedesign.com/wp-content/uploads/2019/07/melissa-profile.jpg)" class="et_pb_testimonial_portrait"></div>
<div style="background-image:url(http://primarywebsitedesign.com/wp-content/uploads/2019/07/sarah-profile.jpg)" class="et_pb_testimonial_portrait"></div>
<div style="background-image:url(http://primarywebsitedesign.com/wp-content/uploads/2019/07/jeff-profile.jpg)" class="et_pb_testimonial_portrait"></div>
<div style="background-image:url(http://primarywebsitedesign.com/wp-content/uploads/2019/07/melissa-profile.jpg)" class="et_pb_testimonial_portrait"></div>
<source type="video/mp4" src="http://primarywebsitedesign.com/wp-content/uploads/2021/08/pexels-rodnae-productions-7308093.mp4" />

See: Test Results: primarywebsitedesign.com - Why No Padlock?

The certificate is fine: SSL Server Test: primarywebsitedesign.com (Powered by Qualys SSL Labs)

2 Likes
6

Ok, fixed it. Thanks so much for your enormous help!

This was the solution. The internal name of the site was not set to HTTPS, so when uploading images they were saved under the internal site identity. A quick fix in the settings changed that!

4 Likes
7

That's another reason why I don't have my words pressed!
Cheers from Miami :beers:

#FreeCuba

4 Likes
8

Welcome to the Let's Encrypt Community, Aaron :slightly_smiling_face:

For posterity...

3 Likes
9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.