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

[Maarten]

If anyone would like to run a script on their RMM tooling, here you go, this worked for us.

#!/bin/bash

# Set variables
TARGET_DIR="/usr/local/psa/admin/sbin"
BACKUP_FILE="/root/pmm-ras_backup"
TGZ_URL="https://support.cpanel.net/attachments/token/mRHWnvEh1prhjg0YITSvI3PnN/?name=pmm-ras-rhel-alma-9.x-plesk-18.0.6x.tgz"
TGZ_FILE="pmm-ras-rhel-alma-9.x-plesk-18.0.6x.tgz"

# Navigate to the target directory
cd "$TARGET_DIR" || { echo "Failed to navigate to $TARGET_DIR. Exiting."; exit 1; }

# Create a backup of the pmm-ras file
if [ -f "$TARGET_DIR/pmm-ras" ]; then
  cp -a "$TARGET_DIR/pmm-ras" "$BACKUP_FILE"
  echo "Backup of pmm-ras created at $BACKUP_FILE."
else
  echo "No pmm-ras file found to back up."
fi

# Remove the original pmm-ras file
if [ -f "$TARGET_DIR/pmm-ras" ]; then
  rm -f "$TARGET_DIR/pmm-ras"
  echo "Original pmm-ras file removed."
else
  echo "Original pmm-ras file does not exist. Skipping removal."
fi

# Download the new pmm-ras file
wget -O "$TGZ_FILE" "$TGZ_URL"
if [ $? -eq 0 ]; then
  echo "Downloaded $TGZ_FILE successfully."
else
  echo "Failed to download $TGZ_FILE. Exiting."
  exit 1
fi

# Extract the downloaded file
tar -xvzf "$TGZ_FILE" || { echo "Extraction of $TGZ_FILE failed. Exiting."; exit 1; }
echo "Extraction completed successfully."

# Set permissions for the extracted file
if [ -f "$TARGET_DIR/pmm-ras" ]; then
  chmod 755 "$TARGET_DIR/pmm-ras"
  chown root:root "$TARGET_DIR/pmm-ras"
  echo "Permissions set for pmm-ras."
else
  echo "pmm-ras file not found after extraction. Exiting."
  exit 1
fi

# Clean up the downloaded tar.gz file
rm -f "$TGZ_FILE"
echo "Cleanup: Removed $TGZ_FILE."

echo "All tasks completed successfully."

Thanks for sharing this script. Could you clarify what type of RMM tool you're referring to? Are you using a specific platform (e.g., MeshCentral, NinjaOne, or similar), or do you mean tools like Ansible or Puppet for automated deployments? It would be helpful for others who want to run this script but are unsure how to integrate it with their setup.

 

[totaliweb]

Hi,

This problem is really annoying, we are living with anxiety about backups since they are all configured on remote storage and so it's really a big problem. Can't fix and update the situation first?

Thanks.

 

[quantim]

Do you have ETA?

 

[occinodo]

Thanks for sharing this script. Could you clarify what type of RMM tool you're referring to? Are you using a specific platform (e.g., MeshCentral, NinjaOne, or similar), or do you mean tools like Ansible or Puppet for automated deployments? It would be helpful for others who want to run this script but are unsure how to integrate it with their setup.

Hi, we are using NinjaOne but probably it would work with any RMM

 

[Maarten]

Do you have ETA?

The temporary solution can be found here:

Issue - Error:030000BD:digital envelope routines::update error

In ticket 95402670 I asked support to provide a method to manually tar the locally generated backups so that we can manually upload them to an external storage. The command provided works so far that it creates the .tar file including all the backup content. But it fails at the end with the same...

talk.plesk.com

The ETA for the hotfix release is the 25th of November.

 

[manos]

Hello, everyone. This is just an estimate, we will do our best to release the fix earlier than that. In the meantime, the workaround we can suggest is:

1. Connect to the server via SSH.
2. Navigate to this directory:
   
   
3. Create a backup copy of the pmm-ras file using the following command:
   
   
4. Remove the original file:
   
   
5. Upload the pmm-ras-rhel-alma-9.x-plesk-18.0.6x.tgz file attached to the /usr/local/psa/admin/sbin directory.
6. Extract it as follows:
   

