PHP-FPM and Nginx: 502 Bad Gateway

Answers of > PHP-FPM and Nginx: 502 Bad Gateway

PHP-FPM is not running,PHP-FPM isn’t w3coded bad nginx running,PHP-FPM is timing out,NGINX will return w3coded bad nginx a 502 Bad Gateway error if it can’t w3coded bad nginx successfully proxy a request to PHP-FPM, or if w3coded bad nginx PHP-FPM fails to respond. In this post, we’ll w3coded bad nginx examine some common causes of 502 errors in the w3coded bad nginx NGINX/PHP-FPM stack, and we’ll provide w3coded bad nginx guidance on where you can find information that w3coded bad nginx can help you resolve these errors.

127.0.0.1 - - [31/Jan/2020:18:30:55 +0000] "GET / HTTP/1.1" 502 182 "-" "curl/7.58.0"

2020/01/31 18:30:55 [crit] 13617#13617: *557 connect() to unix:/run/php/php7.2-fpm.sock failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.2-fpm.sock:", host: "localhost"

sudo ps aux | grep 'php'

root     29852  0.0  2.2 435484 22396 ?        Ssl  16:27   0:00 php-fpm: master process (/etc/php/7.2/fpm/php-fpm.conf)
www-data 29873  0.0  1.5 438112 15220 ?        Sl   16:27   0:00 php-fpm: pool www
www-data 29874  0.0  1.6 438112 16976 ?        Sl   16:27   0:00 php-fpm: pool www

sudo systemctl enable php7.2-fpm.service

Current topics : PHP-FPM and Nginx: 502 Bad Gateway

Newly Added Questions