I’m unable to figure out if the default Cache Key Regex is the proper regex to use with my Nginx fastcgi_cache settings. In the plugins default settings the Cache Key Regex is:

/^KEY:\s+https?(?:GET)?([^\/]+)(\/[^\s]*)/m

In MY nginx.conf. my fastcgi_cache_key line looks like this:

fastcgi_cache_key "$scheme$request_method$host$request_uri";

Is it possible to preload with the default Regex key being used in this plugin, or do I need a different REGEX? If I need a different REGEX, then what should I be using?

Thanks for any and all help

Under “System Checks” section, I see “Permission Isolation (Optional)?Not Isolated”. What exactly is this and how does it work? I would like to secure my cached files permissions as much as possible. Is this setting relevant? How does it work?

Hi all, this plugin is wonderful thank you
however i’m unable to configure a proper Cache Key Regex since i use a custom fastcgi_cache_key can you help me ?
Is it even possible to get preload to work with custom key?

my fastcgi_cache_key is $scheme$request_method$host$device$request_uri
My keys looks like this
KEY: httpsGETevoarmg.xxxxxx.netDESKTOP/
KEY: httpsGETevoarmg.xxxxxx.netMOBILE/

I know we discussed not supporting finding the regex for people but I notice something odd.

I reset all the cache setting and was able to see a cache file under all the defaults. However, as discussed, my custom key is: $scheme$request_method$host$request_uri$mobiles_device_type

And I notice in the Status page there is this section:
FastCGI Cache Keys
Found Unsupported

Lists this as a specific unsupported type over and over again:

$scheme$request_method$host$request_uri$mobile_device_type

Even though, for this test, my key is verified as the default:

    fastcgi_cache_key "$scheme$request_method$host$request_uri";

So something is odd….

Adding the plugin and attempting to activate it and I am presented with the following error: “The plugin does not have a valid header.”

after the update i started getting this error when i try to create or update a post “Not a valid JSON response”

after disabling the plugin everything went to normal as usual

everything seems to be working except for two things:

• Pages In Cache Count is stuck on ”?Not Determined”
• advanced tab gives me this error “
• ERROR CACHE KEY: Nginx cache key format is not suitable for the plugin. Refer to the Help tab for guidance.”

This plugin is amazing and really needed by the community. There are a few things that could be improved.

• Ability to use complicated path names. I like to name folders for the site due to subdomains, but /var/cache/npp/subdomain.sitename/ folder is invalid and throw an incorrect error about root folders.
• The Key format is very restrictive. I like to have separate caches for mobile and desktop so my key setup is like this:
  fastcgi_cache_key “$scheme$request_method$host$mobile_device_type$request_uri$is_args$args”

• I assume the shell_exec requirement is based on needing that other script setup in your setup for users with separate php and nginx users. For those of us who don’t need that workaround we should be able to re-disable shell_exec. Unless there is another reason you need it?

Overall a great plugin!

I didn’t want to have another script to setup and maintain so I tested using bindfs (not bind, get it with apt-get bindfs) and it works perfectly.
sudo bindfs –force-user=”user_name” –force-group=”webserver-group” –perms=u=rwx:g=rwx:o=rx “orig fastcgi cache path” “new folder int he var/cache/ directory”

Add it to fstab and you have a persistent connection.

• This topic was modified 4 months ago by coldrealms65. Reason: clarity