Wordpress How to Enable FCGI Cache on WordPress ?

you need to create it yourself - from guide

---

 

if following the guide at Nginx Wordpress Configuration - CentminMod.com LEMP Nginx web stack for CentOS make sure you're using right php include file and that it's only one in use for each web app/script.
phpwpcache.conf enabled with php.conf disabled/commented out

Code (Text):

include /usr/local/nginx/conf/phpwpcache.conf;
#include /usr/local/nginx/conf/php.conf;

So if you have multiple scripts installed - you may have wordpress directory/script locations use phpwpcache.conf include file. If you have non-wordpress script, you'd use php.conf include. And ensure you don't have
location ~ \.php$ { context in same nginx vhost if they are used by other web app/scripts as you'll have php requests matched to unintended web apps within same nginx vhost.

If unsure, create a test dummy single wordpress site with no other script and test fastcgi_cache wordpress config first to ensure that config is working before trying to mix with other scripts on same site domain name.

 

check your nginx access/error logs and php-fpm error logs for clues

 

Are you using Wordpress permalinks or Nginx rewrite rules which have urls/links with .html extensions ?

Centmin Mod default static files include file at /usr/local/nginx/conf/staticfiles.conf handles .html files via Nginx. But by using wordpress with .html extensions you tell Nginx not to serve .html files and serve via PHP-FPM (not ideal as it reduces performance if you use permalinks with .html extensions and thus use PHP-FPM to server .html files)

If you must use .html extension permalinks, you need to comment out the .html location context from /usr/local/nginx/conf/staticfiles.conf and restart Nginx server as illustrated below with hash # in front

Code:

    location ~* \.(3gp|gif|jpg|jpeg|png|ico|wmv|avi|asf|asx|mpg|mpeg|mp4|pls|mp3|mid|wav|swf|flv|exe|zip|tar|rar|gz|tgz|bz2|uha|7z|doc|docx|xls|xlsx|pdf|iso)$ {
        gzip_static off;
        #add_header Pragma public;
        add_header Cache-Control "public, must-revalidate, proxy-revalidate";
        access_log off;
        expires 30d;
        break;
        }

    location ~* \.(js)$ {
        #add_header Pragma public;
        add_header Cache-Control "public, must-revalidate, proxy-revalidate";
        access_log off;
        expires 30d;
        break;
        }

    location ~* \.(css)$ {
        #add_header Pragma public;
        add_header Cache-Control "public, must-revalidate, proxy-revalidate";
        access_log off;
        expires 30d;
        break;
        }

    #location ~* \.(html|htm|txt)$ {
        #add_header Pragma public;
        #add_header Cache-Control "public, must-revalidate, proxy-revalidate";
        #access_log off;
        #expires 1d;
       # break;
       # }

    location ~* \.(eot|svg|ttf|woff)$ {
        #add_header Pragma public;
        add_header Cache-Control "public, must-revalidate, proxy-revalidate";
        access_log off;
        expires 30d;
        break;
        }

You can also use SSH command shortcut below to launch nano linux text editor and edit file /usr/local/nginx/conf/staticfiles.conf

Code:

statfilesinc

 

When you create a new nginx vhost domain via centmin.sh menu option 2 or menu option 22 or via /usr/bin/nv cli command line, you will create the Nginx vhost files and directories. You will get an outputted the path location where it will create the domain name's vhost conf file named newdomain.com.conf (and newdomain.com.ssl.conf if you selected yes to self signed SSL)

• Nginx vhost conf path will be at /usr/local/nginx/conf/conf.d/newdomain.com.conf
• Nginx HTTP/2 SSL vhost conf path will be at /usr/local/nginx/conf/conf.d/newdomain.com.ssl.conf
• Nginx Self-Signed SSL Certificate Directory at /usr/local/nginx/conf/ssl/newdomain.com
• Vhost public web root will be at /home/nginx/domains/newdomain.com/public
• Vhost log directory will be at /home/nginx/domains/newdomain.com/log

Please post the contents of /usr/local/nginx/conf/conf.d/newdomain.com.conf and if applicable /usr/local/nginx/conf/conf.d/newdomain.com.ssl.conf wrapped in CODE tags (outlined at How to use forum BBCODE code tags)

 

I re-read Nginx Wordpress Configuration - CentminMod.com LEMP Nginx web stack for CentOS and that example is made for wordpress install at /wp so permalinks try_files directive is in /wp location context and not web root /. So make sure you aren't doing that if wordpress is installed in web root at / and have try_files in web root / location context instead