• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Issue recv() failed (104: Connection reset by peer) while reading response header from upstream

doubledeckcafe

New Pleskian
Hi we are getting this error a couple of times since we moved our client's website to a new server.

-----------------------------------------------------------------------------------------------------------
Source:
nginx error

Message:
11335#0: *5300222 recv() failed (104: Connection reset by peer) while reading response header from upstream ngi
-----------------------------------------------------------------------------------------------------------

I would like to know what is exactly happening and what we can do to prevent this error.

For your information the PHP settings are:
-------------------------------------------------------------------------------------------------------------
PHP version : 5.6.30 run PHP as FPM application served by nginx
memory limit 128M
max_execution_time 60 (It was 30 this morning but since this error we have changed to 60)
max_input_time : 60
pos_max_size : 8M
upload_max_filesize 2M
opcache.enable on
-----------------------------------------------------------------------------------------------------------

Thanks in advance
 
Please check the Apache error_log file at the same time when the error is recorded in the nginx log file. There should be a PHP error logged. The most likely problem is that a PHP script does not produce any output, so that the connection to the backend times out. The second likely reason is that 127.0.0.1 and the public IPv4 address were not whitelisted in the Plesk Fail2Ban configuration, so that randomly an IP block for localhost or the server's own IPv4 is triggered.
 
Back
Top