0

I am using Varnish 3 in front of nginx running multiple WordPress sites. I am using a default.vcl recommended and used by many large WordPress sites.

default.vcl: http://pastebin.com/KaSdvuRS

I am using W3 Total Cache which has an option to automatically purge when clearing the cache. I also tested installing Varnish HTTP Purge plugin to purge posts/pages when editing them. Neither seemed to work so I tested interactive session over ssh w/ curl.

I am logged into SSH on the varnish/nginx box, and I type the following command to test the varnish purge:

curl -X PURGE http://www.example.com

The result is:

<head>
    <title>405 Not allowed.</title>
  </head>
  <body>
    <h1>Error 405 Not allowed.</h1>
    <p>Not allowed.</p>
    <h3>Guru Meditation:</h3>
    <p>XID: 265824636</p>
    <hr>
    <p>Varnish cache server</p>
  </body>

Any ideas what I am missing? This vcl file is very similar to what is recommended by Varnish-Cache.org for WordPress and is the purge configuration I see recommended everywhere.

Ketola
  • 2,767
  • 18
  • 21
Michael
  • 525
  • 1
  • 8
  • 20

1 Answers1

1

Chances are, you're connecting to your Varnish box via the public IP and Varnish will also see a public IP connecting, not a local one. Your ACL for purges now only allows localhost/127.0.0.1. You may want to extend that list with the public IP address of your server as well.

Alternatively, try debugging by removing the ACL check and by simply allowing purges from everyone, just to exclude the ACL as the guilty one.

Mojah
  • 1,373
  • 2
  • 12
  • 16
  • Thanks, I added my public IP and it fixed it. I assumed using curl via SSH on the same server would have been using localhost. Now to see if I can get W3 Total Cache to clear it properly. – Michael Oct 02 '12 at 05:49
  • Wouldn't this allow anyone to send the purge request ? – Raphaël Sep 27 '13 at 09:34