This site uses cookies to deliver our services and to show you relevant ads and job listings.
By using our site, you acknowledge that you have read and understand our Cookie Policy, Privacy Policy, and our Terms of Service.
Your use of Stack Overflow’s Products and Services, including the Stack Overflow Network, is subject to these policies and terms.

Join us in building a kind, collaborative learning community via our updated
Code of Conduct.

Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

While this post discusses a similar setup to mine serving blank pages occasionally after having made a successful installation, I am unable to serve anything but blank pages. There are no errors present in /var/log/nginx/error.log, /var/log/php-fpm.log or /var/log/nginx/us/sharonrhodes/blog/error.log.

Unfortunately, I've fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; defined right at the top of /etc/nginx/conf/fastcgi.conf. I will edit the original post to reflect this.
– troutwineJan 18 '11 at 16:29

3

You include the file fastcgi_params, not fastcgi.conf. My answer is still valid.
– Martin FjordvaldJan 18 '11 at 18:44

This one just bit me- and it was totally my fault. I wanted to share what fixed me. In my case, the index.php wasn't loading (blank page) but wp-admin worked.

I have a custom theme and I recently migrated from a shared hosting account to a VPS. I did an rsync and my theme (/srv/blog.clifton.io/wp-content/themes/theme-here) is a symlink. This symlink broke of course, since it was using the path from my previous hosting account.