Thanks to all, adding this > try_files $uri $uri/ /index.php?$args; to sites available worked for me.

I had the same issue after I installed the nginx on my server. The error was caused by some bad statements in my conf file. I just had to add this to the conf file:

include fastcgi.conf;
fastcgi_intercept_errors on;
fastcgi_index index.php;

I used this tutorial, check maybe it will help.

Please am having problem with my debian nginx php configuration. here’s my conf file

Am hosting django in my main domain and i want to host php app called portal by typing domain/portal

but am getting 404 error

server { listen 80; listen [::]:80; server_name xxxxxxx;

location = /favicon.ico { access_log off; log_not_found off; }
location /static/ {
    root /home/tpconnect/myproject;
}

location / {
    include proxy_params;
    proxy_pass http://unix:/home/tpconnect/myproject/myproject.sock;
}
    location ~ /portal/.*\.php$ {
        root /var/www/html/portal;
        index index.php index.html index.htm;
        set $php_root /var/www/html/portal;

        try_files $uri =404;
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
         fastcgi_pass   127.0.0.1:9000;
fastcgi_index  index.php;
fastcgi_param  SCRIPT_FILENAME  $php_root$fastcgi_script_name;
include /etc/nginx/fastcgi_params;
}

location /portal {
        root /var/www/html/portal;
        index index.php index.html index.htm;
        set $php_root /var/www/html/portal;

        fastcgi_split_path_info ^(.+\.php)(/.+)$;
         fastcgi_pass   127.0.0.1:9000;
fastcgi_index  index.php;
fastcgi_param  SCRIPT_FILENAME  $php_root$fastcgi_script_name;
include /etc/nginx/fastcgi_params;

        try_files $uri $uri/ /portal/index.php;
}

}

So I reinstalled everything and setup a new server but still getting the same error below is the error.log and etc/nginx/sites-available/default. @xMudrii @jcolyer

error.log

2017/08/11 21:32:45 [notice] 2139#2139: signal process started 2017/08/11 22:03:34 [notice] 23682#23682: signal process started

etc/nginx/sites-available/default.

You should look at the following URL’s in order to grasp a solid understanding

of Nginx configuration files in order to fully unleash the power of Nginx.

http://wiki.nginx.org/Pitfalls

http://wiki.nginx.org/QuickStart

http://wiki.nginx.org/Configuration

Generally, you will want to move this file somewhere, and start with a clean

file but keep this around for reference. Or just disable in sites-enabled.

Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.

Default server configuration

server { listen 80 default_server; listen [::]:80 default_server;

# SSL configuration
#
# listen 443 ssl default_server;
# listen [::]:443 ssl default_server;
#
# Note: You should disable gzip for SSL traffic.
# See: https://bugs.debian.org/773332
#
# Read up on ssl_ciphers to ensure a secure configuration.
# See: https://bugs.debian.org/765782
#
# Self signed certs generated by the ssl-cert package
# Don't use them in a production server!
#
# include snippets/snakeoil.conf;

root /var/www/html;

# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;

server_name _;

location / {
	# First attempt to serve request as file, then
	# as directory, then fall back to displaying a 404.
	#try_files $uri $uri/ =404;
             try_files $uri $uri/ /index.php?$args;
}

    # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000

     location ~ \.php$ {
     include snippets/fastcgi-php.conf;
     fastcgi_pass unix:/run/php/php7.0-fpm.sock;
    }

# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
#	deny all;
#}

}

Virtual Host configuration for example.com

You can move that to a different file under sites-available/ and symlink that

to sites-enabled/ to enable it.

#server {

listen 80;

listen [::]:80;

server_name example.com;

root /var/www/example.com;

index index.html;

location / {

try_files $uri $uri/ =404;

}

#}

I installed Nginx Helper WP Plugin as well and I see some error related to the plugin as well So I m going to setup a fresh server and install everything again and will then update this page to get some help if still facing issue which I think I will. Thank you @jcolyer and @xMudrii, Thank you for your precious time.

Greetings!

Sounds like the redirects needed for WordPress are not present in the Nginx configuration. This would explain why changing the permalinks resulted in those nasty 404s. Generally you can find the exact coding needed at this WordPress codex page.