Este plugin no se ha probado con las últimas 3 versiones mayores de WordPress. Puede que ya no tenga soporte ni lo mantenga nadie, o puede que tenga problemas de compatibilidad cuando se usa con las versiones más recientes de WordPress.

Varnish/Nginx Proxy Caching


Complete WordPress Varnish Cache 3.x/4.x/5.x and Nginx Proxy Cache integration.

This plugin handles all integration with Varnish Cache and Nginx Proxy Cache. It was designed for high traffic websites.

Main features

  • admin interface, see screenshots
  • console for manual purges, supports regular expressions so you can purge an entire folder or just a single file
  • supports every type of Varnish Cache implementation, see screenshots for examples
  • unlimited number of Varnish Cache servers
  • use of custom headers when communicating with Varnish Cache does not interfere with other caching plugins, cloudflare, etc
  • Varnish Cache configuration generator
  • purge key method so you don’t need to setup ACLs
  • debugging
  • actively maintained

You can control the following from the Varnish Caching admin panel :

  • Enable/Disable caching
  • Homepage cache TTL
  • Cache TTL (for every other page)
  • IPs/Hosts to clear cache to support every type of Varnish Cache implementation
  • Override default TTL in posts/pages
  • Purge key based PURGE
  • Logged in cookie
  • Debugging option
  • console for precise manual purges

This plugin also auto purges Varnish Cache / Nginx Proxy Cache when your site is modified.

Varnish Caching sends a PURGE request to Varnish Cache / Nginx Proxy Cache when a page or post is modified. This occurs when editing, publishing, commenting or deleting an item, and when changing themes.
Not all pages are purged every time, depending on your Varnish / Nginx Proxy Cache configuration. When a post, page, or custom post type is edited, or a new comment is added, only the following pages will purge:

  • The front page
  • The post/page edited
  • Any categories or tags associated with the page

Varnish Cache / Nginx Proxy Cache is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. This plugin does not install Varnish/Nginx for you, nor does it configure Varnish/Nginx for WordPress. It’s expected you already did that on your own using the provided config files.

Inspired from the following :



  • Settings admin panel
  • Console/manual purge admin panel
  • Varnish Cache Statistics admin panel
  • Varnish Cache configuration generator admin panel
  • override default TTL in posts/pages
  • integration example


  • You must install Varnish Cache/Nginx Proxy Cache on your server(s)
  • Go to the configuration generator. Fill in the backends/ACLs then download the configuration files
  • Use these configuration files to configure Varnish Cache server(s). Usualy the configuration files are in /etc/varnish. In most cases you must put the downloaded configuration files in /etc/varnish and restart Varnish Cache
  • The configuration generator does not support Nginx for now. Read the Nginx documentation on how to enable proxy cache

Or use the provided Varnish Cache configuration files located in /wp-content/plugins/vcaching/varnish-conf folder.

You can also use the purge key method if you can’t setup ACLs. You must fill in lib/purge.vcl the purge key.

Preguntas frecuentes

What version of Varnish Cache is supported?

This was built and tested on Varnish 3.x/4.x/5.x.

Is Nginx supported?

Nginx is supported if you configure Nginx to use the PURGE method. Read the official Nginx documentaton on how to do this. Also there are a lot of tutorials to do this.

Why doesn’t every page flush when I make a new post?

The only pages that should purge are the post’s page, the front page, categories, and tags.

How do I manually purge the whole cache?

Click the ‘Purge ALL Varnish Cache’ button on the “Right Now” Dashboard.

How do I manually purge cache?

Use the console. For example you can purge the whole uploads folder with the URL /wp-content/uploads/.*

Does this work with W3 Total Cache?

Yes it does. This plugin uses its own custom headers to communicate with Varnish and does not interfere with the heders sent by W3 Total Cache or any other caching plugin.

Varnish Statistics

Statistics need a special setup. More info on the Statistics tab on your WordPress environment.

How do I configure my Varnish Cache VCL?

Use the Varnish Cache configuration generator. Fill in the backends/ACLs then download your configuration files.
Or use the provided Varnish Cache configuration files located in /wp-content/plugins/vcaching/varnish-conf folder.

Can I use this with a proxy service like CloudFlare?


What is logged in cookie?

Logged in cookie is a special cookie this plugin sets upon user login. Varnish Cache uses this cookie to bypass caching for logged in users.

