• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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