Error 126(net::ERR_SSL_BAD_RECORD_MAC_ALERT) while accessing website.
Reported by email@example.com, Sep 13 2012
The below data is provided based on user reports in 'GoogleFeedback'. We did not reproduce the issue. 100+ users have reported this issue in 'GoogleFeeback' since 09/07 Chrome Version : 21.0.1180.89 (M21 Stable) URLs (if applicable) : NA Other browsers tested:NA What steps will reproduce the problem? 1.Navigate to google site or any random site What is the expected result? Page should be loaded What happens instead? Users get "Error 126(net::ERR_SSL_BAD_RECORD_MAC_ALERT)" while accessing website. Additional Information: 48% of the reports are from locale RU and having Win 7 operating system. 59% of the reports have reported this issue with google related sites. NOTE: We are unable to reproduce the issue (with locale as EN) in Chrome:"22.0.1229.39 beta" version on Ubuntu OS For more details, refer the user reports below: http://goto.google.com/401746549 http://goto.google.com/401680437 http://goto.google.com/401596597 http://goto.google.com/401445093 For further more user reports, refer the below cluster URL http://goto.google.com/1845754
Sep 14 2012,
https://chromiumcodereview.appspot.com/10918099 the issues started after this patch by the hour. I´ll post more of my research soon. I´ve had alot of users around the Sweden (Local as SE) area that have this, reports are droping in all the time.
Sep 14 2012,
It´s most likely to be a error related to SSLV3. I have a full report with info that change during research: https://docs.google.com/document/d/1_-0mG-_Od5Q1E6Nq6hc_Jx8FPEcjCVMr7qJ2mH8bEmM/edit quick report: ---------------- Solutions: Step 1: Delete cache and other browser data Step 2: Change DNS to google´s 184.108.40.206 The above 2 steps only work for a day or so then the errors comes back. Workaround 2: Change your modem/router OR upgrade its firmware. It seems that routers/modems from many manufacturers have this problem, at least: TP-Link, D-Link, Buffalo, ZTE and Telewell. Workaround 2: You can try to change the MTU value from your router/modem to 1400 Both OSX users and Windows 7 users have reported error and from areas around the world: Preston, United Kingdom PR11RY Richmond, Virginia, United States 22109 Reykjavik, Iceland Vienna, Austria tests can be made with "firefox": * Open "about:config" in your browser * type "ssl" into the filter box * Double click on the following to set them to true (enable them): security.enable_ssl2 security.ssl2.rc2_128 security.ssl2.rc2_40 security.ssl2.rc4_128 security.ssl2.rc4_40 * Double click on the following to set it to false (not enabled) security.enable_ssl3 * You may need to close the browser and restart it to ensure these settings take effect. Reversing the above setting will restore the browser back to defaults
Sep 20 2012,
"SSL_ERROR_BAD_MAC_ALERT" is described as "SSL peer reports incorrect Message Authentication Code." This could happen due to various reasons. One of the common reasons is clock being out of sync. Use a tool like http://browserinformation.appspot.com to check if the system time on the affected device is correctly set.
Sep 20 2012,
Updated document with timesync fixes, going to test it during this day.
Mar 10 2013,
May 4 2013,
I am getting this error with Chrome OS 28 on one site too. The Server in question is needs ssl3 for various reasons. when i force Chromium on Ubuntu too use SSL3 it works. It also worked fine with Chrome OS 27. btw the server is only avaiable for two /21 networks
May 4 2013,
Jul 16 2013,
I just reset my Kaspersky settings and it worked.
Jul 30 2013,
Please fix this issue ASAP. Effects one of my favorite sites!!
Aug 13 2013,
I suspect recent reports of this issue was due to crbug/260358 which recently got fixed (but not available on stable yet)
Aug 15 2013,
thanks #8 shantanu...@gmail.com, i suffered from this error a long time, your comment is helpful. Thanks a lot.
Apr 11 2014,
Not able to reproduce the issue on latest stable 34.0.1847.116. @arsids: Could you please verify and confirm and update the behavior. Thanks in Advance.
Jul 8 2014,
Closing the issue due to lack of user response. Please feel free to file a new one if you encounter again.
Sign in to add a comment