• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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