Squid + BBB

72 views
Skip to first unread message

Paul Ascher

unread,
Mar 5, 2010, 12:37:48 PM3/5/10
to BigBlueButton-dev
Hi group,

I'm using squid for reverse proxy at our ec2 small ubuntu instance,
the same box where we're testing bbb on the internet.

After I figured out how to configure squid and bbb, they co-exist in
harmony, or so I thought...

Here is the deal, squid listens to port 80, so I had to change nginx
default and bbb configuration files to listen to port 8081.
Also I edited the hosts file from this server so that
conf.mywebsite.org points to 127.0.0.1

Then I did bbb.conf --setip conf.mywebsite.org

My squid configuration file looks like this:

http_port 80 accel defaultsite=www.mywebsite.org vhost

cache_peer production_ip_address parent 80 0 no-query originserver
name=web
acl sites_acmeweb dstdomain www.mywebsite.org
http_access allow sites_web
cache_peer_access web allow sites_web
cache_peer_access web deny all

cache_peer 127.0.0.1 parent 8081 0 no-query originserver name=bbb
acl sites_bbb dstdomain conf.mywebsite.org
http_access allow sites_bbb
cache_peer_access bbb allow sites_bbb
cache_peer_access bbb deny all

Since we're still testing this stuff, our elastic ip still points to
the production box of our website, and we alter our local hosts files
to test it.

This all works just fine, except we wanted to show bbb(with our video
quality changes) to one of the directors, and we don't want to ask her
to change her hosts file because she's not a tech person.
So, I stopped squid, pointed nginx files back to port 80, and bbb-conf
--setip theIpAddress

Now the weird part, when we tried bbb by just pointing our browsers to
the ip address, bbb not only works, but the video quality is way
better!

I can't see any reason for that, it's just odd, is there a difference
from using port 8081 instead of 80?
Or maybe squid was the problem?
Or was it just some coincidence?

I'd appreciate if you could please share any insights you might have.

Best,

Paul


Now we xan

Jeremy Thomerson

unread,
Mar 5, 2010, 12:44:50 PM3/5/10
to bigblueb...@googlegroups.com
I don't know why that would happen, but so you know, nginx is also doing proxying to backend stuff (tomcat, red5, etc).  So, perhaps it was just because you were proxying twice (squid <-> nginx <-> red5)?

Jeremy Thomerson
http://genericconf.com
BigBlueButton with local number telephone conferencing




--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
To post to this group, send email to bigblueb...@googlegroups.com.
To unsubscribe from this group, send email to bigbluebutton-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bigbluebutton-dev?hl=en.


Walter Tak

unread,
Mar 5, 2010, 1:22:06 PM3/5/10
to bigblueb...@googlegroups.com
Second that. I've used squid for years and the reverse proxy / http-accellerator can be a pain in the ass to configure correctly. In combination with nginx I wish you all the luck you can get.
 
Perhaps you want to check out the nginx configuration and will see that incoming traffic to port 80 is actually split based upon request to various locations or even other ports.
 
In the end I installed nginx on my frontend-server and changed all hosts and locations in the nginx conf to point at the correct servers. For the time being I also copied all fixed files (e.g. the SWF files located in [/client]) to the frontend server , leaving BBB to handle Tomcat and Red5 traffic ony.
 
Regards,
Walter
Reply all
Reply to author
Forward
0 new messages