You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Joon Lee <ju...@gmail.com> on 2012/03/21 14:06:23 UTC

[users@httpd] Re: users Digest 19 Mar 2012 01:35:58 -0000 Issue 4312

>>Drop the cookie thing and replace localhost with 192.168.1.5 in the proxy
lines

Hi Igor, I tried removing the cookie-related lines and replacing localhost
with the ip address as you mentioned, but that gives me a 503 error from a
browser on the server itself and the same inability to connect from other
computers on the network as before.  Here's the relevant entry in the error
log:

[Wed Mar 21 09:00:46 2012] [error] (111)Connection refused: proxy: HTTP:
attempt to connect to 192.168.1.5:8888 (192.168.1.5) failed
[Wed Mar 21 09:00:46 2012] [error] ap_proxy_connect_backend disabling
worker for (192.168.1.5)

Does this mean that there's another setting configuration that's out of
place?

Re: [users@httpd] Re: users Digest 19 Mar 2012 01:35:58 -0000 Issue 4312

Posted by Igor Cicimov <ic...@gmail.com>.
That means the proxy works but the backend doesnt. Do you have anything
listening on port 8888? If you do check it log files to see why is it
refusing connections.
 On Mar 22, 2012 12:06 AM, "Joon Lee" <ju...@gmail.com> wrote:

> >>Drop the cookie thing and replace localhost with 192.168.1.5 in the
> proxy lines
>
> Hi Igor, I tried removing the cookie-related lines and replacing localhost
> with the ip address as you mentioned, but that gives me a 503 error from a
> browser on the server itself and the same inability to connect from other
> computers on the network as before.  Here's the relevant entry in the error
> log:
>
> [Wed Mar 21 09:00:46 2012] [error] (111)Connection refused: proxy: HTTP:
> attempt to connect to 192.168.1.5:8888 (192.168.1.5) failed
> [Wed Mar 21 09:00:46 2012] [error] ap_proxy_connect_backend disabling
> worker for (192.168.1.5)
>
> Does this mean that there's another setting configuration that's out of
> place?
>