Earlier today, I updated packages on one of my servers. One of those packages was an update to php5-fpm, which seems to have broken my ability to utilize unix:/var/run/php5-fpm.sock
.
Disclaimer: I only recently started using Linux; I don't fully understand what's going on here.
I've reviewed lots of other questions but have no been able to find answer to my issue, which is that I get a 502 Bad Gateway error if I try to use php5-fpm.sock
instead of passing to 127.0.0.1:9000
.
Here are some details that seem relevant based off of other questions:
- My
php5-fpm
process is running. - My
/etc/php5/fpm/pool.d/www.conf
file haslisten = /var/run/php5-fpm.sock
- My server block has
fastcgi_pass = unix:/var/run/php5-fpm.sock
php5-fpm.sock
does exist in/var/run/
.
When upgrading php5-fpm, it asked me if I wanted to overwrite my www.conf. I checked the diff and the only change between the maintainer's file and mine was that the maintainer's had listen = 127.0.0.1:9000
set as the default.
After selecting to overwrite it and finishing upgrading php5-fpm, I opened up /etc/php5/fpm/pool.d/www.conf
and changed listen to listen = /var/run/php5-fpm.sock
, like it had been set beforehand. I then restarted php5-fpm, and then nginx, in that order.
I now get a 502 when visiting the domain and am at a complete loss. If I change listen
in www.conf and fastcgi_pass
in my host file to 127.0.0.1:9000
, everything works perfectly. I'm using Ubuntu 12.04LTS, if that matters.
Your help is greatly appreciated.