Thanks Mahedi. Your setting worked like a champ. Since I will be using LDAP, I like to trying to get https to work on 443 and RTMPS on 80. If you know of a setting please let me know. I am following the HTTPS/RTMPS work instruction but changing the port value around.
On Thu, Apr 2, 2015 at 12:52 PM, Mahedi Kaysar < [email protected]> wrote: > I did change in http only. > > Thanks > Mahedi > > On 2 April 2015 at 20:08, FJ <[email protected]> wrote: > >> Thank you Mahedi. Is this from from http or https configuration? >> >> On Thu, Apr 2, 2015 at 11:31 AM, Mahedi Kaysar < >> [email protected]> wrote: >> >>> Hi, >>> I was also facing problem like you that was solved by changing two files >>> bellow: >>> red5.properties: >>> http.port=80 >>> rtmp.port=443 >>> >>> config.xml >>> <rtmpport>443</rtmpport> >>> <red5httpport>80</red5httpport> >>> >>> Thanks >>> Mahedi >>> >>> On 2 April 2015 at 19:21, FJ <[email protected]> wrote: >>> >>>> ahhh, ok. Thanks Maxim. Wonder if the same behavior apply I use >>>> https/rtmps configuration, that it would attempt 8443 first then 443 on >>>> try1. >>>> >>>> On Thu, Apr 2, 2015 at 11:15 AM, Maxim Solodovnik <[email protected] >>>> > wrote: >>>> >>>>> Code modification only :( >>>>> >>>>> WBR, Maxim >>>>> (from mobile, sorry for the typos) >>>>> On Apr 3, 2015 12:12 AM, "FJ" <[email protected]> wrote: >>>>> >>>>>> Thanks Maxim. I am testing as root at the moment and it seems to >>>>>> work in logged in using port 80. But when I start the room, there seem >>>>>> to >>>>>> be a delay because it attempting to use port 1935 then "try1" using port >>>>>> 80 >>>>>> that I change in webapps/openmeetings/public/config.xml >>>>>> red5httpport>80</red5httpport. >>>>>> >>>>>> Is there away to bypas the first default attempt to port 1935 and go >>>>>> straight to using port 80? >>>>>> >>>>>> >>>>>> >>>>>> On Thu, Apr 2, 2015 at 10:47 AM, Maxim Solodovnik < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> running on ports lower than 1000 requires additional permissions >>>>>>> You can google on how to bypass that, I'm not system administrator >>>>>>> so I can't help here >>>>>>> >>>>>>> you can search the list "mod_proxy" there were number of questions >>>>>>> regarding it >>>>>>> >>>>>>> On Thu, Apr 2, 2015 at 9:55 PM, FJ <[email protected]> wrote: >>>>>>> >>>>>>>> Maxim, I tried the red5.properties settings backoon OM2.x days and >>>>>>>> got a denied message. I read that it require root level privileges. >>>>>>>> Has >>>>>>>> that change in OM 3.x? >>>>>>>> >>>>>>>> As far as Apache proxy, where would I go to configure it once I >>>>>>>> install apache in Ubuntu? >>>>>>>> >>>>>>>> -john- >>>>>>>> >>>>>>>> On Thu, Apr 2, 2015 at 1:54 AM, Maxim Solodovnik < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> you can set port 80/443 in red5.properties or set up apache to >>>>>>>>> proxy OM for you >>>>>>>>> >>>>>>>>> On Thu, Apr 2, 2015 at 1:51 PM, FJ <[email protected]> wrote: >>>>>>>>> >>>>>>>>>> Has anyone gotten OM to run on lower ports like 80 or 443? One >>>>>>>>>> of the challenges I face is that alot of company block high ports >>>>>>>>>> and so >>>>>>>>>> when I sent an invite to connect to my OM running either 5080/5443 or >>>>>>>>>> 8443/1935, they can't connect. >>>>>>>>>> >>>>>>>>>> I appreciate any input on how this can be done. >>>>>>>>>> >>>>>>>>>> -john- >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> WBR >>>>>>>>> Maxim aka solomax >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> WBR >>>>>>> Maxim aka solomax >>>>>>> >>>>>> >>>>>> >>>> >>> >> > > > >
