You will see output like below: Filesystem Size Used Avail Use% Mounted on To verify it, run command df -h /var/run. Its generally 20% of your total RAM size.
![404 not found nginx 1.4 6 ubuntu 404 not found nginx 1.4 6 ubuntu](https://i.ytimg.com/vi/ee8Toz6w7HY/hqdefault.jpg)
If you are going with RAM, make sure you check size of /var/run folder. If you do not have ample RAM you can pick any other location. You need give Nginx a folder store fastcgi_cache content. I will recommend using /var/run on Ubuntu as its mounted as tmpfs (in RAM).
![404 not found nginx 1.4 6 ubuntu 404 not found nginx 1.4 6 ubuntu](https://i.ytimg.com/vi/ml6Vqx7z3EY/maxresdefault.jpg)
If you want more control over your cache purging rules, you can play with different purging options it provides. Just activate it, go to its settings and turn on “Enable Cache Purge” option. Apart from other features, it provides cache purging options.
#404 not found nginx 1.4 6 ubuntu install#
So install Nginx helper plugin from WordPress plugin repository and activate it. But Nginx cannot automatically find out which page to purge and when to purge? Sudo apt-get install nginx-custom Install Nginx Helper PluginĪbove step ensures that Nginx can purge a page from its fastcgi_cache selectively. Reinstall nginx with fastcgi_cache purge module support sudo add-apt-repository ppa:rtcamp/nginx Otherwise, if you are on Ubuntu with default Nginx installation, you can run following commands to install nginx with fastcgi_cache_purge module. If you see nginx-cache-purge in output then you already have it. If you have installed Nginx by following our guide, then support for fastcgi_cache_purge should be already there. You can test it by running following command: nginx -V 2>&1 | grep nginx-cache-purge -o Prerequisites Check if your nginx has fastcgi_cache_purge module
![404 not found nginx 1.4 6 ubuntu 404 not found nginx 1.4 6 ubuntu](https://asdqwe.net/wp-content/uploads/2016/04/504-gateway-error.png)
Without this 3rd party module, cache won’t be updated if you create/edit any post/page in WordPress. So we need to rely on third-party nginx module. Nginx has built-in support for fastcgi_cache but it doesn’t have mechanism to purge cached content built-in. Rather than asking a complex PHP-MySQL application like WordPress to do some extra work for caching, we will ask light-weight Nginx to cache WordPress content on its end. Today, we will use an altogether different way of caching! In first part of this series, we have seen many combinations of different WordPress setup with different caching plugins. Easyengine (ee) note: If you are using easyengine, you can accomplish everything in this article using command: ee site create -wpfc