Question
Question
Bad gateway error caused by php-fpm on CEntos 8 / NGINX only on second server block
I have installed the whole LEMP stack sucessfully on my Centos 8 droplet, everything checks out. I have a DB, I am running php woth php-fpm, all is swell.
Except that I have created two new server blocks and there whenever I try to access a php file through a broswer, I get a 502 Bad Gateway error.
I have these configs for the server blocks:
server {
listen 443;
listen [::]:443;
root /usr/share/nginx/lilla.lordcase.dev;
location / {
index index.html index.htm index.php;
}
server_name lilla.lordcase.dev;
access_log /var/log/nginx/lilla.lordcase.dev.access.log;
error_log /var/log/nginx/lilla.lordcase.dev.error.log;
location ~ \.php$ {
include /etc/nginx/fastcgi_params;
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
}
ssl_certificate /etc/letsencrypt/live/lordcase.dev/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/lordcase.dev/privkey.pem; # managed by Certbot
}
The error in the log file is:
2020/07/08 19:33:02 [error] 571#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 176.63.18.177, server: lilla.lordcase.dev, request: “GET /info.php HTTP/1.1”, upstream: “fastcgi://127.0.0.1:9000”, host: “lilla.lordcase.dev”
I have restarted all services, and as I said, on the primary (original) server block php files are parsed perfectly. ANy ideas?
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.
×
I forgot to mention that the extra server blocks work well with non-php files, so html and txt is returned without any errors