I don't know what's happening, since yesterday I was, and still am unable to access all Faithlife websites.
"Your connection is not private"
NET::ERR_DSTE_INVALID
I am using Trend Micro antivirus programme.
Thanks.
Leo Wee Fah
Does it work now, as it hints it may be temporary? From what region of the world are you accessing logos.com?
Can you access logos.com from another browser, like Firefox,Safari or Edge?
No, I still cannot access all Faithlife websites from from my laptop running windows 8.1 with Trend Micro. I have tried putting those links into the exception list of Trend Micro, or even disable Trend Micro, still the same result.
I have also tried Internet Explorer, it gave the same problem as well.
My guess is that it's related to this outage we posted recently: https://status.faithlife.com/incidents/vksrxjfl65tg
my laptop running windows 8.1
Since Windows 8.1 has been EOL for 3.5 years, I suspect it doesn't have the new root certificates required for Faithlife's TLS certificates to be trusted.
As per this post https://scotthelme.co.uk/lets-encrypt-to-transition-to-isrg-root/ you can use https://valid-isrgrootx1.letsencrypt.org/ to test whether your device trusts the new ISRG Root X1 certificate. If it doesn't, you may be able to download and install it manually. However, in my personal opinion, you should not be connecting an unpatched Windows 8.1 machine to the Internet at all; it's likely vulnerable to most of the Windows 10 kernel vulnerabilities that have been discovered in the last 4 years (because the kernels are highly similar) and attackers can easily reverse engineer a Microsoft security update for Windows 10 to fashion an exploit for Windows 8.1.
Thanks... I will try to get new drive with windows 10.
Leo Wee Fah.
There are also lots of recomendations to not use Chrome anymore.
Just as a note, I've reported this before but I get the exact same error message on Windows 11 with Edge. Not sure if other users on 11 are seeing this as well.
This one? https://community.logos.com/forums/t/201893.aspx
That's a different issue.
