core
core copied to clipboard
midori-browser
Can't open certain websites (Error writing data to TLS socket)
Trying to access https://www.google.com returns this:
Midori can't find the page you're looking for The page located at “www.google.com” cannot be found. Check the web address for misspelled words and try again. Error writing data to TLS socket: The specified session has been invalidated for some reason.
Some websites return the same error, other work fine.
gnutls-cli google.com doesn't show any errors (I don't know if it should).
I'm on Slackware64 14.2 with gnutls-3.6.5 Other browsers work without issues.
I've not encountered or heard of that error message so far... does this affect TLS-secured sites in general? I wonder if it might be to do with the CA certificates as some distros package them separately and Midori doesn't bundle them.
Just some of them. For example, It affects Google, but not Bing.
In the same time, running "gnutls-cli google.com" doesn't return any errors.
I tried to google solution for this, but failed to find any answer I could apply to my system.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, February 7, 2019 6:10 PM, Christian Dywan [email protected] wrote:
I've not encountered or heard of that error message so far... does this affect TLS-secured sites in general? I wonder if it might be to do with the CA certificates as some distros package them separately and Midori doesn't bundle them.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
I've hit this same error repeatedly with Midori running as a kiosk under Raspbian. I've been able to somewhat get around it by having curl query Google first, and then running the Midori command with the full link. The kiosk is designed to use docs.google.com with the information about what set of slides to present. I've only hit this error at work, running on their WiFi network. On my home WiFi it works without fail. So I don't know if it is some kind of timing thing, but the longer after bootup that I wait to start the Midori task the fewer TLS errors I get. The WiFi connection is up and live at the time Midori starts. I've added an internet radio task to this system that is playing an audio stream. That starts just fine about 30 seconds before I start Midori. Whether mpd runs or not, Midori hits this TLS error, but only after a boot of the system. It does not have any TLS errors when it refreshes every 30 minutes. I'd use a wired ethernet connection, but corporate IT currently has that all messed up.
Well, I'm running Midori inside an Alpine-based Docker image (accessing via VNC). Here is the console output
Any leads to the solution? I also can't access certain websites... I'm running midori on slax 9.11
Also have this error in terminal (midori:3690): CRITICAL **: session.vala:278: failed add tab to session database. Invalid type '(null)' in statement: INSERT INTO tabs (arguments...) VALUES (arguments...)
I also suffer from some https: sites that can't be found, some load without error ....
.... So I checked out https://clienttest.ssllabs.com:8443/ssltest/viewMyClient.html which suggested 'Next Protocol Negotiation' an extension to TLS (https://tools.ietf.org/id/draft-agl-tls-nextprotoneg-03.html) was NOT supported on Midori.
I cross checked on the same host Windows PC using Chrome (yes, I am running Midori under cygwin) and that browser showed 'Next Protocol Negotiation' was supported.
Hope that helps.
Midori Host: User Agent: (X11; CYGWIN_NT-6.0-6003) AppleWebKit/537.32 (KHTML, like Gecko) Midori/0.5;
Chrome Host: User Agent: (Windows NT 6.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112
( I also tried a similar SSL (including TLS) Checker but Midori could NOT reach it with the above same problem at https://browserleaks.com/ssl)
