Note that there are some explanatory texts on larger screens.

plurals
  1. PONginx with PHP5-FPM -- .php files giving blank screens
    text
    copied!<p>I'm banging my head against the wall trying to get nginx up and running with php5-fpm. I felt that it was a small detail I was overlooking, so I took a break and came back to it a few days later. Been messing with it for another few hours tonight to no avail.</p> <p>Anyways, here is the issue: I have nginx up and running. It appears to be serving out web pages properly. for example, the base website of <a href="http://www.shidenadvanced.com" rel="nofollow">http://www.shidenadvanced.com</a> serves up just fine. However, the php test I have, located at <a href="http://www.shidenadvanced.com/test.php" rel="nofollow">http://www.shidenadvanced.com/test.php</a> is coming back as blank. Previously it was coming back as a 502 Bad Gateway.</p> <p>Through my research I was lead to understand that meant it could not properly route it through the php-fpm. Not 100% on that.</p> <p>This is my /sites-available/config:</p> <pre><code>server { server_name www.shidenadvanced.com shidenadvanced.com; access_log /srv/sites/shidenadvanced/logs/access.log; error_log /srv/sites/shidenadvanced/logs/error.log; root /srv/sites/shidenadvanced/www; index index.php index.html index.htm; location / { try_files $uri $uri/ /index.html; } #location ~ \.php$ { # try_files $uri =404; # include /etc/nginx/fastcgi_params; # fastcgi_pass unix:/var/run/php-fpm5.sock; # fastcgi_index index.php; # fastcgi_param SCRIPT_FILENAME /srv/sites/shidenadvanced/www$fastcgi_script_name; #} location ~ \.php$ { try_files $uri =404; fastcgi_split_path_info ^(.+\.php)(/.+)$; fastcgi_pass unix:/var/run/php5-fpm.sock; fastcgi_index index.php; include fastcgi_params; } location ~ /\.ht { deny all; } } </code></pre> <p>Outside of this I have left most of the settings alone. Not entirely sure what's going on. Can anyone shed some light?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload