• 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.

Migration Manager and cgi-bin permissions

qnet

Basic Pleskian
I am having a problem with migration manager when migrating domains from 10.x to 11.x. The problem is with the permissions
for the "cgi-bin" directory. After migration, the cgi-bin group is set to "psacln". It should be set to "psaserv". With it set to
"psacln" Apache says it can't get at ".htaccess" and Apache returns "Forbidden".

Is there a way to have Migration Manager set the group to "psaserv" for "cgi-bin" during migration?
 
Hi,

not that I know of.
But you could change the Groups like this:

# find /var/www/vhosts -name cgi-bin -gid `cat /etc/group | grep psacln | cut -d ":" -f3` -print0 | xargs chgrp psaserv

That should fix the issue for all wrong cgi-bin below /var/www/vhosts

Regards,
Kristian
 
Kristian, that is essentially what I do now. What I was hoping was Migration Manager would be fixed since it seems like it would be a rather trivial fix and the bug essentially breaks all migrated sites that use the cgi-bin directory.
 
Hi,

for it to be fixed, you will have to contact Plesk support.
I'm guessing they already know about this though.

Regards,
Kristian
 
Back
Top