You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Allen Underdown <wb...@gmail.com> on 2012/02/06 23:32:28 UTC
Still having port issues
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
Re: Still having port issues
Posted by Allen Underdown <wb...@gmail.com>.
Found the problem(s).
See attached error-log.txt and red5-log.txt
So, by what I read, there is something wrong with axis2.xml and a
permissions problem with Tomcat on port 80.
Have no clue where to go from here. Too busy until next week to dig
into axis2.xml (If I remember it's in
/opt/red5/webapps/openmeetings/WEB-INF/conf/ ??) or
to read the Tomcat docs..
Any help appreciated!
Allen
On Wed, Feb 8, 2012 at 8:25 AM, seba.wagner@gmail.com
<se...@gmail.com> wrote:
> Hi Allen,
>
> you should make sure you understand the connection procedure:
>
> There are always 3 ports involved, not two.
>
> 1) You have the HTTP (default 5080) port that loads the SWF, the images,
> upload/download documents (or potentially https if you configure it)
> 2) RTMP (default 1935), the client first tries to connect 3 times to the
> rtmp port (or potentially rtmpS if you configured it)
> 3) RTMPT (default 8088), if the client fails to connect via rtmp if tries
> the firewall friendly (but more CPU hungry) RTMP over HTTP Tunneling, or
> short: rtmpT
>
> So there are 3 ports not 2. And actually 5080/8088 is not true, default
> would be 5080/1935. 8088 is just the port of the fallback protocol rtmpT.
>
> Sebastian
>
>
> 2012/2/8 Allen Underdown <wb...@gmail.com>
>>
>> All on the same subnet - no firewall involved yet. No software firewalls
>> turned on either host or client. This is why I'm confused. Same machines
>> work when everything is set to 5080/8088..
>>
>> If I get some time today I'll fire up WireShark and look at what's going
>> on between the machines.
>>
>>
>> On Wed, Feb 8, 2012 at 1:31 AM, seba.wagner@gmail.com
>> <se...@gmail.com> wrote:
>>>
>>> Connection reset means that it could not connect via rtmp / rtmpt
>>> but port 80 does work.
>>>
>>> You've configured rtmp to be 1935
>>> and rtmpt to be 433
>>>
>>> I guess at least 433 does work, but have you configured your netwetwork
>>> and firewall that these ports are forwarded to the OpenMeetings server ?
>>>
>>> Sebastian
>>>
>>>
>>> 2012/2/7 Allen Underdown <wb...@gmail.com>
>>>>
>>>> Will have to confirm but not a page not found. Think it was a
>>>> "connection reset".
>>>>
>>>> Time to fire up wireshark...
>>>>
>>>> On Feb 7, 2012 7:35 AM, "seba.wagner@gmail.com" <se...@gmail.com>
>>>> wrote:
>>>>>
>>>>> 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 <wb...@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.wagner@gmail.com
>>>
>>>
>>>
>>>
>>> --
>>> Sebastian Wagner
>>> http://www.openmeetings.de
>>> http://incubator.apache.org/openmeetings/
>>> http://www.webbase-design.de
>>> http://www.wagner-sebastian.com
>>> seba.wagner@gmail.com
>>
>>
>
>
>
> --
> Sebastian Wagner
> http://www.openmeetings.de
> http://incubator.apache.org/openmeetings/
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
Re: Still having port issues
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
Hi Allen,
you should make sure you understand the connection procedure:
There are always 3 ports involved, not two.
1) You have the HTTP (default 5080) port that loads the SWF, the images,
upload/download documents (or potentially https if you configure it)
2) RTMP (default 1935), the client first tries to connect 3 times to the
rtmp port (or potentially rtmpS if you configured it)
3) RTMPT (default 8088), if the client fails to connect via rtmp if tries
the firewall friendly (but more CPU hungry) RTMP over HTTP Tunneling, or
short: rtmpT
So there are 3 ports not 2. And actually 5080/8088 is not true, default
would be 5080/1935. 8088 is just the port of the fallback protocol rtmpT.
Sebastian
2012/2/8 Allen Underdown <wb...@gmail.com>
> All on the same subnet - no firewall involved yet. No software firewalls
> turned on either host or client. This is why I'm confused. Same machines
> work when everything is set to 5080/8088..
>
> If I get some time today I'll fire up WireShark and look at what's going
> on between the machines.
>
>
> On Wed, Feb 8, 2012 at 1:31 AM, seba.wagner@gmail.com <
> seba.wagner@gmail.com> wrote:
>
>> Connection reset means that it could not connect via rtmp / rtmpt
>> but port 80 does work.
>>
>> You've configured rtmp to be 1935
>> and rtmpt to be 433
>>
>> I guess at least 433 does work, but have you configured your netwetwork
>> and firewall that these ports are forwarded to the OpenMeetings server ?
>>
>> Sebastian
>>
>>
>> 2012/2/7 Allen Underdown <wb...@gmail.com>
>>
>>> Will have to confirm but not a page not found. Think it was a
>>> "connection reset".
>>>
>>> Time to fire up wireshark...
>>> On Feb 7, 2012 7:35 AM, "seba.wagner@gmail.com" <se...@gmail.com>
>>> wrote:
>>>
>>>> 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 <wb...@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.wagner@gmail.com
>>>>
>>>
>>
>>
>> --
>> Sebastian Wagner
>> http://www.openmeetings.de
>> http://incubator.apache.org/openmeetings/
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.com
>> seba.wagner@gmail.com
>>
>
>
--
Sebastian Wagner
http://www.openmeetings.de
http://incubator.apache.org/openmeetings/
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: Still having port issues
Posted by Allen Underdown <wb...@gmail.com>.
All on the same subnet - no firewall involved yet. No software firewalls
turned on either host or client. This is why I'm confused. Same machines
work when everything is set to 5080/8088..
If I get some time today I'll fire up WireShark and look at what's going on
between the machines.
On Wed, Feb 8, 2012 at 1:31 AM, seba.wagner@gmail.com <seba.wagner@gmail.com
> wrote:
> Connection reset means that it could not connect via rtmp / rtmpt
> but port 80 does work.
>
> You've configured rtmp to be 1935
> and rtmpt to be 433
>
> I guess at least 433 does work, but have you configured your netwetwork
> and firewall that these ports are forwarded to the OpenMeetings server ?
>
> Sebastian
>
>
> 2012/2/7 Allen Underdown <wb...@gmail.com>
>
>> Will have to confirm but not a page not found. Think it was a
>> "connection reset".
>>
>> Time to fire up wireshark...
>> On Feb 7, 2012 7:35 AM, "seba.wagner@gmail.com" <se...@gmail.com>
>> wrote:
>>
>>> 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 <wb...@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.wagner@gmail.com
>>>
>>
>
>
> --
> Sebastian Wagner
> http://www.openmeetings.de
> http://incubator.apache.org/openmeetings/
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>
Re: Still having port issues
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
Connection reset means that it could not connect via rtmp / rtmpt
but port 80 does work.
You've configured rtmp to be 1935
and rtmpt to be 433
I guess at least 433 does work, but have you configured your netwetwork and
firewall that these ports are forwarded to the OpenMeetings server ?
Sebastian
2012/2/7 Allen Underdown <wb...@gmail.com>
> Will have to confirm but not a page not found. Think it was a "connection
> reset".
>
> Time to fire up wireshark...
> On Feb 7, 2012 7:35 AM, "seba.wagner@gmail.com" <se...@gmail.com>
> wrote:
>
>> 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 <wb...@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.wagner@gmail.com
>>
>
--
Sebastian Wagner
http://www.openmeetings.de
http://incubator.apache.org/openmeetings/
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: Still having port issues
Posted by Allen Underdown <wb...@gmail.com>.
Will have to confirm but not a page not found. Think it was a "connection
reset".
Time to fire up wireshark...
On Feb 7, 2012 7:35 AM, "seba.wagner@gmail.com" <se...@gmail.com>
wrote:
> 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 <wb...@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.wagner@gmail.com
>
Re: Still having port issues
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
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 <wb...@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.wagner@gmail.com