NEW Backup (beta) / Restore Account -> Does not list accounts to restore

Even after selecting the directory containing the backup files, the system does not list any accounts to restore. I tried changing the directory (by copying the files), but it still doesn't list them. What could be happening? I have used this feature to restore accounts successfully in the past, but it isn't working now.

I didn't find any errors in the log. Is there a specific log I should check?

CWPpro version: 1.8
AlmaLinux 8

I wish there were a CLI command for restoration.

Hi,

Please update to the latest version that was released today

Hi,
Can someone explain how a developer can release an update without writing about the changes and fixes?
Recovery doesn't work. Version 1.9
Distro Name: AlmaLinux release 9.8 (Olive Jaguar)

Hi,

Please update to the latest version that was released today

I did the update but still not working.

CWPpro version: 1.9

Distro Name: AlmaLinux release 8.10 (Cerulean Leopard)
Kernel Version: 4.18.0-553.154.1.el8_10.x86_64
Platform: x86_64 Dedicated

 I have the same problem I think, It backups up okay to local and an S3 garage bucket, but when I go to the restore button, there is nothing listed under user accounts. Below that it says in the yellow box, "Please first select the backup you want to restore."

Well I can't select any backups because nothing is listed there - the top field is totally blank, no accounts to select. I'm pretty livid about this. Long ago this worked; I don't know how long it has been broken, but it is broken in AlmaLinux 8 and 9 on CWP version 1.9. I have CWP updates set to two weeks, do I need to step that up to immediately to get a bugfix or something? I am so used to having to fix things that are broken in CWP that I fear taking breaking updates from this operation...

This truly is not acceptable. To be able to make backups but not restore them makes it 100% worthless.

We urgently need a solution for restoring backups.

I’m already on version 1.10, but there’s no fix; the issue persists.

I am facing the same issue on over 30 servers running CWPpro version 1.10.

We need to migrate urgently due to recent vulnerabilities, but CWP is hindering the process.

print: https://i.imgur.com/fHoniFE.png

Please help

My server experienced a security vulnerability too.

I now suspect the breach is related to CWP, and that the backup system — specifically the restore function — was deliberately compromised to prevent the recovery of compromised sites.

My server experienced a security vulnerability too.

I now suspect the breach is related to CWP, and that the backup system — specifically the restore function — was deliberately compromised to prevent the recovery of compromised sites.

Servers were exploited using v1/backup.

I have done quite a bit more troubleshooting on this and can confirm that the S3 restore problem occurs before CWP ever attempts to connect to the S3 server.

My setup is AlmaLinux 9.8 using the New Backup (beta) system. Local restore is working now, but S3 restore still does not populate the Frequency, Backup, or User Accounts fields.

The S3 storage is a Garage S3-compatible server. Backups to it are working normally.

I verified the following:

* The backup archives are present in the S3 bucket in the expected structure, for example:
  `full/daily/Sunday/accounts/user.tar.gz`
* Using the same endpoint, bucket, region, access key and secret key stored in CWP's backup configuration, `aws s3 ls` successfully lists the bucket, directories and account backup files.
* CWP itself successfully uploads backups to this same S3 bucket.
* The CWP AJAX request for `searchbackupaccount` returns HTTP 200, but the response is only 5 bytes when S3 is selected. The equivalent Local request returns 82 bytes and the restore selections populate normally.
* There are no corresponding errors recorded in the CWP backup `errors` or `restore` SQLite tables.
* I ran tcpdump while selecting the S3 restore source. CWP made no connection at all to the configured S3 server.
* I then traced the CWP PHP-FPM process. During the S3 restore request CWP reads `/usr/local/cwp/.conf/backup_config.sqlite` and checks that the AWS CLI is installed with `which aws`.
* CWP finds `/usr/bin/aws`, but it never executes an `aws` command after that check.
* Since no AWS command is executed and no network connection is made to the S3 server, the restore code appears to stop locally before it ever attempts to enumerate the S3 bucket.

I also compared the working Local backup configuration with the S3 configuration and tested the few potentially relevant differences. Changing `S3_PATH` from an empty value to the database default of `0` made no difference. I also tested `DEFAULUSERBACKUP=0` instead of `1`, with no difference. Both values were restored to their original settings after testing.

At this point I don't believe this is an S3 credentials, permissions, endpoint, network, or AWS CLI problem. All of those work when tested directly, and CWP is successfully writing backups to the same bucket.

It appears that the New Backup (beta) S3 restore discovery code is returning before it ever attempts to access S3.

Hopefully this additional information will help locate the problem.