This thread was archived. Please ask a new question if you need help.
Firefox 67.0 (64-bit) Linux: tls handshake fail
As of this morning, I am unable to access many of the sites I visit regularly and am now unable to conduct aspects of my business. The error is always that the connection timed out, the website isn't available and the tls handshake simply stops.
I can't even reach https://input.mozilla.org/en-US/feedback/firefox/67.0/ because of this handshake. That's kind of ridiculous, isn't it?
The issue doesn't affect all websites, but unfortunately it's the ones I need. I've created a new profile, refreshed Firefox, reset my modem and router. My ISP says the connection is fine on their end.
Firefox is the only browser I have access to on my desktop. Google Chrome, which I don't want to use, works fine on my Android phone.
Further research, including installing Chrome for Android, revealed the tls handshake problem was not limited to Firefox. Charter finally admitted that the problem was on their end and fixed it later today. No one could tell me what caused the problem, but for now everything is working. Thanks for the reply.Read this answer in context 👍 0
All Replies (6)
There is security software like Avast, Kaspersky, BitDefender and ESET that intercept secure connection certificates and send their own.
Further research, including installing Chrome for Android, revealed the tls handshake problem was not limited to Firefox. Charter finally admitted that the problem was on their end and fixed it later today. No one could tell me what caused the problem, but for now everything is working. Thanks for the reply.
That was very good work. Well done. Please flag your last post as Solved Problem so others will know.
Thank you, FredMcD. Although my problem didn't involve antivirus or any of the other most common issues, it was a good lesson for me to keep going and to push when needed. Now, stupid question: how do I mark this topic solved?
I imagine there could be several reasons for this so I don't think there's a single correct answer, just what worked for somebody else.
In my case my internet connection is a wifi hotspot from an Android phone. Because the phone runs on its internal battery even through power outages it hadn't been rebooted in months. Rebooting it solved the problem for 2 computers and another phone working through its wifi.
But the problem happened just as I had done a build of a Firefox nightly, for which I'd had to update something involving TLS from the standard Debian deb version so I was suspicious of that. Everything's working fine after the phone reboot, including my new nightly.
Just guessing, maybe the new TLS version was one the phone had never seen before. The symptoms were about identical to the OP's. Facebook and some other sites wouldn't be able to do a TLS handshake, while others would. And it was the same sites on all the wifi client machines. My Nightly is 70.0a1 aarch64. It was probably nodejs I was thinking of, but how updating something on one wifi client machine could affect 2 other clients and the router I don't know. Maybe it was coincidence.
Modified by ab1jx