medsha

You are not the only one with this problem. I have the same problem and it appeared a week ago.

You guys are not the only one. I have the same issue. ?? I hope this get fixed soon. Is there a possible work-around?

Hey Rahul,

This indeed finally solved the problem. I took care of phpmyadmin and the problem is finally solved!

This is the current code I use that allows my website to use proper permalinks:

server {
        server_name 3rabgamer.net;

        root /var/www;
        index index.php;

        location / {
                try_files $uri $uri/ /index.php?$args;
        }

        location ~ \.php$ {
		include 	/etc/nginx/fastcgi_params;
		fastcgi_pass  	127.0.0.1:9000;
		fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        }

	location /phpmyadmin {
               root /usr/share/;
               index index.php index.html index.htm;
               location ~ ^/phpmyadmin/(.+\.php)$ {
                       try_files $uri =404;
                       root /usr/share/;
                       fastcgi_pass 127.0.0.1:9000;
                       fastcgi_index index.php;
                       fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
                       include /etc/nginx/fastcgi_params;
               }
               location ~* ^/phpmyadmin/(.+\.(jpg|jpeg|gif|css|png|js|ico|html|xml|txt))$ {
                       root /usr/share/;
               }
        }
        location /phpMyAdmin {
               rewrite ^/* /phpmyadmin last;
        }

}

This is the code in the /sites-available/default file. Thanks for your help guys.

@rahul286

I tried your code and it doesn’t work either.

@pothi

I am trying to find anything special in the logs, but I can’t find anything. Do you have any suggestions what to look for? Maybe I just didn’t pay enough attention in finding the culprit in the error logs.
—————————————-

I do have to tell you that the data is not in my nginx.conf – it’s in the default file.

I’ll post the content again of what I exactly have.

nginx.conf

user www-data;
worker_processes  1;

error_log  /var/log/nginx/error.log;
pid        /var/run/nginx.pid;

events {
    worker_connections  1024;
    # multi_accept on;
}

http {
    include       /etc/nginx/mime.types;

    access_log	/var/log/nginx/access.log;
    error_log /var/log/nginx/error.log info;

    sendfile        on;
    #tcp_nopush     on;

    #keepalive_timeout  0;
    keepalive_timeout  65;
    tcp_nodelay        on;

    gzip  on;
    gzip_disable "MSIE [1-6]\.(?!.*SV1)";

    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;
}

File default located in /etc/nginx/sites-enabled/

# You may add here your
# server {
#	...
# }
# statements for each of your virtual hosts

server {

	listen   80; ## listen for ipv4
	listen   [::]:80 default ipv6only=on; ## listen for ipv6

	server_name  3rabgamer.net;
	server_name_in_redirect off;

fastcgi_buffer_size             32k;
fastcgi_buffers                 16 32k;
fastcgi_busy_buffers_size       64k;
fastcgi_temp_file_write_size    64k;

	location / {
		root   /var/www;
		index  index.html index.htm index.php;
	}

	# redirect server error pages to the static page /50x.html
	#
	#error_page   500 502 503 504  /50x.html;
	#location = /50x.html {
	#	root   /var/www/nginx-default;
	#}

	# proxy the PHP scripts to Apache listening on 127.0.0.1:80
	#
	#location ~ \.php$ {
		#proxy_pass   https://127.0.0.1;
	#}

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

	location ~ \.php$ {
		root 		/var/www;
		include 	/etc/nginx/fastcgi_params;
		fastcgi_pass  	127.0.0.1:9000;
		fastcgi_index 	index.php;
		try_files $uri @wordpress;

		fastcgi_param  	SCRIPT_FILENAME /var/www/$fastcgi_script_name;
	}

	location /phpmyadmin {
               root /usr/share/;
               index index.php index.html index.htm;
               location ~ ^/phpmyadmin/(.+\.php)$ {
                       try_files $uri =404;
                       root /usr/share/;
                       fastcgi_pass 127.0.0.1:9000;
                       fastcgi_index index.php;
                       fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
                       include /etc/nginx/fastcgi_params;
               }
               location ~* ^/phpmyadmin/(.+\.(jpg|jpeg|gif|css|png|js|ico|html|xml|txt))$ {
                       root /usr/share/;
               }
        }
        location /phpMyAdmin {
               rewrite ^/* /phpmyadmin last;
        }

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

Maybe that can clear something up now. Thanks for your time, guys.

@pothi Kalimuthu

By following your suggestion only the homepage becomes reachable. If you try to access the admin panel or any random post/page, you will be redirected to the homepage again.

@jan Dembowski

Nope, that didn’t do the trick.

When I add the suggested command line above the location ~ \.php$ I get the error

Restarting nginx: [emerg]: duplicate location "/" in /etc/nginx/sites-enabled/default:41
configuration file /etc/nginx/nginx.conf test failed

After that happened, I tried to implement

try_files $uri $uri/ /index.php; into location ~ \.php$ itself
I did disable the try_files $uri @wordpress; part in the code when I tried your code. ??

It resulted into 404 errors when I turn on custom permalinks.

Any other suggestions maybe?

A work around might be adding the “Read More” code before the post itself.

Make sure to choose summary at the settings page if you are going to do that. ??

You could start by going to the settings section in your admin-panel. Once you are there, find the “Reading” section at the settings-menu left on your screen. Once you have clicked “Reading” you will get to see:

For each article in a feed, show: Full text or Summary. Choose Full Text and click save changes.

Did you only change the code in the theme itself? If so, then you should copy the theme folder to the other server and paste it right there (WP-content/themes). And do the same to the plugins if you are using any.