• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue PHP critical error on Centos not on Debian, same config

MicheleP

Basic Pleskian
Hi
I've a php soap server, on a server with Centos
On this I need to parse the response with a function Parse_function
ob_start("Parse_function");
whatever php version or apache/ngnix application, get always the same error:
23893#0: *320074 upstream prematurely closed FastCGI request while reading upstream

And there is no problem on the code, also for a simple response with "Hallo" (no elaborations, no long operations that could require a different timeout, no query, no nothing...) the server breaks

But (my last test) the same solution on a server with Debian works great! As it is suppose to do.
Why??
There are differences between the two server versions? There is a solution?
It is important
Thanks
 
Hi, yes, then the error change in this:
31871#0: *366111 upstream prematurely closed connection while reading upstream
 
Please try to increase the timeouts for nginx and test again:
Code:
proxy_connect_timeout 180s;
proxy_send_timeout 180s;
proxy_read_timeout 180s;
fastcgi_send_timeout 180s;
fastcgi_read_timeout 180s;
 
in Apache & nginx Settings, right?
done
same error
19018#0: *367849 upstream prematurely closed connection while reading upstream
 
done, same error
19018#0: *368941 upstream prematurely closed connection while reading upstream

The problem is not only on this server, I've tried another server with centos, same thing
 
However I think it's not a timeout problem, there are no operations or scripts that could go in timeout, seems to me there is a problem with php on centos with the ob_start function
 
Back
Top