Nginx Fastcgi 502 Time Out Recurring

Posted August 10, 2017 4.6k views
2017/08/10 19:41:42 [error] 2428#2428: *55 FastCGI sent in stderr: "PHP message: PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 72 bytes) in /home/forge//vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/GuardsAttributes.php on line 188" while reading response header from upstream, client:, server: XX, request: "GET /listOrders HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php5.6-fpm.sock:", host: "XXX", referrer: ""
2017/08/10 19:42:18 [error] 2428#2428: *24 recv() failed (104: Connection reset by peer) while reading response header from upstream, client:, server:XXX, request: "GET /fetchData HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php5.6-fpm.sock:", host: "XXX"

The site works but it gives a timeout error (502 Bad Gateway) When im trying to fetch orders from an API.
I have tried to change fastcgi pass to 127.x.x.x already. Changed the limits on several timeout .ini files.

Anyone can help me?

1 comment

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.

Submit an Answer
1 answer

Hey there,

This appears to be directly impacted by the application your web server is trying to serve. We have a community article that can help provide guidance on general web server troubleshooting:

If you use an application manager or proxy configuration (php-fpm, passenger, gunicorn/unicorn, T

In your particular case, your application (running via PHP) is hitting resource contention, causing issues in rendering the content. You can tell by this message from your errors:

Allowed memory size of 536870912 bytes exhausted

Basically, you need to either optimize the application to need less memory, allow the application to utilize more memory, or upgrade the droplet to have more usable memory.

by Justin Ellingwood
Everybody runs into issues with their website at one point or another. This guide will help you troubleshoot some common issues and get your site running again.