Unable to access a particular site since Yesterday ...
-
rseiler last edited by
Opera employee Håvard said (in the above blog post, comments section) that "If you manually change the tls settings through opera:config, the Opera 12.17 update system will leave them alone," so that should be one way to stop it. I haven't tested that way.
Blocking autoupdate.opera.com in hosts or firewall also prevents updating.
Original configuration (no problem):
SSL 3: ON
TLS 1: ON
TLS 1.1: OFF
TLS 1.2: OFFAutomatically changed configuration (crashes for some):
SSL 3: OFF
TLS 1: ON
TLS 1.1: ON
TLS 1.2: ONWorking alternative here:
SSL 3: OFF
TLS 1: ON
TLS 1.1: OFF
TLS 1.2: OFFEnabling of the higher TLS's (one or both) seems to be the issue.
-
A Former User last edited by
I would agree, I've been working all day with just TLS 1 checked, and had no crashes at all.
-
A Former User last edited by admin
An off-topic aside, but I've been having problems, as have others, using the latest Java versions with 12.17.
https://forums.opera.com/topic/5889/java-not-working-after-new-java-install-8-25
I happened to notice when I was checking its settings that Java 7 Update 67 (the last one that seems to work with 12.17) has SSL 3.0 enabled in its default security settings, and TLS 1.0 enabled and TLS 1.1 and 1.2 disabled.
-
highstream last edited by
Looking good so far. Wish I'd heard about this earlier, as I've tried lots of uninstalls and sys restores the past few days trying to find the culprit. Thanks,
-
rseiler last edited by
I've tried the other TLS combinations now, and at least here, if SSL3 is disabled then the only TLS you can use with stability is TLS1.
-
A Former User last edited by
I've been using it today with SSL 3 disabled, and TLS 1.0, 1.1, and 1.2 all enabled, and haven't had any crashes so far (touch wood!)
-
A Former User last edited by
Spoke too soon, just crashed!
;_;
Now switched TLS 1.1 and 1.2 off again.
-
kanstisama last edited by
You guys rock! Thanks for all this info. I thought I loose all my hair because of not being able to log to some sites and this random crashing!!! Argh!!!... Really annoying week!!! I will also stay on TLS 1.0 for now.
-
redfox-cz last edited by
The only working solution is to block access to address "autoupdate.opera.com" in your firewall (or add it to the Hosts file if you don't have a FW).
I don't know why Opera team is still disabling TLS 1.1 and 1.2 remotely on all clients, if it is more secure than TLS 1.0. Some web sites require the later TLS versions and don't work with 1.0. -
blackbird71 last edited by adminThe only working solution is to block access to address "autoupdate.opera.com" in your firewall (or add it to the Hosts file if you don't have a FW). I don't know why Opera team is still disabling TLS 1.1 and 1.2 remotely on all clients...
Have you tried the opera:config method noted above in <https://forums.opera.com/post/55410 >? Regardless, some time ago, I also blocked Opera's autoupdater (via renaming the updater file) just to be sure my own settings aren't perturbed any more. As to why Opera continues disabling TLS 1.1 and 1.2, I believe there's a definite though not universal stability problem for some users and sites if those settings are turned on with SSL3 turned off (see: <https://forums.opera.com/post/55555 > plus a myriad of past posts in various forums). I think Opera has set their update server to auto-respond to every Presto Opera startup "ping" with their SSL-TLS fix instructions. In the past, they've auto-delivered JavaScript updates and other things at that startup point, so it's not unprecedented.
