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

Skeleton files chmod

D

dood

Guest
I've uploaded a skeleton file but the chmod is all wrong now. Can you preset the chmod for each file?

Apparently no one else has ever dealt with this issue, at least I couldn't find it.
 
ho dood ! :)

I had the same issue as you ...

I created a directory called "control" in the skeleton that I didnt it or its contents changed by the silly users.

Therefore I created a couple of system events

1. domain created
2. domain updated

and in those events put in

chmod root /var/www/vhosts/*/httpdocs/control -R

So each time it would go and make sure they were owned by root and therefore the user could not updated.

I will revisit these events as I am sure you can run them using <new_domain_name> instead of the "*".

regards

Andy @ teckna
 
I tried everything I could think of and never could get it the chmod to auto set for the skeleton files.

Even directly changing them from root in ssh would revert back to default chmod settings.

Thanks for the info, I'll have to look into it.
 
Back
Top