You may download the archive from here.

Is not it funny that download link is fro, cpanel? ¨)

 

[Sebahat.hadzhi]

Hello,

For those of us who have Plesk 18.0.59 installed, logically the provisional solution provided does NOT work.
When entering the Backup Management menu, a 500 error appears.
Do we necessarily have to update Plesk to ; 18.0.6x ?

Any ideas to be able to perform remote backups with Plesk: 18.0.59?

Thank you all.

It will be best to consider an upgrade. A patch most likely will not be introduced for Plesk 18.0.59 considering it is currently 6 updates ahead.

Hi,

This problem is really annoying, we are living with anxiety about backups since they are all configured on remote storage and so it's really a big problem. Can't fix and update the situation first?

Thanks.

We understand the inconvenience caused by the issue and we are extremely sorry. Could you please try the workaround provided in #post-954868 until the official fix is released?

 

[rkbonatto]

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


Plesk Obsidian v18.0.65_build1800241106.13 os_RedHat el9
AlmaLinux 9.5 (Teal Serval)


The curiosity is:
This server worked perfectly with centos7 without any problems, I tried updating centos2alma with the provided script, piece of s, 4 hours and a thousand errors, I just did a clean and fresh install with alma9 and boom I got some bugs. What plesk is doing is really a joke, forcing users to update their servers otherwise they will be charged extra fees for running an outdated OS, and licenses have gone up exorbitantly in price, from January onwards they will charge the price of the VPS license almost 2x the value of Metal in the past.
This is what happens when Cpanel developers work on something that was beautiful and unique like Plesk, they are transforming Plesk into Cpanel, a real affront, with each update they release Plesk looks more like cpanel, full of texts and unnecessary functions, confusing panel with zero UI/UX

 

[jasviwhs]

Hi, the problems persist in
Plesk Obsidian 18.0.65 Update #1.

When will it be possible to make backups?
We have a very serious situation and problem!

 

[macadia]

Hi, the problems persist in
Plesk Obsidian 18.0.65 Update #1.

When will it be possible to make backups?
We have a very serious situation and problem!

Hi, did you apply the temporary solution commented a few posts before?

 

[jasviwhs]

Hi, did you apply the temporary solution commented a few posts before?

I was waiting for the proper update that I had set for the 25th.

I have a snapshot of the server in AWS, but I didn't want to mess around more than I should since not everyone has had that patch work.

 

[manos]

Hi all!

Any update?
25th in what time zone?

 

[Sebahat.hadzhi]

Hello, everyone. We have released the fix for the issue with the backup creation. If you have automatic updates enabled this update should be installed automatically overnight. Plesk Obsidian 18.0.65 Update 2:

Fixed the issue where, on Red Hat Enterprise Linux 9 servers, creating a backup in via the CLI failed with the “Unable to create the remote backup: Cannot update digest: error:030000BD:digital envelope routines::update error” error.

 

[macadia]

Thanks, installed

 

[manos]

Confirming problem fixed for backups!

 

[jasviwhs]

confirmed!
full backup in AWS completed successfully after update #2.
Thank you!

 

[ALister]

Any update on the

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

issue please. ETA for fix was 2 days ago.

 

[ALister]

Any update on the

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

issue please. ETA for fix was 2 days ago.

I have tested the backups on ftp, sftp & s3 storage and I can confirm they were all successful, as far as I am concerned this issue has now been fixed, thank you.

 

[ddowdell]

This is working for me on S3, but one subscriber uses OneDrive and that appears to still be failing.

Warning:
Unable to create the remote backup: Transport error: Extension transport: ext://one-drive-backup/subscription/3/: Microsoft OneDrive returns the error: The object specified does not belong to a list.

 

[Sebahat.hadzhi]

Thank you for your update, @ddowdell. The issue you are experiencing with OneDrive is not related to the bug discussed in this thread. We are aware of that issue as well and there is a dedicated thread for it you can find here.