Hi Allen, I have a sample config that seems to be 1:1 the same like yours.
* I cannot make any type of connection on an initial port 80* => that means your browser will show a "page not found" error or what? I guess that has nothing todo with OpenMeetings then (except the server is just offline). Sebastian 2012/2/6 Allen Underdown <wbrc...@gmail.com> > Ok, so in a previous post on ports I was concerned with Apache interfering > with OM operations on port 80. > > Rather than try to eliminate Apache and insure a clean network, I just > blew away the machine (in ESXi) > and re-built it from scratch. > > My issue is that I need to allow access to OM from behind various > firewalls, with OM itself being behind > a firewall. I obviously have control over my end, and can forward > ports/NAT policies etc. > > So, to make things easy, I planned on just having OM work on port 80/443 > as described in the Wiki > documents. > > For grins, I checked iptables - all clean. I didn't install any firewall. > The only item in inetd.conf is telnetd > on port 23 (which I added). > > Unfortunately, I must be missing something. I cannot make any type of > connection on an initial port 80 > request. If I reset everything back to defaults for 5080/8088 it all > works fine. > > Also, for some reason, the index.html file also does not seem to read > properly (??), but this may be tied > to the above. I just need a clean re-direct to my default OM directory/port > > I've attached config.xml (in text form) and red5.properties (in text > form). I want to make sure that I'm > changing the right config parms. > > If this is all correct, next step will have to be WireShark and some debug. > > Ubuntu 10 LTS and latest OM 1.9 release. > > Thanks! > Allen > -- Sebastian Wagner http://www.openmeetings.de http://incubator.apache.org/openmeetings/ http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com
