Failed to upload backup ssl/tls alert bad record mac

[milandzuris]

The problem

Hey, Backup was created but only uploaded to Google Drive not HA Cloud where is Problem?.

Logger: homeassistant.components.backup
Source: components/backup/manager.py:594
integration: Backup (documentation, issues)
First occurred: 05:54:37 (1 occurrences)
Last logged: 05:54:37

Upload failed for cloud.cloud: Failed to upload backup Failed to fetch: [Errno 1] [SSL: SSLV3_ALERT_BAD_RECORD_MAC] ssl/tls alert bad record mac (_ssl.c:2648)

What version of Home Assistant Core has the issue?

2025.4.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

https://www.home-assistant.io/integrations/backup/

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (backup) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of backup can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign backup Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

backup documentation
backup source
_{^{(message by IssueLinks)}}

[MartinHjelmare]

That error is probably due to something in your environment being not correctly configured or interfering with the request.

[MartinHjelmare]

Do you have any custom network configuration or applications that handle network settings or could interfere with events in your network?

[milandzuris]

Do you have any custom network configuration or applications that handle network settings or could interfere with events in your network?

yes PiHole, but HA is connected to CloudFlare DNS and I have the same settings before this problem, I am seeing this problem for the first time now.

[MartinHjelmare]

Can you try temporarily disabling PiHole and/or CloudFlare DNS and see if it makes a difference? You can create an automatic backup from the GUI, so you don't need to wait for the scheduled backup to test it.

Activate debug logging for backup and cloud integrations when testing. The cloud backup platform will retry for some minutes before giving up if there's an error but the debug logs will show immediately if there's a problem.

[yearsy]

I am experiencing the exact same issue and have created bug report #142289 for further details. I have also tested the scenario without a Pi-hole in the network, but unfortunately, the backup was still unsuccessful.

[MartinHjelmare]

Let's continue here.

[MartinHjelmare]

I'd try achieving a "clean" network with as little things as possible that could interfere with the request to try and find a state where it works. Then work your way back adding things that you normally have active, until it breaks again.

[yearsy]

The backup failures are occurring randomly. I’ve experienced several consecutive days of failed backups, followed by one or two days where the backups succeed, without making any changes to my setup. This inconsistency happens without any logical explanation or identifiable pattern.

These issues have been present since the introduction of the new cloud backup system at the end of 2024.

To rule out possible causes and test under clean conditions, I’ve taken the following steps:

• Removed Pi-hole from the network to eliminate potential DNS-related issues.
• Rebooted the system into safe mode to minimize interference from other processes.
• Reduced the scope of the backup to configuration files only, to limit data volume.
• Enabled debug-level logging for both the Nabucasa cloud service and the backup process.

Despite these efforts, the backups continue to fail. The only consistent log message is:

[Failed to upload backup to cloud [Errno 1] [SSL: SSLV3_ALERT_BAD_RECORD_MAC]

[home-assistant]

Hey there @home-assistant/cloud, mind taking a look at this issue as it has been labeled with an integration (cloud) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of cloud can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign cloud Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

cloud documentation
cloud source
_{^{(message by IssueLinks)}}

[ludeeus]

Could you make sure the date and time on the machine is correct?
If it is then remove all custom integrations, reboot, and then use the command ha core rebuild when it starts up again.