Magento & Varnish / Turpentine, Zero-hit rate

Magento & Varnish / Turpentine, Zero-hit rate

October 12, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento & Varnish / Turpentine, Zero-hit rate

Magento & Varnish / Turpentine: Diagnosing Zero-Hit Rate Issues

Introduction

Welcome to another technical deep dive on our blog! Today, we’re going to troubleshoot some perplexing issues you’ve been facing with your Magento, Nginx, and Varnish/Turpentine setup. Don’t worry, by the end of this post, we’ll have this mystery solved.

Understanding Your Setup

First things first—let’s clarify what we’re working with:

  1. Magento: Version 1.9.0.1
  2. Turpentine: The Varnish Configuration File (VCF) for Magento
  3. Varnish: Version 3.0.2
  4. Nginx: Your reverse proxy server
  5. Operating System: Ubuntu 12.04 LTS

You’ve done a great job so far by applying the VCL to your running varnish instance and enabling debug info in Turpentine. You’re also seeing that the VCL is properly loaded.

The Zero-Hit Rate Conundrum

Now let’s dive into the heart of the issue—the zero-hit rate problem you’re experiencing when both Turpentine caching methods are activated in the Magento backend cache settings, particularly the Full Page Cache (FPC).

When FPC is active:

  1. Server Response: You’re seeing a response from Nginx.
  2. Transfer Encoding: It’s using chunked transfer encoding.
  3. Via Header: The request passes through Varnish once (indicated by “Via 1.1 varnish”).
  4. Turpentine Cache and ESIs: Both are set.
  5. X-Varnish Hits & Age: These headers suggest that the request is not being served from cache—it’s a miss.

The problem lies in the X-Turpentine-Cache header, which is showing 0—the full page hasn’t been cached by Varnish or Turpentine.

Possible Causes and Solutions

Issue 1: Incomplete Turpentine Configuration

Turpentine relies on certain Magento configurations to function properly. Ensure you’ve followed the official Turpentine documentation (linked here) for your Magento version accurately.

Issue 2: VCL Mistmatch

Check if there are any discrepancies between the VCL loaded by Turpentine and what’s actually running in your Varnish instance. You can use varnishadm vcl.list to verify this.

Issue 3: URL Exclusion Rules

Turpentine may be excluding certain URLs from caching that you didn’t intend to exclude. Review the URL exclusion rules (also found in the documentation) and make sure they align with your requirements.

Best Practices for Magento + Varnish/Turpentine

  1. Always use the latest stable versions: Outdated software can lead to compatibility issues.
  2. Follow the official documentation: Turpentine’s documentation is comprehensive—use it as a guide.
  3. Regularly review and update your cache configuration: Magento updates often come with improved caching mechanisms.

Conclusion

In most cases, zero-hit rate problems like this stem from either misconfigured VCLs or URL exclusion rules that are too broad. Remember to follow the documentation closely and regularly audit your setup.

If you’re still struggling after checking these points, feel free to reach out via our Laravel Company support forum. We’re always here to help!

Happy coding!

Magento 1 Cache Admin Configuration

Our network