[nick tailor]

Yes, this would most likely not be varnish issue.

Are you able to telnet to port 80 from the varnish to server to your
webservers on the internal or NAT ip?

If not, you should check your router firewall to ensure your allowing
traffic to the internal ip on port 80 to your webservers, retest the telnet
from varnish server to your webserver until you can get a connection. :)

Cheers

Nick Tailor

On Tue, Nov 20, 2012 at 2:12 PM, Bjørn Ruberg <bjorn at ruberg.no> wrote:

>  On 11/20/2012 11:03 PM, Reinhard Trompetter wrote:
>
> Hi,
>
> I cannot solve my problem, therefore again I write this post:
>
>
> Please use a descriptive subject when posting to the list.
>
>
>  My public IP is 217.140.77.176 und the corresponding domain "
> www.medmoodle.de".
>
> The varnish cache server hat the IP 192.168.1.59 and is reached over NAT
> and port 80 from my router with the public IP above.
>
>
> $ telnet 217.140.77.176 80
> Trying 217.140.77.176...
> telnet: Unable to connect to remote host: Connection refused
>
> Also:
>
> http://www.downforeveryoneorjustme.com/217.140.77.176
>
> There seems to be an error with your router's configuration, and/or the
> server on the inside does not respond to connection requests on port 80.
> It's quite probably not a Varnish issue.
>
> --
> Bjørn
>
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20121120/e2cee07e/attachment.html>