Does anyone on /g/ know how to fix this recently maybe the past

Did you install any new software just before the problem started?

Fix your date and time
>>>/g/sqt

>>58612658
No that's the weird thing

>>58612666
My date and time is fine

>>58612639
It's because you updated chrome.

Look up there error

>>58612666
nah it ain't a time problem, that's certificate transparency.

Basically because CAs are a big racket and vulnerable to governments applying legal pressure to them to issue bogus certs, browser makers and the security community thought it'd be nice if they published a record of every cert issued, in an authenticated, cryptographically-difficult-to-forge way. Then anyone could look at the record and verify that nothing fishy was going on. CAs, of course, didn't want to do this, they want to keep getting paid lots of money for doing almost nothing. So the browser people said okay, do it or we'll disallow TLS connections using your certs. Chrome, in particular, has a lot of leverage, since it has the biggest userbase, and they're on board with this. The idea is that it creates a powerful incentive for sites to get their certs only from CAs doing cert transparency, because if they don't they'll lose a lot of traffic in a hurry.

g2a, twith, and their CAs apparently didn't get the memo in time.

Modern browsers, having learned the hard way that users will click a big red "DANGEROUS OVERRIDE" button if it lets them access their site, generally no longer let the user instruct them to continue anyway in the face of TLS errors. Go tweet at g2a and twitch or something to get their shit together.