The /tmp problem is caused by the directory /tmp/nginx_client filling up. We set up a cron job to clean that dir only as cleaning the whole of /tmp could cause problem, eg the mysql.sock files resides there. So we do:
0 */4 * * * /usr/sbin/tmpwatch -am 4 /tmp/nginx_client

Yeah, I assumed that would be solution, but because this issue is so often, it would be great for all new /noob users to cron job solution is added up on installation of nginxcp.

And what’s with upload problem ?
In some last post of yours, some guy commented that he also has problem with “Uber-Uploader” (or so…), so is there a solution?
I also received email from one of my clients saying that his upload (some simple php…) isn’t working, and last file he successfully uploaded was few hours before I installed nginx, and again script works after uninstalling it…

A client added a subdomain in his cpanel today, and it stopped nginx from working, so that no sites on the server were being served. I tried restarting nginx, rebuilding vhosts, but had to uninstall and then re-install to get it working again.

The error was:

Restarting nginx daemon: nginxnginx: [emerg]: no host in “:80” of the “listen” directive in /etc/nginx/vhosts/subdomain.domain.org:3