• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Backup warning, due to root perms of .ssh/ directory. Backup "was created and can be restored, although some minor issues occurred."

Paul Larson

Basic Pleskian
Server operating system version
CentOS Linux release 7.9.2009 (Core)
Plesk version and microupdate number
18.0.72
It seems nearly every Plesk server, and nearly every backup, displays this warning each time the backup is run.

Code:
Warning: Extension "Git"
Unable to back up extension. Error: Failed to exec backup_restore_helper: Exit code: 1: Failed to copy files storage to destination path. stderr: filemng: Cannot open destination file '/var/www/vhosts/example.com/.ssh/id_rsa.Z77a1q'
System error 13: Permission denied
stdout: filemng: Cannot open destination file '/var/www/vhosts/example.com/.ssh/id_rsa.Z77a1q'
System error 13: Permission denied

In those cases, I login to the shell of that domain user to review the ownership of $/.ssh

Code:
-bash-4.2$ ls -la
total 7224
drwx--x---. 12 myuser psaserv     268 Oct 27 12:21 .
drwxr-xr-x. 28 root     root       4096 Oct 27 12:21 ..
-rw-------.  1 myuser psacln      694 Sep  9 13:26 .bash_history
.....truncated....
drwxr-xr-x.  2 root     root         29 Sep  9 12:45 .ssh
drwxr-xr-x.  3 myuser psacln       65 Oct 10 00:24 .subversion
drwxr-xr-x.  5 myuser psacln      101 Sep  9 12:46 system
drwxrwxr-x.  4 myuser psacln       43 Sep  9 12:46 templates

If I change the ownership of .ssh/ from "root:root" to "myuser: psacln" - all is fixed.

Can this be made to a default permissions setting, server-wide?
 

Attachments

  • plesk-perm_2.jpg
    plesk-perm_2.jpg
    380.9 KB · Views: 3
  • plesk-perm_1.jpg
    plesk-perm_1.jpg
    123 KB · Views: 3
The default permission should be the useraccount:psacln. You can always run plesk's repair on the file system to repair the permissions. This can be done from the panel itself or running the following as root:

plesk repair fs
 
Back
Top