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

Resolved Plesk website / NAS HA error reading

Erwan

Regular Pleskian
Server operating system version
Debian 11.7
Plesk version and microupdate number
18.0.54
Hi all,

We have a website that works well.
Storage space (server): /var/www/vhsosts/mydomain.com/production/

Wishing to assign another instance to the website, we mounted an NFS NAS with the same rights and copied the files:
- mv /var/www/vhsosts/mydomain.com/production/ to /var/www/vhsosts/mydomain.com/production.bck/ (for backup)
- create /var/www/vhsosts/mydomain.com/production/
- chown on the directory (for the same as production.bck): #chown ftpprod:psacln /var/www/vhsosts/mydomain.com/production/
Copy of thefiles:
- copy: #cp -aRf production.bck/* production
No problem.

But when i access to the website, i have an 500 error.
=> mod_fcgid: read data timeout in 45 seconds

Apache does not seem to be able to read the files even though the rights have been carried over identically.
The basic rights of the NAS are indeed read/write.

Do you have an idea of the problem?

Erwan
 
Please make sure that the pathis not /var/www/vhsosts, but /var/www/vhosts.

For details on the 500 error, please check the error_log file of the corresponding website. Mostly you'll find more details on the cause of the error.
 
Thank you Peter.
The path is good.

It works now by increasing the timeout values enormously.
The problem seems to come from the hosting, very slow.

Thank you.
 
Back
Top