This thread was archived. Please ask a new question if you need help.
Suddenly, *only with Firefox* all computers in the house show (Error code: ssl_error_rx_record_too_long) when trying to access any Google product.
Today, all laptops in the house (latest ver of FF) began throwing the error:
(Error code: ssl_error_rx_record_too_long)
When trying to access any Google products: gmail, Google+, analytics, Google website, etc
Make sure to reset the security.tls.version.max pref to 1 if you have previously changed this pref to 0 to disable TLS 1.0Read this answer in context 👍 6
All Replies (20)
@mnoorenberghe could you check for me if you get the error we get when accessing these ips:
They are Ips that serve www.google.ca requests in the affected region
Modified by maylard
@chapters please don't forget to change it back in the new few days. Make yourself a note
Modified by maylard
@maylard oh? change it back ?any reason why it has to be changed back? (again sorry for the stupid questions)
Modified by chapters
For security reasons.
Basically what you just did was disable a security feature that was causing problems. But obviously since it's a security feature it's not advisable to leave it off.
Modified by maylard
@maylard, those don't give this error from Mozilla's network in California (only ssl_error_bad_cert_domain because the cert is for domains, not IPs)
It may be good to let Shaw know where you found the problem lies in case they didn't find that yet.
Modified by Matt N.
@maylard ahh ic! thanks, ill make sure to turn it on, hopefully a fix will be out soon :) glad i found this thread, was freaking out and thinking it was only me affected >.<
Having same problem with dropbox.com via Shaw from Firefox
Server (126.96.36.199) sends "404 Requested URL was not found" HTML in response.
Modified by olwince
Android 4.4 is a huge update for Google. If they have started doing the updates then they will be done by regions which means redirecting traffic to their servers because they cannot handle the traffic load all at once. I am aware of this only because I own a Nexus 4 and am one of the people waiting for this to happen. It seems to be too much of a coincidence that this is happening now when the OS was announced last Thursday with the release of the Nexus 5. They said updates would be out sometime within the next couple weeks for the other Nexus devices.
Thank you guys so much! Maple Ridge, BC here and I was puzzled beyond belief with this. The workaround from Gary will work until Shaw can address this problem. Created an account just to thank you guys, you are much appreciated.
I'm on Shaw in Mission, B.C. Same problem here this morning.
Running Firefox as my main browser on iMac, Linux netbook and Windows PC. Seems to be a Firefox issue as I can connect on the Mac via Safari and IE on the PC.
Addendum: Like "olwince", same problem with Dropbox on Firefox.
Modified by oldbrownhat
I work for Shaw and am one of the people trying to track this down.
Can we get packet (wireshark) captures of examples using firefox (without the workaround) and another browser?
And more traceroutes would be fantastic as well, so that we can narrow down the affected devices!
We're also tracking this on our community site.
Modified by cdearborn
Er... possibly... but could you put that in English for the regular folks out here?
Also, this may not be relevant but I have not been able to access my usual online music streams (Classical Minnesota Public Radio and one other), except via iTunes. I normally use VLC on the Linux netbook, but trying playing the stream in a browser- either Firefox of Safari, has been unsuccessful. IE on the PC seems to work, though... Weird morning.
@cdearborn here's a traceroute for www.google.ca (from South Surrey)
Geo-Location Information for 188.8.131.52 Country United States State/Region CA City Mountain View Postal Code 94043 Latitude 37.4192 Longitude -122.0574 Area Code 650
Traceroute Tracing route to 184.108.40.206
Hop Time Host IP Location 1 0.45 10.0.0.1 10.0.0.1 , , 2 3.166 10.20.62.254 10.20.62.254 , , 3 5.453 r2-l3tca-cr2.nextweb.net 220.127.116.11 Irvine, CA, United States 4 81.105 ge-6-15.car2.Tustin1.Level3.net 18.104.22.168 , , United States 5 7.817 vl-3102-ve-133.ebr1.Tustin1.Level3.net 22.214.171.124 , , United States 6 8.179 ae-6-6.ebr1.LosAngeles1.Level3.net 126.96.36.199 , , United States 7 8.225 ae-61-61.csw1.LosAngeles1.Level3.net 188.8.131.52 , , United States 8 14.877 ae-2-70.edge1.LosAngeles9.Level3.net 184.108.40.206 , , United States 9 13.002 220.127.116.11 18.104.22.168 , , United States 10 6.873 22.214.171.124 126.96.36.199 Mountain View, CA, United States 11 7.301 188.8.131.52 184.108.40.206 Mountain View, CA, United States 12 37.548 220.127.116.11 18.104.22.168 Mountain View, CA, United States 13 46.479 22.214.171.124 126.96.36.199 Mountain View, CA, United States 14 53.273 188.8.131.52 184.108.40.206 Mountain View, CA, United States 15 86.131 220.127.116.11 18.104.22.168 Mountain View, CA, United States 16 161.371 22.214.171.124 126.96.36.199 Mountain View, CA, United States 17 161.174 188.8.131.52 184.108.40.206 Mountain View, CA, United States 18 164.326 220.127.116.11 18.104.22.168 Mountain View, CA, United States 19 162.689 22.214.171.124 126.96.36.199 Mountain View, CA, United States 20 167.836 muc03s02-in-f24.1e100.net 188.8.131.52 Mountain View, CA, United States
This has been going on since Monday Nov 5 around noon . I was on the phone to Shaw for over an hour at 6am today while they tried to resolve. They tried everything that I already tried. The tech knew nothing about the problem, btw. The only thing they managed to do was re-install firefox and lose all my remembered passwords, bookmarks etc. No happy about that.
Last words from Shaw - use explorer instead. And hopefully the problem will resolve itself. Not a solution.
Modified by VickiOBB
I have kinda the same problem with 3 PCs in the house, but google products doesn't work on every browser. My location is pretty different too, I'm from Italy.. i don't really know how to fix this.. help plx
Modified by Davidxad
I'm using shaw and live east of Maple Ridge
Are you running over a VPN at the moment? If so, can you turn that off before performing the traceroute?
My brother found that apparently firefox 12 works WITH TLSv1 enabled.
TLSv1 normal Client Hello from Firefox 12 to Google server: http://pastebin.com/b7iE7bqs
TLSv1 normal Server Hello from Google server to Firefox 12: http://pastebin.com/BSMsvK7e
As you can see the server response is properly formed. (no html nonsense) And the only real difference I can find in the Client Hello between Firefox's 12 to Firefox's 13, and up, is the bottom part. The "Extension: next_protocol_negotiation" part