Telnet works fine, when i type get I get the front page.

The problem is not routing, as I have other web hosts configured the same
way and they work fine.

Is there any sort of caching being done on pound?

On Thu, Jun 30, 2011 at 11:31 AM, Jacob Anderson 
<[email protected]>wrote:

> Test #1:****
>
> ** **
>
> > telnet 192.168.1.5 80   (from the pound machine)****
>
> ** **
>
> If this fails, then you have a firewall rule blocking port 80 outbound
> traffic, or you have a port 80 inbound block on 192.168.1.5.****
>
> ** **
>
> Pound often times must reside on both an external and internal network. The
> next test is to see if your routing is bad. Do the “route -n -a” to get all
> of your routes to see if your 192.168.1.0/24 network is being routed
> correctly on the pound machine. You may have your default routing for that
> network using the same interface as your external interface, which is no
> good.****
>
> ** **
>
> -- jake****
>
> ** **
>
> ** **
>
> *From:* Nelson Pereira [mailto:[email protected]]
> *Sent:* Thursday, June 30, 2011 5:28 AM
> *To:* [email protected]
> *Subject:* [Pound Mailing List] New problems arrising, cannot connect to
> web server...****
>
> ** **
>
> see bellow what errors imn getting:****
>
>  ****
>
> Jun 30 08:15:17 pound pound: received signal 15 - exiting...
> Jun 30 08:15:43 pound pound: (b731db70) connect_nb: poll timed out
> Jun 30 08:15:43 pound pound: (b731db70) backend 192.168.1.5:80 connect:
> Connection timed out
> Jun 30 08:15:43 pound pound: (b731db70) BackEnd 192.168.1.5:80 dead
> (killed)
> Jun 30 08:15:43 pound pound: (b731db70) e503 no back-end "GET / HTTP/1.1"
> from 208.87.23.173
> Jun 30 08:16:04 pound pound: (b739fb70) connect_nb: poll timed out****
>
>  ****
>
> This has started happening since I moved servers.****
>
>  ****
>
> The addres 192.168.1.5 works fine when accessing from the inside network
> and/or vpn****
>
>  ****
>
> im running the latest (i think) 2.5. What is the command to see what
> version is running?****
>
>  ****
>
> thanks for any help.****
>
>  ****
>

Reply via email to