Issue Im Getting Diagnose & Repair Error

[Ash95]

The operation failed with the following error: {"id":1,"cmd":"plesk repair fs -n","type":"progress","message":"Checking Linux system files","level":0} {"id":1,"cmd":"plesk repair fs -n","type":"success","message":"Checking Linux system files","level":0} {"id":2,"cmd":"plesk repair fs -n","type":"progress","message":"Checking virtual hosts' file system","level":0} {"id":3,"cmd":"plesk repair fs -n","type":"error","message":"There is incorrect ownership on some items in the WWW root directory of the domain '******.com'.","level":1}

i have noticed im getting this when i run a check

 

[IgorG]

The check showed an error. Now it needs to be fixed. Try it with the command:

# plesk repair fs -y

 

[gastonwagner]

Hi all, hope all of you are well.

# plesk version | grep "Product version"
Product version: Plesk Obsidian 18.0.39.1

# cat /usr/local/psa/version (AlmaLinux fresh install)
18.0.39 CentOS 8 1800211014.23

When I try to repair it shows this:

# plesk repair fs -y

Checking Linux system files

There are incorrect permissions on some items: /dev/null .......... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................. [2021-11-09 14:13:30.594] 2721181:618aac3a90f7e ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/fsmng' '--set-ac' '/dev/null'] with exit code [1]
[FAILED]
- fsmng failed: ERROR:[Errno 1] Operation not permitted:
'/dev/null'

There are incorrect permissions on some items: /dev/random ........ [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................. [2021-11-09 14:13:31.945] 2721181:618aac3a90f7e ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/fsmng' '--set-ac' '/dev/random'] with exit code [1]
[FAILED]
- fsmng failed: ERROR:[Errno 1] Operation not permitted:
'/dev/random'

There are incorrect permissions on some items: /dev/urandom ....... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................. [2021-11-09 14:13:33.354] 2721181:618aac3a90f7e ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/fsmng' '--set-ac' '/dev/urandom'] with exit code [1]
[FAILED]
- fsmng failed: ERROR:[Errno 1] Operation not permitted:
'/dev/urandom'

Checking virtual hosts' file system
One or more files or directories in the root directory of the domain
'iot.org.ar' are either writable by anyone or neither readable nor
writable by the owner. Such permissions are insecure and may result
in or indicate a security breach .................................. [INFO]
To see more details, run the command in the verbose mode: plesk repair fs -verbose

There is incorrect ownership on some items in the WWW root directory
of the domain 'dommm.com.ar' ............................. [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect ownership ................................... [FIXED]

Error messages: 4; Warnings: 0; Errors resolved: 1



Any ideas?

 

[gastonwagner]

Note: Plesk + Almalinux is installed in an Proxmox LXC container

 

[sysbitnet]

After long testing I think this problem is so long here, and only when it is installed on Container. When installing Plesk on VM type does not get any error.

I get the same error and problem as before but for the community, I uploaded a screenshot, for the future if someone gets the same error.

So a little more analysis and someone of explanation from my side can be like.
Container Isolation:
Containers are designed to provide isolated environments. They do this, in part, by limiting the container's ability to interact with certain system-level resources. This can include restrictions on modifying device files in /dev.

Ownership and Permissions in Containers:
The ownership of these device files as nobody:nogroup in LXC container is likely a security and isolation feature of LXC. It prevents containerized applications from inadvertently or maliciously affecting these critical system files, which could impact both the container and the host system.

Managing Changes in Containers:
If need to change the ownership or permissions of these files within the LXC container, it's typically done via container configuration settings rather than direct manipulation within the container. This is because changes within the container can be restricted or overridden by the container management system.

Potential Implications of Changes:
Attempting to forcibly change the ownership of these device files within the LXC container might not be advisable. It could lead to unexpected behavior or stability issues within the container. The configuration set by LXC is usually optimized for both functionality and security.

Consulting Documentation and Support:
For specific needs or configurations, consult the LXC documentation or relevant support forums. If there is a specific requirement for these device files to have root:root ownership within the container, there might be a recommended method for achieving this within the scope of LXC's configuration capabilities.

In summary, the difference in ownership of /dev/null, /dev/random, and /dev/urandom between the standard Debian / Ubuntu or Almalinux / RockyLinux server and the LXC container is due to the differing nature and security models of standalone systems versus containerized environments. Changes to these files within the container should be handled cautiously and ideally through LXC's configuration mechanisms.

But the problem that Plesk has I hope can be fixed because after testing all versions that are available and Plesk support, I get the same error on fresh Plesk installation. In the image that I attached, you can see, where is the problem.

As i said i testing on all support OS in this moment what you see on the official Plesk Software Requirements for Plesk Obsidian

And if you scroll down you can see

Supported virtualization​

The following virtualization platforms are supported:

• VMware
• XEN
• Virtuozzo 7
• OpenVZ
• KVM
• Hyper-V
• LXC (Docker)

So that means Plesk needs to work on how can officially support Proxmox