• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

wrong max_execution_time default value

exit15

Basic Pleskian
FYI - Using only the Plesk Interface! I think there is a bug with the default php max_execution_time within a subscription. It is set to 60 sec, but if looking at the actual phpinfo() you will find that the value is in fact 30 sec.

I went nuts about a timeout error only to find that the values in the php setting interface within a subscription are not the same as the default settings. Changing to a higher number 240 sec or so, does take hold. Type your value, don't use the pull down selector.

Related: the php timeout can manifest itself as "nginx 504 error: Connection timed out", or "fcgi timeout", or as "proxy timeout" errors - when it fact it is a simple php timeout error. This article http://kb.odin.com/en/120210 offers the wrong solution in my opinion. nginx is not the problem...
 
Back
Top