| |
G-Force
Registered: Sep 2012
Posts: 29 |
Clock is ahead
Anybody else get this with chrome browser on csdb.
Do not get this on any other website, only csdb.
Your clock is ahead.
A private connection to csdb.dk can't be established because of your computers date and time.
Time & date are incorrect. NET::ERR_CERT_DATE_INVALID
The time & date are correct on my computer.
I have also entered chrome://flags and disabled mark non secure origins & disabled allow invalid certificates to turn off SSL warnings and still get the clock ahead warning.
My clock is also automically synchronized with the internet time server.
It does not say this on any other website, only csdb.
Having to use firefox browser which is not as good as chrome. |
|
... 1 post hidden. Click here to view all posts....
|
| |
Mixer
Registered: Apr 2008
Posts: 422 |
I think it is time to start the browser wars. Pun intended.
Ohhh, I remember the good old days of the internets when everything just worked and no one cared about standard compliance or certificates or other such nonsense, which became added just because money and children become involved with the nets. Since the invention of smart phone, just about every living thing on the planet now has access to nets and think that their view is the only correct one. Or they attempt to exploit everything else that roam the wires. Now the site compliance is defined between a few big human registry operators, who push their view of the standards and then claim that only their browser is the compliant one. Thus it must be their concept of space and time, which is superior to all. |
| |
spider-j
Registered: Oct 2004
Posts: 449 |
Quote: Anybody else get this with chrome browser on csdb.
Do not get this on any other website, only csdb.
Your clock is ahead.
A private connection to csdb.dk can't be established because of your computers date and time.
Time & date are incorrect. NET::ERR_CERT_DATE_INVALID
The time & date are correct on my computer.
I have also entered chrome://flags and disabled mark non secure origins & disabled allow invalid certificates to turn off SSL warnings and still get the clock ahead warning.
My clock is also automically synchronized with the internet time server.
It does not say this on any other website, only csdb.
Having to use firefox browser which is not as good as chrome.
Any chance your OS is maybe outdated?
I've read about some issues with Let's Encrypt certificates after 31.9.2021 with people:
- running a Windows XP prior to SP2.
- running a Windows XP SP3, 7 or similiar with having disabled automatic root certificate update.
https://letsencrypt.org/docs/certificate-compatibility/
Afaik Firefox does not rely on the OS certificates, which would explain why the problem only occurs in chrome. |
| |
G-Force
Registered: Sep 2012
Posts: 29 |
Quote: Any chance your OS is maybe outdated?
I've read about some issues with Let's Encrypt certificates after 31.9.2021 with people:
- running a Windows XP prior to SP2.
- running a Windows XP SP3, 7 or similiar with having disabled automatic root certificate update.
https://letsencrypt.org/docs/certificate-compatibility/
Afaik Firefox does not rely on the OS certificates, which would explain why the problem only occurs in chrome.
I suspected it might be because i am still on win xp spider-j , but all other wesbites are ok.
That's whats strange, only happens on csdb.
Not had any problems on any other website so far. |
| |
spider-j
Registered: Oct 2004
Posts: 449 |
This will only effect sites that use Let's Encrypt certificates.
And: I don't completely understand all this encryption stuff, but it also seems to depend on the server configuration (?). When checking csdb.dk I get more incompatibilities[*] than when I check i.e. my private coder notes blog (which also uses Let's Encrypt):
https://shice.jesus-rocks.com/
You can test if that page works without errors. If yes: maybe there's something Perff can do on the server side to improve "legacy OS" support. If not: who knows ... (?) :-P
[*] but Chrome on XP is *not* listed as a problem, only older IEs on Win XP, Win 7... |
| |
hedning
Registered: Mar 2009
Posts: 4618 |
I wouldn't even go online on a XP machine. But hey. :D |
| |
Burglar
Registered: Dec 2004
Posts: 1051 |
there was a big letsencrypt outage, they forgot to renew their root certs.
https://scotthelme.co.uk/lets-encrypt-old-root-expiration/
so yea, that must've been the issue |
| |
chatGPZ
Registered: Dec 2001
Posts: 11149 |
Quote:I remember the good old days of the internets when everything just worked
was that before or after vt100? |
| |
G-Force
Registered: Sep 2012
Posts: 29 |
Quote: This will only effect sites that use Let's Encrypt certificates.
And: I don't completely understand all this encryption stuff, but it also seems to depend on the server configuration (?). When checking csdb.dk I get more incompatibilities[*] than when I check i.e. my private coder notes blog (which also uses Let's Encrypt):
https://shice.jesus-rocks.com/
You can test if that page works without errors. If yes: maybe there's something Perff can do on the server side to improve "legacy OS" support. If not: who knows ... (?) :-P
[*] but Chrome on XP is *not* listed as a problem, only older IEs on Win XP, Win 7...
Yep spider-j same problem when i goto https://shice.jesus-rocks.com/ |
| |
spider-j
Registered: Oct 2004
Posts: 449 |
Quote: Yep spider-j same problem when i goto https://shice.jesus-rocks.com/
Then I don't think CSDB / Perff can do much about it. I guess using Firefox for webpages that use Let's Encrypt certs is the best way to work around the issue on your end.
At least if there isn't another way I don't know yet. |
| |
G-Force
Registered: Sep 2012
Posts: 29 |
Ok thanks spider-j & all for your input.(:-) |
| Previous - 1 | 2 - Next |
