Ssl error bad record mac

Facing ERR_SSL_BAD_RECORD_MAC_ALERT error when you try to access a web address, Right? Here ClickSSL guide can help you.

An SSL Certificate makes use of cryptography to transmit information between the server and the client securely. However, there are times when specific network interferences or interruptions can cause SSL errors like the ERR_SSL_BAD_RECORD_MAC_ALERT pop-up. This is one of the most annoying errors that keep you from accessing even the most reputed and trusted websites. Nevertheless, you must fix it as early as possible so that you can access your favorite websites without any further inconvenience.

What is ERR_SSL_BAD_RECORD_MAC_ALERT?

The ERR_SSL_BAD_RECORD_MAC_ALERT error is exclusive to the Chrome browser and may arise due to several reasons, which are either directly or indirectly connected to data transmission. Although pinpointing the exact cause for this issue might not be an easy thing to do, fixing it is, and that is precisely what you should focus on. If this is the first time you have encountered this type of error, you are probably worried about your safety, but you don’t have to.

This technical glitch is often caused due to some underlying problem on the client computer and can be easily verified. You can confirm that by trying to access legitimate websites like paypal.com that already have an SSL certificate installed and are running on the HTTPS protocol. If you continue to encounter the same error, it only confirms the above stated — it is a client-side issue that you need to resolve. As we have already mentioned, detecting the cause for this issue may not always be possible — not until you find a suitable solution, so you will have to try them out one by one. Let us now discuss some of the most effective ways to solve the ERR_SSL_BAD_RECORD_MAC_ALERT error.

1. Update your OS

Do you have a licensed operating system and update it from time to time? Probably not! But doing that could help resolve this SSL error and many other pre-existing vulnerabilities in your system. Your OS maker releases security patches from time to time in the form of updates. Downloading and installing those updates can not only prevent security concerns but can also fix technical glitches this SSL error.

Follow the below-mentioned steps to update your Windows OS right away.

• Click on the windows button and type ‘Settings’ in the search bar
• Click on Settings
• Click on the ‘Updates and Security’ Option
• Click on the ‘Download and Install’ Option

Once you are done updating your system, you might be prompted to restart your computer.

2. Update Google Chrome

Sometimes, updating the Google Chrome browser can resolve the ERR_SSL_BAD_RECORD_MAC_ALERT issue. You can do that by clicking on the three vertical dots on the top-right corner of the Chrome Browser and clicking on ‘more’. If you find the ‘update’ option, you need to click on that to update your browser.

On the other hand, if you do not see that option, it only indicates that your Chrome Browser is up to date. You can always confirm that by clicking on the three vertical dots on the top-right corner and then on ‘help’ and ‘About Google Chrome’. If your system is up to date, you will find a message like the one shown in the image below.

3. Antivirus

If you recently installed an Antivirus and have been experiencing this error ever since you already know what the problem is. It is never a good idea to meddle with your antivirus’ settings, but sometimes it becomes inevitable. Particularly, when you are using one that inspects the HTTPS and blocks out potentially dangerous traffic. In that case, you need to deactivate the HTTPS Inspection from your antivirus’ settings. However, please do this at your own risk and continue to avoid websites without SSL certificates installed on them.

4. Stop using Advanced Streaming Technologies

If you fancy high-speed internet, you most likely have a speed optimizing application or more advanced technology like a Killer Network card installed on your system. That could very well be the root cause of the ERR_SSL_BAD_RECORD_MAC_ALERT issue. The application or the Killer Network assigns a high priority to the data packets to boost the internet speed, which can sometimes cause this SSL error.

You can conveniently fix that by simply turning down the ‘Stream Detect’ function in your Killer Control Center or by uninstalling the speed-boosting application. Sometimes, your Killer Network card might need a more advanced solution. In that case, uninstall it by following the steps listed below.

