Resolved Error:030000BD:digital envelope routines::update error

[sup_ajn]

Server operating system version

AlmaLinux 9.5 (Teal Serval)

Plesk version and microupdate number

Plesk Obsidian 18.0.64 Update #1 Web Host Edition

I'm getting this error during scheduled or manual backups to FTP server, settings are ok and can be access without problems with filezilla.

Unable to create the remote backup: Cannot update digest: error:030000BD:digital envelope routines::update error

 

[macadia]

Hi, same problem here and reported to my ISP... They say they are waiting for a response from Plesk. FTP backup to Hetzner, the FTP is ok.

<message severity="error">
<description>Unable to create the remote backup: Cannot update digest: error:030000BD:digital envelope routines::update error</description>
</message>

 

[manos]

Yes same here, problem started today, whatever backup i am trying from linux plesk servers to whatever backup server, same message


Unable to create the remote backup: Cannot update digest: error:030000BD:digital envelope routines::update error

Can be related to almalinux 9.5? The only server that works is almalinux 9.4

 

[manos]

Hi, same problem here and reported to my ISP... They say they are waiting for a response from Plesk. FTP backup to Hetzner, the FTP is ok.

<message severity="error">
<description>Unable to create the remote backup: Cannot update digest: error:030000BD:digital envelope routines::update error</description>
</message>

What operating system?

 

[manos]

Definitely seems related to almalinux 9.5 as i tested now at three 9.4 servers and works fine, these are
the only servers i had not automatic system updates enabled, all the others seem updated today to 9.5

 

[macadia]

AlmaLinux 9.5 (Teal Serval)
Plesk Obsidian 18.0.65, update 1
Web Host Edition

 

[Sebahat.hadzhi]

Hello, everyone. Thank you for reporting the issue. We are aware of it and our team is already investigating it. The behavior is identified with bug ID PPP-66727 and it is observed only on AlmaLinux 9.5/Red Hat 9. Unfortunately, I cannot provide any ETA for the fix release at this point.

In the meantime, the workaround we can suggest is to create backups manually from Plesk > Tools & Settings > Backup Manager > Backup

 

[manos]

Hello, everyone. Thank you for reporting the issue. We are aware of it and our team is already investigating it. The behavior is identified with bug ID PPPM-14674 and it is observed only on AlmaLinux 9.5/Red Hat 9. Unfortunately, I cannot provide any ETA for the fix release at this point.

In the meantime, the workaround we can suggest is to create backups manually from Plesk > Tools & Settings > Backup Manager > Backup

Same problem is at manual backups

 

[Bitpalast]

@Sebahat.hadzhi This is critical, it will need a fast hotfix, because it leaves the affected servers without valid backups.

 

[manos]

Another problem is that issue seems to affect also plesk migration that would be a solution, will check now in some servers

 

[manos]

Ufff migration works fortunately

 

[Sebahat.hadzhi]

Same problem is at manual backups

Sorry, just want to confirm - you are encountering the same error when attempting to perform the backup manually through the Plesk interface, not via the cli - is that right?

 

[macadia]

I can confirm that making backup manually fails too

Unable to create the remote backup: Cannot update digest: error:030000BD:digital envelope routines::update error

 

[Sebahat.hadzhi]

@Sebahat.hadzhi This is critical, it will need a fast hotfix, because it leaves the affected servers without valid backups.

Yes, we are aware. The bug was recently identified and our engineers are already actively working on it.

 

[Bitpalast]

It occurs independently from an enabled or disabled backup encryption and independently from FTP/FTPS settings. It affects not only the server backup, but all backup operations, including end user (subscriber) backups. It also has one more caveat: The failed remote backup is stored locally until manually removed from the local storage. For server backups this will fill local disc space fast.

 

[Bitpalast]

It is related to the recent Alma 9.4 -> 9.5 update.

 

[Bitpalast]

I've also tested it on the CLI, same error.

 

[manos]

It occurs independently from an enabled or disabled backup encryption and independently from FTP/FTPS settings. It affects not only the server backup, but all backup operations, including end user (subscriber) backups. It also has one more caveat: The failed remote backup is stored locally until manually removed from the local storage. For server backups this will fill local disc space fast.

Yes can confirm it as i use only remote backups, that "temporary" local backups are stored to /var/lib/psa/dumps when remote backup fails. Seems the biggest caveat in this case as we need to deactivate all scheduled backups before server storage gets filled near 100%

 

[manos]

Finally expriencing some problems at plesk migrations. Do not know if there was problem before today's incident but usually i never had problems.
Any other with Alma 9.5 tried Plesk migrations today?

Errors
Failed to create the remote configuration dump on the target server. Not all settings may be migrated.
Error message: Command execution failed on the local server with non-zero exit code.
stderr: rsync: [sender] link_stat "/root/plesk_migrator/plesk_migrator-v4nuycnpe0l6uk21ir1iiz0t12he48nu/backup.tar" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1823) [Receiver=3.2.3]
rsync: [Receiver] write error: Broken pipe (32)

Tried to migrate same site to 9.4 server and worked so i assume maybe it is related?

Thanks

 

[manos]

Hi,

Any update?