Hey @jesin , I did nginx -t before changing. I received

nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied)
2015/05/22 11:47:56 [warn] 24811#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:1
2015/05/22 11:47:56 [emerg] 24811#0: open() "/etc/nginx/fastcgi.conf" failed (2: No such file or directory) in /etc/nginx/sites-enabled/wordpress:46
nginx: configuration file /etc/nginx/nginx.conf test failed

And restarted nginx after changing, problems seems to have gone but other files like css, js, dashicons are not opening.
Screenshot: http://i.imgur.com/tFDV3d4.png

Screenshot: http://i.imgur.com/f58OD58.png

@jesin , sorted the problem. The line
location ~ /wp-includes { internal; }
code was causing problem. Thanks for your help.

Do you know does wordpress processes urls? I mean how does they end with .php as I have seen all wordpress nginx configs contain this line

location ~ \.php$ {

@gts13 Glad you got it working!

The following line does the trick:

try_files $uri $uri/ /index.php?q=$uri&$args;

So if http://example.com/hello-world is accessed, Nginx will check:

• if a file named “hello-world” exists, $uri
• if it doesn’t it will check if a directory named “hello-world” exists, $uri/
• if that too doesn’t exist, it will process the request via /index.php

Now the request will match location ~ \.php$ { which will pass it to the PHP-FPM socket file - unix:/var/run/php5-fpm.sock

This is how permalinks work.