I spent a couple of hours yesterday trying to debug an issue that made me hit my head against the wall while it lasted.
I run multiple instances of WordPress, and with it, comes a nice little editor bundled called TinyMCE. But on my main WordPress installation (this very blog, dear reader, where you are reading this from), TinyMCE wouldn’t come up, it wouldn’t render properly on the browser, it didn’t matter if it was my main browser, Chrome, or Firefox, Safari, cached, uncached, it was just broken. Since I hadn’t have the time to go through this issue before, I was using a different editor installed as a plugin. LAME. And coward.
Anyway, I found out that one of the scripts
After a lot of googling I ended up reading this blog post (in Portuguese), suggesting to make sure the file permissions for both the client_body_temp and fastcgi_temp directories allowed the user running nginx (www-data in my case) to write in them. Apparently large scripts would start writing to disk on them temporarily while processing the shit. Of course, you wouldn’t have this issue if you are running an nginx from your operating system package manager (like Debian’s), but this might very well happen when you are running a custom nginx with separate modules and all sorts of crap on top of it:
chown www-data:www-data -R /usr/local/nginx/fastcgi_temp/; chmod -R 777 /usr/local/nginx/fastcgi_temp/; chown www-data:www-data -R /usr/local/nginx/client_body_temp/; chmod -R 777 /usr/local/nginx/client_body_temp/;
Obrigado, republicavirtual.com.br :-)