New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 6 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2014
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug

Sign in to add a comment

Error 126(net::ERR_SSL_BAD_RECORD_MAC_ALERT) while accessing website.

Reported by, Sep 13 2012 Back to list

Issue description

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.

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:

For further more user reports, refer the below cluster URL

Comment 1 by, Sep 14 2012 
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.

Comment 2 by, 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:

quick report:
Step 1:
Delete cache and other browser data

Step 2:
Change DNS to google´s

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):
    * Double click on the following to set it to false (not enabled)

    * 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

Comment 3 by, Sep 20 2012

Labels: -Pri-2 Pri-3 Hotlist-Enterprise
"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 to check if the system time on the affected device is correctly set.

Comment 4 by, Sep 20 2012

Updated document with timesync fixes, going to test it during this day.
Project Member

Comment 5 by, Mar 10 2013

Labels: -Area-Internals Cr-Internals
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

Comment 7 by, May 4 2013

Labels: -Build

Comment 8 by Deleted ...@, Jul 16 2013

I just reset my Kaspersky settings and it worked.

Comment 9 by Deleted ...@, Jul 30 2013

Please fix this issue ASAP.  Effects one of my favorite sites!!

Comment 10 by, 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)

Comment 11 by Deleted ...@, Aug 15 2013

thanks #8,
i suffered  from this error a long time, your comment is helpful. Thanks a lot.
Labels: Needs-Feedback
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.
Labels: -Needs-Feedback
Status: WontFix
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