[BUG] 736 is not fixed....

[master3395]

You don't understand what I'm saying. The documentation is lacking that the backup folder has to manually be moved to /home/backup with the domain user permission or copied there.

It does not state that it needs the domain's user permission anywhere.

The I/O issue you mentioned was fixed, it was only a minor warning bug with Centos 7.9... Has nothing to do with this issue at all.

Here's how to fix the Centos 7.9 bug if anyone else gets it, even if it's not related to CP.

How to fix GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed

The workaround is as follows:

groupadd -g 23 nohidproc
usermod -a -G nohidproc polkitd
mount -o remount,rw,hidepid=2,gid=nohidproc /proc
systemctl restart polkit
Add the following in /etc/fstab as well
echo "proc /proc proc defaults,hidepid=2,gid=nohidproc 0 0" >> /etc/fstab

After mount the new mount point

mount -a
systemctl restart polkit

By full backup, I mean full domain backup that is located in /home/domain.TLD/backup

Originally when you make a backup from CP, it goes to /home/domain.TLD/backup With these permissions (new user for every CP)

But /home/ has no backup folder on a clean install of cyber panel.

This has to be manually "moved" or "duplicated" from /home/domain.tld/backup over to /home/backup. That way, CP is allowed to read it. If /home/backup has "root" permissions or any other permission that is over the domain, CP will not be able to read it.

The problem with making a PR for me is that I don't have any idea where that permission line is, or how to make it so when you do a domain backup, it gets moved to /home/backup instead of /home/domain.tld/backup. Because having it stored under the domain when it can only be read when it's located under /home/backup sounds totally wrong.