Hello Tom, I'm answering emails as soon as I got free time, you shouldn't expect immediate answer :))
Camera/Microphone will be started automatically as soon as you will set it up once So open the settings, choose correct devises, press Save According to port availability you need to check detailed results: push small "Copy" button on the right, Paste result to some text file and check what is wrong On Thu, Nov 9, 2017 at 2:40 AM, Tom Luo <mario...@gmail.com> wrote: > Another issue is that when I do port testing using the tool on the login > page. The port testing always fails even thought I opened all ports in my > server. > Do you know why? Is this issue related to the camera issue? > > Thanks, > > Tom > > > > On Wed, Nov 8, 2017 at 2:38 PM, Tom Luo <mario...@gmail.com> wrote: > >> Right now, I can see my video if I click "choose device". However, I >> still cannot see the video in my camera in the public conference. >> >> The demo website does not have this problem. So, I know it must be some >> settings in my side. >> Any idea how to solve this issue? >> >> Thanks, >> >> Tom >> >> >> >> On Wed, Nov 8, 2017 at 1:12 PM, Tom Luo <mario...@gmail.com> wrote: >> >>> Ok. I fixed the problem. Now I can connect using https. I will explain >>> to you how I fixed the problem later. >>> However, after I enter a public room, it seems my camera is not working. >>> I remember in OM3.3. The camera automatically starts. Is there a button >>> I need to press in OM4.0 to start my camera? >>> >>> Thanks, >>> >>> Tom >>> >>> >>> >>> On Wed, Nov 8, 2017 at 12:45 PM, Maxim Solodovnik <solomax...@gmail.com> >>> wrote: >>> >>>> I'm referring these instructions: http://openmeeti >>>> ngs.apache.org/RTMPSAndHTTPS.html >>>> Unfortunately I have no time to check everything .... >>>> >>>> >>>> On Thu, Nov 9, 2017 at 12:29 AM, Tom Luo <mario...@gmail.com> wrote: >>>> >>>>> Now there are some logs in red5.log >>>>> >>>>> 2017-11-08 17:26:39,998 [NioProcessor-11] INFO >>>>> o.r.s.net.rtmp.RTMPMinaConnection - Connection is closed: >>>>> WNZC8FWV7N3VL >>>>> 2017-11-08 17:26:39,998 [NioProcessor-11] WARN >>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Connection was not found for >>>>> WNZC8FWV7N3VL >>>>> 2017-11-08 17:26:40,007 [RTMPConnectionScheduler-5] WARN >>>>> o.r.server.net.rtmp.RTMPConnection - Closing O4WODAWEPAMAT, due to >>>>> long handshake. State: connect >>>>> 2017-11-08 17:26:40,007 [NioProcessor-12] INFO >>>>> o.r.s.net.rtmp.RTMPMinaConnection - Connection is closed: >>>>> O4WODAWEPAMAT >>>>> 2017-11-08 17:26:40,007 [NioProcessor-12] WARN >>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Connection was not found for >>>>> O4WODAWEPAMAT >>>>> >>>>> On Wed, Nov 8, 2017 at 12:22 PM, Tom Luo <mario...@gmail.com> wrote: >>>>> >>>>>> http://openmeetings.markmail.org/message/j4gx2q6woidyqj7l?q= >>>>>> letsencrypt >>>>>> >>>>>> This is the instruction I followed. I performed step 1-8. Just >>>>>> skipped step 7 as you said. >>>>>> >>>>>> I don't feel I miss any step. >>>>>> >>>>>> On Wed, Nov 8, 2017 at 12:20 PM, Maxim Solodovnik < >>>>>> solomax...@gmail.com> wrote: >>>>>> >>>>>>> Unfortunately not >>>>>>> Maybe you miss some steps from the instructions? >>>>>>> >>>>>>> On Thu, Nov 9, 2017 at 12:17 AM, Tom Luo <mario...@gmail.com> wrote: >>>>>>> >>>>>>>> Yes. I did SSL for the web interface and Set up Native RTMPS. >>>>>>>> It still does not work. Nothing is listening at port 5443. >>>>>>>> Do you have any other ideas why? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> Tom >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Nov 8, 2017 at 11:30 AM, Maxim Solodovnik < >>>>>>>> solomax...@gmail.com> wrote: >>>>>>>> >>>>>>>>> Have you performed these: http://openmeetings.apa >>>>>>>>> che.org/RTMPSAndHTTPS.html#SSL_for_the_web_interface steps? >>>>>>>>> >>>>>>>>> On Wed, Nov 8, 2017 at 11:14 PM, Tom Luo <mario...@gmail.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> I cleared my old log and restarted the red5. >>>>>>>>>> Here is my red5.log: >>>>>>>>>> >>>>>>>>>> 2017-11-08 11:04:47,270 [main] INFO org.red5.server.Launcher - >>>>>>>>>> Red5 Server 1.0.10 (https://github.com/Red5) >>>>>>>>>> 2017-11-08 11:04:47,338 [main] INFO >>>>>>>>>> o.s.c.s.FileSystemXmlApplicationContext - Refreshing >>>>>>>>>> org.springframework.context.support.FileSystemXmlApplication >>>>>>>>>> Context@5f2050f6: startup date [Wed Nov 08 11:04:47 EST 2017]; >>>>>>>>>> root of context hierarchy >>>>>>>>>> 2017-11-08 11:04:47,393 [main] INFO >>>>>>>>>> o.s.b.f.xml.XmlBeanDefinitionReader - Loading XML bean >>>>>>>>>> definitions from class path resource [red5.xml] >>>>>>>>>> 2017-11-08 11:04:47,572 [main] INFO >>>>>>>>>> o.s.b.f.xml.XmlBeanDefinitionReader - Loading XML bean >>>>>>>>>> definitions from class path resource [jee-container.xml] >>>>>>>>>> >>>>>>>>>> Right now, I can still use http at port 5080 to access OM4.0; >>>>>>>>>> however https still does not work. >>>>>>>>>> Do I need to check other places? >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> >>>>>>>>>> Tom >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Nov 8, 2017 at 10:55 AM, Maxim Solodovnik < >>>>>>>>>> solomax...@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> please check red5.log. >>>>>>>>>>> Red5 reports what ports it is listening >>>>>>>>>>> >>>>>>>>>>> Ports are configured in red5.properties >>>>>>>>>>> HTTP vs HTTPS is being configured in jee*.xml >>>>>>>>>>> >>>>>>>>>>> All other configuration values are in Admin->Config >>>>>>>>>>> >>>>>>>>>>> On Wed, Nov 8, 2017 at 10:53 PM, Tom Luo <mario...@gmail.com> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Is there a similar configuration file like >>>>>>>>>>>> webapps/openmeetings/public/config.xml in OM4.0? >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> >>>>>>>>>>>> Tom >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Nov 8, 2017 at 10:52 AM, Tom Luo <mario...@gmail.com> >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi, Maxim, >>>>>>>>>>>>> >>>>>>>>>>>>> I checked the more up-to-date instructions you sent. It still >>>>>>>>>>>>> lists step 7: >>>>>>>>>>>>> webapps/openmeetings/public/config.xml| >>>>>>>>>>>>> >>>>>>>>>>>>> I understand you said this step is not necessary. However, I >>>>>>>>>>>>> tried to access mydoamin:5443/openmeetings. >>>>>>>>>>>>> I just see an inaccessible error. More important, I tried sudo >>>>>>>>>>>>> netstat -plnt, but nothing is listening at port 5443. >>>>>>>>>>>>> Of course, I started the red5 server. Do you know why? >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks, >>>>>>>>>>>>> >>>>>>>>>>>>> Tom >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Nov 8, 2017 at 1:52 AM, Maxim Solodovnik < >>>>>>>>>>>>> solomax...@gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> This is email from 2016 >>>>>>>>>>>>>> It is not necessary to modify config.xml anymore >>>>>>>>>>>>>> >>>>>>>>>>>>>> These parameters are redundant since 4.0.0 >>>>>>>>>>>>>> <protocol>https</protocol> <red5httpport>5443</red5httpport> >>>>>>>>>>>>>> <rtmpsslport>5443</rtmpsslport> >>>>>>>>>>>>>> These can be set via Admin->Config >>>>>>>>>>>>>> <useSSL>yes</useSSL> <proxyType>none</proxyType> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Here is the thread with more up-to-date instructions: >>>>>>>>>>>>>> http://markmail.org/message/ik4qdhdychl364bp (I haven't >>>>>>>>>>>>>> check them ... ) >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Nov 8, 2017 at 1:33 PM, Tom Luo <mario...@gmail.com> >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi, all, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> In the email: >>>>>>>>>>>>>>> http://openmeetings.markmail.org/message/hqwjnihcfb4tqxkx?q= >>>>>>>>>>>>>>> letsencrypt >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> It said we need to modify >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Edit ../webapps/openmeetings/public/config.xml and set >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> <protocol>https</protocol> <red5httpport>5443</red5httpport> >>>>>>>>>>>>>>> <rtmpsslport>5443</rtmpsslport> <useSSL>yes</useSSL> >>>>>>>>>>>>>>> <proxyType>none</proxyType> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> However, in OM4.0, I cannot find the config.xml file. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> So, which file should I modify? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Tom >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> WBR >>>>>>>>>>>>>> Maxim aka solomax >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> WBR >>>>>>>>>>> Maxim aka solomax >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> WBR >>>>>>>>> Maxim aka solomax >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> WBR >>>>>>> Maxim aka solomax >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> WBR >>>> Maxim aka solomax >>>> >>> >>> >> > -- WBR Maxim aka solomax
