Let's Encrypt error

*dan* · 09-29-2021, 04:13 PM

Getting variations of this error on all our websites today in Chrome/Safari on all our computers.

NET::ERR_CERT_DATE_INVALID
This server could not prove that it is www.valleyobgyn.md; its security certificate is not valid at this time. This may be caused by a misconfiguration or an attacker intercepting your connection.

Sometimes the error says our clocks are set wrong, which there are not.

Even getting it for FutureQuest. I tried sending this through the service desk, but it won't let me.

I reset the SSL Cert for the website above, still getting the same message. Is this something of the server side, or on our side?

Thanks
Daniel

*Wrightwood* · 09-29-2021, 05:09 PM

I'm also getting security certificate errors

**Kevin** · 09-29-2021, 07:53 PM

Sorry, I didn't notice a thread had already started on this. I made a post here: https://futurequest.net/forums/showthread.php?t=27722 describing what went wrong.

*dan* · 09-30-2021, 01:46 PM

Still not working for me in Chrome or Safari on Mac. (I read the announcement) Emptied caches and refreshed but still no go. Getting the error NET::ERR_CERT_AUTHORITY_INVALID in Chrome.

aztecmedia.com
aztecmuseum.com
valleyobgyn.md
pisapain.com

Just a few of our sites. Getting the error for all our FutureQuest sites.

*Wrightwood* · 09-30-2021, 08:49 PM

People using Chrome still have issues connecting to my FutureQuest sites

*Wrightwood* · 10-01-2021, 12:54 PM

Any updates Kevin?

Quote:

Originally Posted by Wrightwood

People using Chrome still have issues connecting to my FutureQuest sites

**Kevin** · 10-01-2021, 01:51 PM

Is this only on Macs? It works fine for us but none of us has a Mac. The two of you are the only complaints we have currently. Is there any error info you can provide?

*Wrightwood* · 10-01-2021, 07:45 PM

The users said it's with Chrome on a tablet & Android phone

**Kevin** · 10-01-2021, 08:28 PM

Can you check and see if this is still a problem? There is info in the notice about Android OS older than 8.0.0 work differently. I have an old phone with 5.1.1 on it and I confirmed yesterday that it couldn't handle the current setup. I didn't think there was anything we could do to fix it so I just hoped that 8 was old enough to not bother many people. However, I just booted that old phone back up and it works fine now (once I removed the h from your domain). Nothing was changed on our end and this phone was off (the battery in it doesn't even work) so I can only guess that there was a glitch in the special exception for old Android stuff.

*dan* · 10-04-2021, 04:06 PM

I'm still getting errors in Chrome and Safari on Mac. I did check on a Windows machine this weekend and I am not getting any errors. I have attached an image of the errors I'm receiving from both.

https://aztecmedia.com/SSL-Error-Chrome.png

https://aztecmedia.com/SSL-Error-Safari.png