This is a small step towards securing your site for denial of service attacks. Denial of service attacks can happen if the attacker bypasses Varnish Cache and hits the backend directly.
With the current configuration and the way WordPress works, this can still happen with POST/AJAX requests.

Available filters
  • vcaching_varnish_ips – change the IPs set in Settings
  • vcaching_varnish_hosts – change the Hosts set in Settings
  • vcaching_events – add events to trigger the purge
  • vcaching_schema – change the schema (default is http://)
  • vcaching_purge_urls – add additional URLs to purge


4 de diciembre de 2019
There are a bunch of Varnish purging / banning plugins out there but this is the only one that seems to work with a Plesk Docker container setup. Very much appreciated 🙂
10 de julio de 2018
I’ve spent months (on and off) trying to achieve what the VCL generator this plugin has gives to you. Simply amazing. And the few tweaks I needed I learned from my months of failure. Thank you for this great plugin!
15 de abril de 2018
Configuring Varnish is so hard and even if you get varnish to work usually it does not cache. Well, with this plugin, the nightmare is over. Great work. Thank you.
7 de noviembre de 2016 5 respuestas
A great way to test if Varnish is truly and totally working on website is verifying if the “age” value is increasing in page’s header when checking the website using a tool like Chrome’s Developer Tools. I was having a problem where this age value in header was always 0 which meant that Varnish was not caching pages properly. After testing different Varnish configs from Google, I was never able to make it work. After installing this plugin, this age value is now increasing. It integrates perfectly with wordpress. However, the purge option was not working properly on my website and the age value (which was now increasing thanks to this plugin) was not being purged when purging Varnish using this plugin, therefore, it was constantaly increasing without rolling back to 0. Nevertheless, this purge problem was also resolved after installing the “Varnish HTTP Purge” plugin.
Leer todas las 10 reseñas

Colaboradores y desarrolladores

Este software es de código abierto. Las siguientes personas han contribuido a este plugin.


“Varnish/Nginx Proxy Caching” ha sido traducido a 4 idiomas locales. Gracias a los traductores por sus contribuciones.

Traduce “Varnish/Nginx Proxy Caching” a tu idioma.

¿Interesado en el desarrollo?

Revisa el código, echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios


  • scheduled posts flush


  • readme.txt update


  • typo fix


  • Nginx Proxy Cache support, uninstall script, use ssl optimization


  • various bugfixes


  • fixed php notice


  • fixed wp-cli calling an older method name


  • use sys_get_temp_dir() to address open_basedir restictions to /tmp. thanks @maltfield


  • no more SSl auto detection. If you use SSL with Varnish use the option ‘Use SSL (https://) for purge requests.’
  • there are cases where the website uses SSL, but the Varnish servers do not


  • added sslverify set default to false to wp_remote_request. thanks @Jules81


  • fixed php notice


  • added SSL to schema filter. thanks @Jules81


  • fixed purge_post empty 2nd param


  • Do/do not purge when saving menus option
  • fixed bug showing multiple Truncate message activated ...


  • Varnish 5.x support


  • fixed ob_end_flush error in wp-admin while debug is on. thanks @samlangdon


  • improvements to Varnish configs like websocket support, remove the Google Analytics added parameters, strip hash, remove unnecessary cookies. thanks @pavelprischepa


  • hardcoded on/off VCL Generator, filters added to readme


  • added AMP URL purge


  • fixed PHP notices
  • tested with 4.6


  • Purge from Varnish post/page action link
  • removed 10 chars logged in cookie restriction
  • code cleanup/some wp coding standards
  • vcaching_varnish_ips filter
  • vcaching_varnish_hosts filter


  • Truncate option added for too many ‘trying to purge’ messages. Added check for ZipArchive class to download VCLs.


  • Bugfix release. Replaced home_url with plugins_url to show VCaching image


  • Do not cache static files on admin domain


  • Varnish Cache configuration generator
  • added logged in cookie. This replaces the logged in admin/user based on WordPress standard cookies to bypass caching
  • moved backends to conf/backend.vcl
  • moved ACLs to conf/acl.vcl
  • updated VCLs. If you are using 1.3 VCLs should upgrade to 1.4


  • support for Varnish 4


  • bugfix displaying a single server stats


  • better varnish statistics, generated by varnishstat


  • varnish statistics


  • wordpress 4.4 compatibility
  • Romanian language file


  • wp cli


  • console for precise manual purge


  • Play nice with W3 Total Cache


  • Initial commit