Chrome reporting site certificate as invalid

[TrimixToo]

Right, so fix it!

Sure, I'll get right on that. Right after they hire me. If they can afford me. ;-)

@The Chairman , any update from your hosting company?

 

[diversteve]

I don't think it's our hosting company since it's AWS (Amazon Web Services)

afaik we're in process on getting a new C..A.

til then Firefox is still working for me. Or I guess Edge....

When there's an update the Chairman will post it here.

 

[The Chairman]

I will.

 

[Seaweed Doc]

Seems to be working for me mostly now. (A little glitchy on my phone, but that might just need a reboot on my end. Fine on a desktop where I don't think it worked earlier today.)

Edit: Apparently my phone is more than a little glitchy.

 

[rhwestfall]

When it hits this pc, and my phone, I'll see you again someday.....

 

[Insta-Gator]

My phone works if I access SB in unsecured mode.

 

[MaxBottomtime]

Google Online Security Blog: Distrust of the Symantec PKI: Immediate action needed by site operators

 

[stuartv]

This problem was reported on Oct 28th.

Some statement on the status of "things" would be nice. @Sean Walberg's post (#10) seems like it might offer a way to get a working cert pretty quickly...

BTDT on server certs. I know it's a PITA. Good luck with it!

 

[Sean Walberg]

Figured I'd throw a link to Amazon's docs for setting up a Let's Encrypt cert on Amazon Linux and Apache: Tutorial: Configure Apache Web Server on Amazon Linux 2 to Use SSL/TLS - Amazon Elastic Compute Cloud

You already have TLS set up so you can skip to the Certbot step. It does look like you have an http -> https redirect so you'll want to make sure the /.well-known path doesn't get redirected and can be served over HTTP. The docroot can be any directory as long as it's writable.

 

[GreggS]

What's odd is that I started getting the message today with Chrome on one of my desktops, but still works in Chrome on the desktop I'm on now as well as on my Android phone. Still works in Firefox on both.