I'm presently focusing on my Wordpress blog, that is located on the VPS.Internet VPS with Nginx as front-end to Apache for everyone static files, while Apache takes proper care of the PHP in FastCGI. This appears to become working great, however have not yet handled to possess Nginx serve Wordpress-SuperCache files too, which I'd like for optimum performance (I'm not likely to completely replace Apache with Nginx at this time because I have got a Virtualmin license and it doesn't support Nginx). I've attempted lots of rules found in some places but ultimately none labored for me personally or I'm missing something. If Apache is stopped, actually, I'm able to get images, stylesheets and javascript shipped towards the browser by Nginx directly. But when I attempt to surf your blog (with pages cached without a doubt by Wordpress-SuperCache) with Apache stopped, all I recieve from Nginx is really a "502 bad gateway". Any ideas could be greatly appreciated. Thank you ahead of time.

It appears silly to operate Nginx through Apache.

Setup Nginx for everyone in the php and dynamic pages itself you'll also find a significantly faster service and will not possess the problem where apache dies leaving your webserver(Nginx) hanging.

In case your admin panel does not support this, you most likely should simply be using apache to begin with. Either do either, both is simply requesting problems.

Nginx are designed for your fastCGI. Bundled up with Nginx, generally, all Apache does is set you back assets.

Regarding Wordpress Super Cache, should you produce a new file and paste this, it'll provide you with both might, while we are about this, FURLs...

# if the requested file exists, return it immediately
if (-f $request_filename) {

set $supercache_file '';
set $supercache_uri $request_uri;

if ($request_method = POST) {
set $supercache_uri '';

# Using pretty permalinks, so bypass the cache for any query string
if ($query_string) {
set $supercache_uri '';

if ($http_cookie ~* "comment_author_|wordpress|wp-postpass_" ) {
set $supercache_uri '';

# if we haven't bypassed the cache, specify our supercache file
if ($supercache_uri ~ ^(.+)$) {
set $supercache_file /wp-content/cache/supercache/$http_host/$1index.html;

# only rewrite to the supercache file if it actually exists
if (-f $document_root$supercache_file) {
rewrite ^(.*)$ $supercache_file break;

# all other requests go to Wordpress
if (!-e $request_filename) {
rewrite . /index.php last;

Now, goto your virtual host file, or nginx.conf should you bundle your sites, and give a line like ..

# Wordpress WP Super Cache plugin and permalinks.
include /usr/local/nginx/conf/wordpress_params.super_cache;

.. where wordpress_params.super_cache is exactly what you known as the file we produced, and given a path in accordance with that I have proven.

Then restart Nginx and switch on Wordpress Super Cache wordpress plugin and, for that pretty links, give a permalink structure.

Truth is, there is lots to understand going to obtain the Nginx install right, particularly with WordPress and also to configure fastCGI. If you want, this is an excellent start for you personally...

.. Setup WordPress on NGINX (FURLs & Cache) - VPS Bible Pt 13

Re. Virtualmin .. I realize you'll need a Clubpenguin, but the fact is, the resource price is more than the price of the program .. and it also takes way longer to complete stuff having a Clubpenguin.

I am presently posting a 21 part VPS Admin series which addresses the possible lack of an Nginx Clubpenguin .. which will be all that's necessary, frankly.

Given one or two weeks, I challenge you to definitely let me know it's faster or else better to utilize a Clubpenguin :)