Hi, Maxim,

Thanks for your reply.
For whatever reason, it works now:)

Thanks,

Tom


On Thu, May 14, 2020 at 10:46 PM Maxim Solodovnik <solomax...@gmail.com>
wrote:

> Hello Tom,
>
> these lines are from OpenMeetings:
> tcp6       0      0 :::5080                 :::*                    LISTEN
>      2555/java
> tcp6       0      0 :::5443                 :::*                    LISTEN
>      2555/java
>
> How are checking "It is not running"?
>
> On Fri, 15 May 2020 at 03:20, Tom Luo <mario...@gmail.com> wrote:
>
>> Thanks. I did not know Apache2 server is not required.
>> I followed Installation OpenMeetings 5.0.0-M4 on Ubuntu 18.04 LTS.pdf
>> <https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20OpenMeetings%205.0.0-M4%20on%20Ubuntu%2018.04%20LTS.pdf?version=5&modificationDate=1588003937000&api=v2>
>>  and Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4
>> on Ubuntu 18.04.pdf
>> <https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeetings%205.0.0-M4%20on%20Ubuntu%2018.04.pdf?version=1&modificationDate=1587558435000&api=v2>.
>> But Openmeetings still isn't working. I tried "sudo netstat -tulpn |
>> grep LISTEN". Do you have all services listening here? Thanks
>>
>> tcp        0      0 127.0.0.53:53           0.0.0.0:*
>> LISTEN      761/systemd-resolve
>> tcp        0      0 172.26.3.5:3478         0.0.0.0:*
>> LISTEN      2403/turnserver
>> tcp        0      0 127.0.0.1:3478          0.0.0.0:*
>> LISTEN      2403/turnserver
>> tcp        0      0 172.26.3.5:3478         0.0.0.0:*
>> LISTEN      2403/turnserver
>> tcp        0      0 127.0.0.1:3478          0.0.0.0:*
>> LISTEN      2403/turnserver
>> tcp        0      0 0.0.0.0:22              0.0.0.0:*
>> LISTEN      948/sshd
>> tcp        0      0 172.26.3.5:3479         0.0.0.0:*
>> LISTEN      2403/turnserver
>> tcp        0      0 127.0.0.1:3479          0.0.0.0:*
>> LISTEN      2403/turnserver
>> tcp        0      0 172.26.3.5:3479         0.0.0.0:*
>> LISTEN      2403/turnserver
>> tcp        0      0 127.0.0.1:3479          0.0.0.0:*
>> LISTEN      2403/turnserver
>> tcp        0      0 127.0.0.1:3306          0.0.0.0:*
>> LISTEN      1147/mysqld
>> tcp6       0      0 :::80                   :::*
>>  LISTEN      1036/apache2
>> tcp6       0      0 :::22                   :::*
>>  LISTEN      948/sshd
>> tcp6       0      0 ::1:3478                :::*
>>  LISTEN      2403/turnserver
>> tcp6       0      0 ::1:3478                :::*
>>  LISTEN      2403/turnserver
>> tcp6       0      0 ::1:3479                :::*
>>  LISTEN      2403/turnserver
>> tcp6       0      0 ::1:3479                :::*
>>  LISTEN      2403/turnserver
>> tcp6       0      0 :::5080                 :::*
>>  LISTEN      2555/java
>> tcp6       0      0 :::8888                 :::*
>>  LISTEN      2464/kurento-media-
>> tcp6       0      0 :::443                  :::*
>>  LISTEN      1036/apache2
>> tcp6       0      0 :::5443                 :::*
>>  LISTEN      2555/java
>> tcp6       0      0 127.0.0.1:8005          :::*
>>  LISTEN      2555/java
>> tcp6       0      0 :::5701                 :::*
>>  LISTEN      2555/java
>>
>>
>> On Thu, May 14, 2020 at 3:59 PM Juan Antonio Moreno Carmona <
>> jam...@gmail.com> wrote:
>>
>>> Hi Tom.
>>>
>>> Well, actually you don't need Apache2 server to get a functional and
>>> working openmeetings installation. Why do you want to install Apache2?
>>>
>>> Regards.
>>> El 14/5/20 a las 21:52, Tom Luo escribió:
>>>
>>> Hi, all,
>>>
>>> I followed this instruction to set up Letsencrypt and the server.
>>>
>>>
>>> https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeetings%205.0.0-M4%20on%20Ubuntu%2018.04.pdf?version=1&modificationDate=1587558435000&api=v2
>>>
>>> However, this document has never mentioned how to setup Apache2 config
>>> file along with the Letsencrypt certificate.
>>> Does anyone know how?
>>>
>>> Thanks,
>>>
>>> Tom
>>>
>>>
>>>
>
> --
> Best regards,
> Maxim
>

Reply via email to