Report this

What is the reason for this report?

Nginx: upstream prematurely closed connection while reading response header from upstream

Posted on December 12, 2013
hn

By hn

Hello,

I followed tutorial(https://www.digitalocean.com/community/articles/how-to-install-rails-and-nginx-with-passenger-on-ubuntu) to set up my Rails App(nginx 1.4.4, passenger 4.0 and mysql) on DigitalOcean’s 512MB RAM and 20GB Disk server. I got below error once I started Nginx and visit my App.

– I checked /opt/nginx/logs/error.log, which shows “1 upstream prematurely closed connection while reading response header from upstream” at the latest line.

Is this a performance issue on DigitalOcean’s 512MB RAM server? anyone know how to fix this? Thanks!



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hello, <br>I followed tutorial(https://www.digitalocean.com/community/articles/how-to-install-rails-and-nginx-with-passenger-on-ubuntu) <br>I got upstream timed out (110: Connection timed out) while reading response header from upstream in error.log file

@Kamal Nasser, <br>Could you please tell how can i check passenger’s error logs?

just restart php-fpm, it worked for me!

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.