It IS the plugin, but I’m going to go talk to that tech becuase this was a noted issue.
Your wp-config has the wrong Varnish IP. Your server was moved and this section of your wp-config was set so you could work with CloudFlare (who can be weird):
// for using cloudflare with varnish
define('VHP_VARNISH_IP','208.97.157.21');
Your IP is 67.205.24.254 (you can see it in your Panel – go to your DNS settings and it’s your A record).
However it looks like you’re not using cloudflare anymore, so you can just delete that part of your config and the plugin should start working again 🙂
I had the same issue. However we never had it before. Any thoughts on why this would just start happening now. I never had the varnish config entry in wp-config.php. So I added it and the problem went away.
Are you using CloudFlare or some other proxy before your domain like Sucuri’s firewall? That’s why :/
Varnish runs the purge command based on your URL so if an DNS check on domain.com doesn’t match the IP your server is actually on, it 503s.
I’ve been trying to make it smarter, to always grab the IP, but it’s not actually easy since there are infinite setup possibilities.
Yeah we are using cloudflare but also a load balancer. I believe the load balancer is where the issue is because they made some config changes to it recently. Before a week ago all was working fine with your plugin and there was no need for the explicit IP declaration in wp-config.php.
Then suddenly a few days ago it start timing out.
The load balancer probably changed how it passed the domain through to the IP yeah. It’s a very weird thing 🙂