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.su
>>> pport.FileSystemXmlApplicationContext@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/publ
>>>>> ic/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

Reply via email to