• You need to first download the uninstaller tool from here
• Next, choose the Remove Killer Software option to uninstall
• Finally, restart the computer when prompted to do that, and you are done

Remember that fixing this issue could lower your internet speed, so you must be prepared for that.

5. Fix your Router

If none of the above fixes worked, your router could very well be the culprit. You can fix that by adjusting the Maximum Transmission Unit (MTU) of your router. This might sound a tad bit technical, but all it means is the maximum packet size that can be transmitted over the network. It is an advanced configuration that can be readjusted easily by typing 192.168.0.1. or 192.168.1.1. in the URL bar.

You can then look for the MTU settings under WAN and change it to 1400. In most cases, this should solve the problem, but we must mention that different routers may have different IPs and the ones mentioned above are the default ones.

Conclusion

We have discussed some of the most common ways to fix the ERR_SSL_BAD_RECORD_MAC_ALERT error, and one of those should work for you. None of these methods requires you to have any technical expertise, so try them out one at a time. Once you have resolved the error, do let us know which one worked out for you.

Recommended Reading:

• NET::ERR_CERT_AUTHORITY_INVALID Error on Google Chrome
• ERR_BAD_SSL_CLIENT_AUTH_CERT for Google Chrome
• NET::ERR_Certificate_Transparency_Required
• ERR_SSL_PROTOCOL_ERROR on Google Chrome
• ERR_CONNECTION_REFUSED in Chrome

bad record mac #1866

I have Java based server with SSL connections.
The C-based client connects to it using the OpenSSL library.

