Adam@Gmail wrote:
Hello there,
Thanks for the reply Ron and Amos
Maybe my original e-mail wasn't clear a bit confusing I am sorry if I
confused you
I have squid running on Machine A with let's say local ip 192.168.1.4
the backend server is running on machine B and ip address 192.168.1.3
Now, instead of getting the website that is located on Machine B
192.168.1.3 which is listening on port 81 not 80.
I am getting the default Apache Page on the Proxy server Machine which
is 192.168.1.4
And I do have the vhost in my configuration
Well there are two apaches running on the two machines, the proxy
machine and the web-server machine, except the web-server apache
listens on port 81, logically (technically) speaking it should work,
but for some reason it doesn't.
I hope it makes more sense to you what I am trying to describe here
Very helpful.
You can not have apache listening for port 80 on 192.168.1.4 and Squid
trying to do the same thing.
Only one process can have port 80.
You will very likely find a note in the squid logs that says something
to the effect that squid can not bind to port 80.
If you shutdown apache on 192.168.1.4 and restart squid, your proxy will
work (if the rest of the configuration is correct)
If you then try to start apache on 192.168.1.4 it will certainly
complain loudly about port 80 not being free.
If you want to use Apache on both 192.168.1.4 and 192.168.1.3 you need
to set the apache on 192.168.1.4 to listen on port 81 and set squid to
proxy to the apache on 192.168.1.4 and use apache's proxy and vhost
features to reach 192.168.1.5 which can be set to listen on port 80.
This will support
browser=>Squid on 192.168.1.4 ==> Apache on 192.168.1.4:81 (vhost)
==>Apache 192.168.1.3:80
That is a pretty common approach.
Ron
Thank you all for your help
Regards
Adam
----- Original Message ----- From: "Amos Jeffries" <squid3@xxxxxxxxxxxxx>
To: <squid-users@xxxxxxxxxxxxxxx>
Sent: Thursday, March 25, 2010 1:01 AM
Subject: Re: Help with accelerated site
On Wed, 24 Mar 2010 19:48:27 -0400, Ron Wheeler
<rwheeler@xxxxxxxxxxxxxxxxxxxxx> wrote:
What is squid proxying?
Usually the normal behaviour is exactly what you are getting since
squid
normally proxies Apache on 80.
Browser ==> Squid on 80==>proxied to Apache on port 81.
If Squid is not proxying Apache, then it looks like you have Apache
running on 80.
If you are trying to redirect port 80 to another program that is not
Apache, then you need to get Apache off port 80.
You can not have 2 programs listening to port 80.
If Apache is running and owns port 80, Squid will not start.
If this is the case, You likely have errors in the logs to this effect.
Shut down Apache and and restart Squid.
Try to start Apache and now it should howl with anger (or log in anger)
at not getting port 80.
Ron
Adam@Gmail wrote:
Hello All,
I have followed this configuration, but when I try and access the
website from outside my network
All I get is the default page of the apache on the machine where the
Squid proxy is installed
Here is the link:
http://wiki.squid-cache.org/ConfigExamples/Reverse/BasicAccelerator
here is the configuration I followed
http_port 80 accel defaultsite=your.main.website.name(changed my port
to 81 my backend server listens on port 81)I havehttp_port 81 accel
defaultsite=www.my.website.org vhostand then used thiscache_peer
ip.of.webserver parent 80 0 no-query originserver
name=myAccelcache_peer 192.168.1.5 parent 81 0 no query originserver
name=myAccel(myAccel I have put a name)and then acl our_sites
dstdomain my.website.org
http_access allow our_sites
cache_peer_access myAccel allow our_sites
cache_peer_access myAccel deny all Anybody with any suggestions
please?Any help would be appreciated thank youRegardsAdam
Sorry, took me a while to un-mangle that original email text.
You are missing the "vhost" option on https_port 80. All traffic Squid
receives on port 80 will go to Apache's default virtual host.
Amos
