One of my DO servers that we are using as a test environment works well most of the time, but at seemingly random times, the server responds with a “502 Bad Gateway” error.
In the nginx logs, I can see the following error message: 2019/06/27 13:46:15 [error] 1013#1013: *19539 connect() to unix:/var/run/php/php7.3-fpm.sock failed (111: Connection refused) while connecting to upstream, client: 117.204.xxx.xxx, server: subdomain1.sometestdomain123.xyz, request: “POST /client/communicationNotifyAlerts HTTP/2.0”, upstream: “fastcgi://unix:/var/run/php/php7.3-fpm.sock:”, host: “subdomain1.sometestdomain123.xyz”, referrer: “https://subdomain1.sometestdomain123.xyz/client/api1”
I’m guessing this could be happening after updating our php code but not performing a restart? Could this be caused by something else.
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.
It looks like that your PHP FPM service is crashing. If you see that 502 error just try starting PHP FPM and it should start working as normal.
I would recommend checking your syslogs to further investigate the problem, maybe your server is out of RAM and that’s why PHP FPM gets killed.
Here is a link to an answer on how to troubleshoot common Nginx problems:
And here is also a quick video demo on how to do that as well:
Hope that this helps! Bobby