After a random period by the Java side error bad record mac occurs:
javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: bad record MAC
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.checkEOF(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.checkWrite(Unknown Source)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write(Unknown Source)

Try Java 6.0_21, 6.0_25, Java 7.0_79, OpenSSL 1.0.1h, 1.0.1u, 1.0.2j, 1.1.0b and 1.1.1 from development branch. Also, try to use different ciphers — no any results.

Application message size is about 20. 200 bytes. The data is correct, and the problem is only with message authentification code.

I suppose, OpenSSL has some issue with «mac».

CAP file with certificate can be downloaded here: https://yadi.sk/d/3cnBUIN3yCRKw

The text was updated successfully, but these errors were encountered:

I must update my team-mate. Our Java app receives a packet with probably bad_record_mac after a couple of minutes of proper communication with C-based OpenSSL side, then Java socket closes the connection. Full Java stack trace is as follows:

javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: bad record MAC
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.checkEOF(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.checkWrite(Unknown Source)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write(Unknown Source)
at java.nio.channels.Channels$WritableByteChannelImpl.write(Unknown Source)
. some internal code.
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.net.ssl.SSLException: bad record MAC
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.AppInputStream.read(Unknown Source)
at java.nio.channels.Channels$ReadableByteChannelImpl.read(Unknown Source)
. some internal code.

We suspect OpenSSL is the root of the problem.
Could someone help us to check our guess to find a workaround for the issue. Because now our mission-critical app loses data during reconnection after this error.

I got a similar problem when trying to connect to YouTube with Python. Bisecting shows that there’s a bad commit on the master branch: 5a8e54d good and 94ed2c6 is bad. Here’s the error message:

In Python, line 749 of _ssl.c reports the return value of SSL_do_handshake .

I can upload Wireshark capture files if necessary.

Источник

Исправление ошибки ERR_SSL_BAD_RECORD_MAC_ALERT

Некоторые пользователи жалуются на возникновение ошибки ERR_SSL_BAD_RECORD_MAC_ALERT при попытке доступа к некоторым веб-адресам. Большинство из них сообщают, что эта ошибка возникает только при попытке подключиться к account.google.com – адресу, который отвечает за обработку входа в систему большинства служб Google. Но эта проблема не относится исключительно к Google Chrome, поскольку большинство из пользователей, обнаруживших проблему, утверждают, что одни и те же веб-адреса также недоступны и в других веб-браузерах.

В чем причина ошибки ERR_SSL_BAD_RECORD_MAC_ALERT?

Мы провели анализ этой конкретной проблемы, просмотрев различные отчеты и решения, которые предприняли пользователи в попытке решить данную проблему. Исходя из этого, нам удалось собрать несколько распространенных сценариев, которые могут привести к появлению этой проблемы:

• Антивирусное программное обеспечение сторонних производителей проверяет трафик HTTPS. Большинство из антивирусных программ настроено для по умолчанию, некоторые из них проявляют чрезмерную защиту. Пользователи затронутые этой проблемой сообщают, что им удалось ее решить после отключения проверки HTTPS (сканирование SSL) в настройках AV сторонних производителей.
• Версия Chrome сильно устарела. Эта конкретная проблема встречается на компьютерах с более старой версией Chrome. Однако известно, что это происходит только с версией Chrome 40 и старше.
• Значение MTU маршрутизатора несовместимо с конфигурацией сети. Также есть подтверждения того, что ошибка возникает, если значение MTU маршрутизатора несовместимо с текущей конфигурацией сети.

Если в настоящее время вы пытаетесь решить эту конкретную проблему, то в нашей статье вы найдете проверенные шаги по устранению неполадок. Ниже есть несколько методов, которые использовали другие пользователи в аналогичной ситуации для решения этой проблемы.

Для достижения хороших результатов следуйте приведенным ниже способам, пока не найдете решения вашей проблемы, эффективное в конкретном сценарии.

Способ 1. Отключение проверки HTTPS (если это применимо) в настройках антивируса сторонних производителей

Согласно различным пользовательским отчетам, проблема может возникнуть в том случае, если у вас есть стороннее антивирусное программное обеспечение, настроенное для проверки трафика HTTPS с целью защиты от посторонних атак на защищенных каналах. Это не обязательно плохо, но сообщается, что многие из сторонних AV-пакетов, включая ESET, AVAST, BitDefender и McAfee, способствуют появлению ошибки ERR_SSL_BAD_RECORD_MAC_ALERT.

Большинству из пользователей, затронутых этой проблемой, удалось решить возникающую ошибку, отключив функцию проверки HTTPS в настройках AV. Вы можете решить эту проблему, запретив стороннему антивирусу выполнять любые проверки HTTPS (сканирование SSL). Нижеприведенные шаги, зависят от того, какой AV вы используете. В BitDefender вы можете отключить эту функцию, выбрав «Настройки»> «Основные»> «Дополнительно» и сняв флажок «Сканировать SSL».

Если вы не можете найти эти настройки (возможно, у вас нет функции отключения проверки HTTPS), то единственный способ убедиться в том, что ошибка возникает не из-за вашего AV, – это полностью удалить его.

Примечание: пользователи, столкнувшиеся с данной проблемой, сообщают, что ошибка ERR_SSL_BAD_RECORD_MAC_ALERT не возникает, когда Защитник Windows находится в активных параметрах безопасности.

Если этот метод не подходит для вашей конкретной ситуации или не помог решить данную проблему, то перейдите к следующему способу.

Способ 2: обновление браузера до последней версии

Некоторые из пользователей сообщают, что исправить эту проблему просто: достаточно обновить Chrome (или другой браузер, где возникает проблема) до последней версии. Но имейте в виду, что это решение может помочь только тем, кто столкнулся с проявлением данной ошибки в обозревателе очень ранней версии. К примеру, ошибку часто замечают на Chrome 20-40 версий.

Вот краткое руководство по устранению ошибки ERR_SSL_BAD_RECORD_MAC_ALERT в браузере Google Chrome:

1. Откройте Google Chrome и нажмите кнопку действия в правом верхнем углу. Затем нажмите Справка> О Google Chrome.
2. Примечание. Помните, что Google Chrome настроен на получение обновлений по умолчанию. Ручное вмешательство пользователя или некоторые расширения могут изменить этот параметр.
3. Дождитесь завершения сканирования, затем нажмите «Обновить Chrome» и установите новую версию.
4. Перезапустите браузер и посмотрите, была ли ваша проблема решена.

Практически точно также можно обновить браузеры и от других разработчиков. В общем, проблем у вас тут возникнуть не должно. Если оговариваемая ошибка все еще тревожит вас, то перейдите к следующему способу.

Способ 3: изменение MTU маршрутизатора на 1400

Многие пользователи, столкнувшиеся с ошибкой ERR_SSL_BAD_RECORD_MAC_ALERT, решили проблему изменением значения MTU маршрутизатора на 1400.

Шаги изменения MTU (Maximum Transmission Unit) будут отличаться в зависимости от производителя вашего маршрутизатора. Тем не менее было выявлено несколько общих шагов, которые укажут вам правильное направление решения проблемы:

1. Запустите веб-браузер и введите адрес входа в свой маршрутизатор. Большинство маршрутизаторов используют IP-адреса по умолчанию: 192.168.0.1. или 192.168.1.1.
2. Проверьте настройки маршрутизатора и настройки сети или WAN, которые позволят вам изменять размер MTU. На большинстве маршрутизаторов этот пункт можно найти в меню «Дополнительно» в разделе «Настройка WAN».
3. Установите размер MTU равным 1400 и нажмите «Сохранить» (или «Применить»), чтобы сохранить выбранные изменения.
4. Перезапустите ваш маршрутизатор и посмотрите, была ли решена проблема путем попытки доступа к тому же адресу, который ранее вызывал ошибку ERR_SSL_BAD_RECORD_MAC_ALERT.

Источник

bad_record_mac error when connecting to SSLv3-only server

This article applies to: Deskzilla 1.x-2.x, JIRA Client 1.x-2.x, and connecting to Bugzilla and JIRA servers via https://. connections.
For clarity, this article is written about JIRA Client and JIRA, but it applies to Deskzilla / Bugzilla as well.

Problem

When trying to establish a connection to a server with HTTPS-based URL, JIRA Client reports the following problem:

Check if the server allows only SSL v3 as the protocol for HTTPS connection.

The problem is caused by issues with Sun Java security package (#4815023), which makes the client (JIRA Client) try TLS even if it’s not supported on the server. This results in aborted connection.

Solution

The workaround is to enable only SSLv3 on the client. This can be done by setting «https.protocols» system property to «SSLv3», and also turning on «force.http.jre.executor» system property.

On Windows

Find «JIRA Client» start menu item (or other shortcut that you use to launch JIRA Client), Right-Click on it and select Properties. The Shortcut tab will appear, with the Target field containing something like «C:Program FilesJIRA Clientbinjiraclient.exe».

Click on the Target field and modify it so it says

Use copy&paste from this article to avoid typos.

Note the quotes in this example. Don’t put additional parameters inside the quotes around the .exe file path.

Источник

How to fix ERR_SSL_BAD_RECORD_MAC_ALERT error? [5 Ways]

Facing ERR_SSL_BAD_RECORD_MAC_ALERT error when you try to access a web address, Right? Here ClickSSL guide can help you.

An SSL Certificate makes use of cryptography to transmit information between the server and the client securely. However, there are times when specific network interferences or interruptions can cause SSL errors like the ERR_SSL_BAD_RECORD_MAC_ALERT pop-up. This is one of the most annoying errors that keep you from accessing even the most reputed and trusted websites. Nevertheless, you must fix it as early as possible so that you can access your favorite websites without any further inconvenience.

What is ERR_SSL_BAD_RECORD_MAC_ALERT?

The ERR_SSL_BAD_RECORD_MAC_ALERT error is exclusive to the Chrome browser and may arise due to several reasons, which are either directly or indirectly connected to data transmission. Although pinpointing the exact cause for this issue might not be an easy thing to do, fixing it is, and that is precisely what you should focus on. If this is the first time you have encountered this type of error, you are probably worried about your safety, but you don’t have to.

This technical glitch is often caused due to some underlying problem on the client computer and can be easily verified. You can confirm that by trying to access legitimate websites like paypal.com that already have an SSL certificate installed and are running on the HTTPS protocol. If you continue to encounter the same error, it only confirms the above stated — it is a client-side issue that you need to resolve. As we have already mentioned, detecting the cause for this issue may not always be possible — not until you find a suitable solution, so you will have to try them out one by one. Let us now discuss some of the most effective ways to solve the ERR_SSL_BAD_RECORD_MAC_ALERT error.

1. Update your OS

Do you have a licensed operating system and update it from time to time? Probably not! But doing that could help resolve this SSL error and many other pre-existing vulnerabilities in your system. Your OS maker releases security patches from time to time in the form of updates. Downloading and installing those updates can not only prevent security concerns but can also fix technical glitches this SSL error.

Follow the below-mentioned steps to update your Windows OS right away.

• Click on the windows button and type ‘Settings’ in the search bar
• Click on Settings
• Click on the ‘Updates and Security’ Option
• Click on the ‘Download and Install’ Option

Once you are done updating your system, you might be prompted to restart your computer.

2. Update Google Chrome

Sometimes, updating the Google Chrome browser can resolve the ERR_SSL_BAD_RECORD_MAC_ALERT issue. You can do that by clicking on the three vertical dots on the top-right corner of the Chrome Browser and clicking on ‘more’. If you find the ‘update’ option, you need to click on that to update your browser.

On the other hand, if you do not see that option, it only indicates that your Chrome Browser is up to date. You can always confirm that by clicking on the three vertical dots on the top-right corner and then on ‘help’ and ‘About Google Chrome’. If your system is up to date, you will find a message like the one shown in the image below.

3. Antivirus

If you recently installed an Antivirus and have been experiencing this error ever since you already know what the problem is. It is never a good idea to meddle with your antivirus’ settings, but sometimes it becomes inevitable. Particularly, when you are using one that inspects the HTTPS and blocks out potentially dangerous traffic. In that case, you need to deactivate the HTTPS Inspection from your antivirus’ settings. However, please do this at your own risk and continue to avoid websites without SSL certificates installed on them.

4. Stop using Advanced Streaming Technologies

If you fancy high-speed internet, you most likely have a speed optimizing application or more advanced technology like a Killer Network card installed on your system. That could very well be the root cause of the ERR_SSL_BAD_RECORD_MAC_ALERT issue. The application or the Killer Network assigns a high priority to the data packets to boost the internet speed, which can sometimes cause this SSL error.

You can conveniently fix that by simply turning down the ‘Stream Detect’ function in your Killer Control Center or by uninstalling the speed-boosting application. Sometimes, your Killer Network card might need a more advanced solution. In that case, uninstall it by following the steps listed below.

• You need to first download the uninstaller tool from here
• Next, choose the Remove Killer Software option to uninstall
• Finally, restart the computer when prompted to do that, and you are done

Remember that fixing this issue could lower your internet speed, so you must be prepared for that.

5. Fix your Router

If none of the above fixes worked, your router could very well be the culprit. You can fix that by adjusting the Maximum Transmission Unit (MTU) of your router. This might sound a tad bit technical, but all it means is the maximum packet size that can be transmitted over the network. It is an advanced configuration that can be readjusted easily by typing 192.168.0.1. or 192.168.1.1. in the URL bar.

You can then look for the MTU settings under WAN and change it to 1400. In most cases, this should solve the problem, but we must mention that different routers may have different IPs and the ones mentioned above are the default ones.

Conclusion

We have discussed some of the most common ways to fix the ERR_SSL_BAD_RECORD_MAC_ALERT error, and one of those should work for you. None of these methods requires you to have any technical expertise, so try them out one at a time. Once you have resolved the error, do let us know which one worked out for you.

Источник

Question

Issue: How to fix ERR_SSL_BAD_RECORD_MAC_ALERT error?

I recently updated my Windows 10 PC, and now I cannot access many sites, including https://support.microsoft.com/en-us. I use Google Chrome web browser, and it shows an error message instead of loading the site – ERR_SSL_BAD_RECORD_MAC_ALERT. Is there a way to fix this? Many thanks.

Solved Answer

ERR_SSL_BAD_RECORD_MAC_ALERT is an SSL certificate error that is specific to Google Chrome browser – while MS Edge users would encounter an equivalent – INET_E_DOWNLOAD_FAILURE error. SSL certificates are crafted for your own safety – they use a cryptographic key to digitally sign the owner of the site and bind a domain name and the organization together. If some problems arise with the certificate, users might start receiving various SLL errors, including ERR_SSL_BAD_RECORD_MAC_ALERT.

While no particular sites are connected to ERR_SSL_BAD_RECORD_MAC_ALERT error, users cannot access legitimate and trusted sites, such as Microsoft support or Google support domains. Therefore, there is no doubt that these sites have a valid certificate, and the problem lies somewhere else.

One of the most likely culprits and ERR_SSL_BAD_RECORD_MAC_ALERT error causes is third-party anti-malware software that is set to scan all the encrypted connections. Nevertheless, other reasons, like the outdated Google Chrome web browser, can also be the cause of the problem.

Find out how to fix ERR_SSL_BAD_RECORD_MAC_ALERT error

However, to fix ERR_SSL_BAD_RECORD_MAC_ALERT error, you will have to apply various solutions that we provide below. Before you do that, however, we would recommend you to scan your computer with ReimageMac Washing Machine X9, it can fix various errors and repair damage done by malware when trying to recover from the infection.

For the record, you should not enter financial or personal information into sites that do not provide a safe connection (HTTPS)^[1] that includes a valid SSL certificate, as the data can be intercepted and stolen not necessarily by website authors but hackers. Consequently, you might face money loss or even identity theft.

Fix 1. Update Google Chrome and Windows

Regardless of what type of computer problem you are facing, updating the software should be your first troubleshooting option. In this particular instance, you should make sure that Windows are updated, as well as Google Chrome. The latter should update automatically as long as you turn off the browser and enable it again. To update Windows, follow these steps:

• Right-click on Start button and select Settings
• Go to Update & Security
• On the right-side, click on Check for updates

  Outdated software can be a cause of various errors

• Windows should automatically download and install the latest updates
• Reboot your computer

Fix 2. Add problematic sites to Trusted sites list

This ERR_SSL_BAD_RECORD_MAC_ALERT error fix helped many users, so you should try this method if you are having problems with just a few particular sites and the issue is not universal:

• Type in Control Panel into Cortana’s search box and hit Enter
• Go to Network and Internet > Internet Options
• Select Security tab and click on Trusted sites
• Click on Sites
• Type in the problematic site address and click Add

  Add the problematic site to Trusted sites

• Try entering the website

Fix 3. Stop the anti-virus scanning the encrypted connections

ERR_SSL_BAD_RECORD_MAC_ALERT was mostly present in computers of users who used such anti-malware tools like Bitdefender.^[2] It is important to keep your system protected, so you should not uninstall security software completely. However, you can disable the excessive HTTPS scanning (note that these instructions apply to BitDefender and can differ depending on security application you are using):

• Go to Features and select Web Protection
• Select Settings
• Under Scan SSL option toggle the switch to the left to turn the feature off

  Disable SSL scanning scanning feature on your anti-virus program

Fix 4. Set Windows Time service to automatic

Many SSL errors are connected to incorrect time settings. To permanently fix ERR_SSL_BAD_RECORD_MAC_ALERT or similar SSL errors, you should set the startup time of Windows Time service to automatic:

• Press Win + R on your keyboard
• Type in services.msc and hit Enter or click OK
• Scroll down and locate Windows Time service
• Double-click on it and to open its Properties
• Under Startup type, pick Automatic from the drop-down menu
• Click Apply and then select Start

  Set Windows Time service to automatic setting

• Reboot your computer

Fix 5. Change the settings of your router

Another way to fix ERR_SSL_BAD_RECORD_MAC_ALERT error by changing the MTU^[3] (Maximum transmission unit) rate to 1400. For that, you will have to log in to your router environment via the browser (you need to know admin credentials which you obtained when setting up the account with the ISP).^[4] You should try using a default IP address to enter the account, such as 192.168.0.1, 192.168.1.1, 192.168.2.1, or 192.168.1.100.

Once inside, look for such option like Advanced, Setup or WAN settings where you would be able to change the value of MTU. Set the size to 1400 and press OK.

Repair your Errors automatically

ugetfix.com team is trying to do its best to help users find the best solutions for eliminating their errors. If you don’t want to struggle with manual repair techniques, please use the automatic software. All recommended products have been tested and approved by our professionals. Tools that you can use to fix your error are listed bellow:

I got a similar problem when trying to connect to YouTube with Python. Bisecting shows that there’s a bad commit on the master branch: 5a8e54d good and 94ed2c6 is bad. Here’s the error message:

$ ./python -c 'import urllib.request; urllib.request.urlopen("https://www.youtube.com/")'
Traceback (most recent call last):
  File "/home/yen/Projects/cpython/Lib/urllib/request.py", line 1318, in do_open
    encode_chunked=req.has_header('Transfer-encoding'))
  File "/home/yen/Projects/cpython/Lib/http/client.py", line 1232, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/home/yen/Projects/cpython/Lib/http/client.py", line 1278, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/home/yen/Projects/cpython/Lib/http/client.py", line 1227, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/home/yen/Projects/cpython/Lib/http/client.py", line 1019, in _send_output
    self.send(msg)
  File "/home/yen/Projects/cpython/Lib/http/client.py", line 957, in send
    self.connect()
  File "/home/yen/Projects/cpython/Lib/http/client.py", line 1393, in connect
    server_hostname=server_hostname)
  File "/home/yen/Projects/cpython/Lib/ssl.py", line 401, in wrap_socket
    _context=self, _session=session)
  File "/home/yen/Projects/cpython/Lib/ssl.py", line 808, in __init__
    self.do_handshake()
  File "/home/yen/Projects/cpython/Lib/ssl.py", line 1061, in do_handshake
    self._sslobj.do_handshake()
  File "/home/yen/Projects/cpython/Lib/ssl.py", line 683, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: SSLV3_ALERT_BAD_RECORD_MAC] sslv3 alert bad record mac (_ssl.c:749)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/yen/Projects/cpython/Lib/urllib/request.py", line 223, in urlopen
    return opener.open(url, data, timeout)
  File "/home/yen/Projects/cpython/Lib/urllib/request.py", line 526, in open
    response = self._open(req, data)
  File "/home/yen/Projects/cpython/Lib/urllib/request.py", line 544, in _open
    '_open', req)
  File "/home/yen/Projects/cpython/Lib/urllib/request.py", line 504, in _call_chain
    result = func(*args)
  File "/home/yen/Projects/cpython/Lib/urllib/request.py", line 1361, in https_open
    context=self._context, check_hostname=self._check_hostname)
  File "/home/yen/Projects/cpython/Lib/urllib/request.py", line 1320, in do_open
    raise URLError(err)
urllib.error.URLError: <urlopen error [SSL: SSLV3_ALERT_BAD_RECORD_MAC] sslv3 alert bad record mac (_ssl.c:749)>

In Python, line 749 of _ssl.c reports the return value of SSL_do_handshake.

Python version: 12b4e7209d03

I can upload Wireshark capture files if necessary.