Facebook
Twitter-
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 upload the site made with tailwindcss to hosting
- Thread starter ebunebus
- Start date
-
- Tags
- tailwindcss
There is a wide range of possible causes. One frequent cause is a wrong file ownership.
httpdocs must be owned as follows:
The files and directories inside httpdocs must be owned as follows:
Then it is possible that file or directory permissions are insufficient. They ought to be:
httpdocs: 0750
Inside httpdocs: At least 0644 for public files.
There can be several other reasons. I suggest to look into /log to check the error log file contents why a 403 is thrown. It could also be a result of a ModSecurity block against certain URLs.
httpdocs must be owned as follows:
Code:
<subscription user name>:psaservThe files and directories inside httpdocs must be owned as follows:
Code:
<subscription user name>:psaclnThen it is possible that file or directory permissions are insufficient. They ought to be:
httpdocs: 0750
Inside httpdocs: At least 0644 for public files.
There can be several other reasons. I suggest to look into /log to check the error log file contents why a 403 is thrown. It could also be a result of a ModSecurity block against certain URLs.
