again SSL is messing up and im getting OCSP errors accessing the site in opera.... pls to fix?

Are you using Opera Classic in your phone? Because I use Opera 12.15 on my laptop and e6 just loads fine, but not in my phone

opera 12.16 on linux... if i hit the refresh button a -lot- of times or use opera turbo the site sorta works... ...this is the 3rd time this has happened.. this glitch seems to come in waves... the background and stylesheet stop loading then either static1.e621.net goes or the main site goes...

ps.. is there a way to access the site without https? or is it mandatory?

blarg... lol.. and just as soon as i make mention of this error on the forum it gets fixed within a few minutes... even if i let it go for a day with the error.... someone is watching.... or its a glitch that just happens...

and now its broke again.... plz to fix... lol...

There's something screwy with OCSP checking in Opera 12. To fix it, go to opera:config, search for OCSP at the top, then uncheck "OCSP validate certificates". It's not really all that necessary anyway; Chrome's had it disabled by default since 2012, for example.

setting that causes opera to use unusual amounts of cpu time to make a connection and often it fails.. epiphany cant connect at all citing a tls failure... firefox and im guessing chrome seem to be the only that work...

OCSP errors happen to me as well (Version 12.17, Build 1863). But only for certain sites

tony311 said:
There's something screwy with OCSP checking in Opera 12. To fix it, go to opera:config, search for OCSP at the top, then uncheck "OCSP validate certificates". It's not really all that necessary anyway; Chrome's had it disabled by default since 2012, for example.

That sounds very unsafe

titanmelon said:
OCSP errors happen to me as well (Version 12.17, Build 1863). But only for certain sites

That sounds very unsafe

From what I've gathered OCSP isn't very reliable or safe to begin with and caused more problems than it solved. IIRC a lot of browsers just ignore it if it doesn't validate anyways, making it even less practical for verification.

Disclaimer: I'm not a security expert; tony might be able to explain it better than I can.