What else can I try

Paul A. Procacci pprocacci at datapipe.com
Thu Apr 10 03:01:37 CEST 2014

Copied the list for completeness......

On Thu, Apr 10, 2014 at 01:50:46AM +0100, Roy Forster wrote:
> Thanks Paul not yet sure how to do that but at least I feel hopeful

Let me try to be a bit descriptive:

Let's say you have apache listening on and   (randomly selected)

The host your interested in as defined in your apache config is
sitting on

Varnish listens on

In your varnish config you define the backend as

The problem I believe you are running into is you are connecting to
apache from varnish over an interface that apache can't make a match
on.  You've connected to but the host is sitting @

Since you didn't provide this information this is a stab in the dark,
but something like this or similar would give you the default page
you are describing.


> On 10 April 2014 01:45, Paul A. Procacci <pprocacci at datapipe.com> wrote:
> > On Wed, Apr 09, 2014 at 07:42:59PM -0500, Paul A. Procacci wrote:
> > > On Thu, Apr 10, 2014 at 01:38:14AM +0100, Roy Forster wrote:
> > > > When I access my site using :8080 the site loads but there is no
> > mention of
> > > > varnish in the header. Without :8080 appended I get the default website
> > > > page but varnish is mentioned in the header.
> > >
> > > You'll have to forgive me, but this sounds like it's functioning just
> > fine.
> >
> > I'm sorry (again) ... you mean default apache page?
> >
> > If that's the case, make sure your backend configuration matches the way
> > you
> > are accessing it.  For instance....if you are accessing it via ip address,
> > you need to ensure that ip address is defined in the vhost container.
> >
> > That should be about it.
> >

More information about the varnish-misc mailing list