Re: KMS Crash

[YUP]

KMS server is very unstable in my case too.

On Tue, Apr 21, 2020 at 9:32 AM R. Scholz
 wrote:
>
> Hello,
>
> today I had a manager (a little older one) who try the first time "such
> modern thing like a online-conference".
>
> I sent him an invitation-email and he made three (or more) times a
> doube-click on the link.
> I see his name a lot of in the client-list.
>
> After that I see the red error "no multimedia" (or sth. like that).
>
> I restarted KMS and Tomcat and all is OK again.
>
> Is it possible to avoid that? Maybe only one connection per invitation?
>
> Best regards,
>
> René
>

Re: OM Moodle plugin: What is the frame Comments for?

[YUP]

Thanks, appreciate it.

On Sat, Apr 11, 2020, 10:17 Maxim Solodovnik  wrote:

> Got notification :))
> Will see what I can do
>
> On Sat, Apr 11, 2020, 13:35 YUP  wrote:
>
>> Good to know... I filled out the feature request. Thanks!
>>
>> Best,
>> Yarema
>>
>> On Sat, Apr 11, 2020 at 4:19 AM Maxim Solodovnik 
>> wrote:
>> >
>> > Hello Yarema,
>> >
>> > AFAIK room description is displayed in room list only
>> > This part of UI is useless for Moodle users (they have access to room
>> only)
>> >
>> > Recordings doesn't have "Comment" DB field, so it can't be displayed
>> for recordings as well
>> > I guess this might be the area of improvement
>> >
>> > On Sat, 11 Apr 2020 at 05:25, YUP  wrote:
>> >>
>> >> Hi Maxim,
>> >> When adding openmeetings session to my course I see frame Comment.
>> >> What is this frame for? Sometimes I need to add a short description to
>> >> video session, can I use it somehow? Usually activities have
>> >> description frame which can be displayed in the main page of the
>> >> course. This feature in OM Moodle plugin will be very useful for
>> >> teacher.
>> >>
>> >> Regards,
>> >> Yarema
>> >
>> >
>> >
>> > --
>> > Best regards,
>> > Maxim
>>
>

Re: OM Moodle plugin: What is the frame Comments for?

[YUP]

Good to know... I filled out the feature request. Thanks!

Best,
Yarema

On Sat, Apr 11, 2020 at 4:19 AM Maxim Solodovnik  wrote:
>
> Hello Yarema,
>
> AFAIK room description is displayed in room list only
> This part of UI is useless for Moodle users (they have access to room only)
>
> Recordings doesn't have "Comment" DB field, so it can't be displayed for 
> recordings as well
> I guess this might be the area of improvement
>
> On Sat, 11 Apr 2020 at 05:25, YUP  wrote:
>>
>> Hi Maxim,
>> When adding openmeetings session to my course I see frame Comment.
>> What is this frame for? Sometimes I need to add a short description to
>> video session, can I use it somehow? Usually activities have
>> description frame which can be displayed in the main page of the
>> course. This feature in OM Moodle plugin will be very useful for
>> teacher.
>>
>> Regards,
>> Yarema
>
>
>
> --
> Best regards,
> Maxim

OM Moodle plugin: What is the frame Comments for?

[YUP]

Hi Maxim,
When adding openmeetings session to my course I see frame Comment.
What is this frame for? Sometimes I need to add a short description to
video session, can I use it somehow? Usually activities have
description frame which can be displayed in the main page of the
course. This feature in OM Moodle plugin will be very useful for
teacher.

Regards,
Yarema

Re: General questions about DMZ, https, apache web server, single Interent IP address

[YUP]

Yes, I would like to confirm that it is (still) impossible to use only
one tcp port for OM.  You should also have UDP ports open in your
firewall, it is a requirement :(

I even tried to use udptunnel which can operate on tcp port to handle
upd flow, but my attempt was unsuccessful too.

On Mon, Apr 6, 2020 at 4:42 PM Maxim Solodovnik  wrote:
>
> Hello George,
>
> Welcome back :)
> I'm not sure about "any Video Conferencing systems"
> OM 4.0.10 will work almost the same as 2.0.x (it will additionally require 
> websocket connection on the same port as OM) [will use Flash]
> OM 5.0.x CAN work be set up to work over single SSL port but additional 
> server for TURN will be required :(
>
> @Yarema, at this ML try to get everything configured via single HTTPS port, 
> but this seems to be impossible
>
> On Mon, 6 Apr 2020 at 05:30, Kirkham, George  
> wrote:
>>
>> Hi,
>>
>> Background
>>
>> Reading about Jitsi and BigBlueButton, it seems the underlying software they 
>> the use required "direct connection to the internet" and exclusive use of 
>> port 443.
>>
>> While my infrastructure has a single external IP address, Router that 
>> changes Internet facing IP address to internal IP address, DMZ via NAT 
>> firewall which handles UPD, changing IP address to yet another IP address. 
>> This is a common configuration for small business.
>> I also have an Apache Web server which uses both port 80 and port 433. I 
>> believe while you can redirect port 80 traffic to another server, because 
>> port 443 traffic is encrypted, it cannot be redirected. The above two 
>> systems do not use Apache, but do want to have use of port 443.
>>
>> Reading documentation for Openmeetings which pointed to Kurento Media Server 
>> documetation: "If Kurento Media Server, its Application Server, or any of 
>> the clients are located behind a NAT, you need to use a STUN or a TURN 
>> server in order to achieve NAT traversal."
>>
>>
>> Questions
>>
>> Is there any Video Conferencing systems that can work from inside a NAT DMZ 
>> ?  Note: I used to use OpenMeeting 2.0 quite effectively inside a NAT DMZ, 
>> and because it did not require the use of  port 443, it ran nicely in our 
>> environment.
>>
>> Would OpenMeetings work in Debian 10 (Buster) environment, it did work in 
>> Debian Squeeze, but a lot of underlying software has been updated since that 
>> time?
>>
>> Does OpenMeetings work in a single Docker container?   (not that I use 
>> Docker). I have seen some implementations of the above to systems where part 
>> of the system is in side Docker but not the WebRTC component.
>>
>> Any useful thoughts on the above ?
>>
>> Regards,
>>
>> George.
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> Best regards,
> Maxim

Re: no audio, no video for remote user - works only locally

[YUP]

Not enough, you also need to open UDP ports. And check that firewall
doesn't reject udp requests.

On Fri, Apr 3, 2020 at 6:17 PM Geffert, Otfried  wrote:
>
>
> Yes.
> I opened two ports on the server: 5443 
>
> Otfried
>
> - Original Message -
> From: "Maxim Solodovnik" 
> To: "user" 
> Sent: Friday, 3 April, 2020 18:14:19
> Subject: Re: no audio, no video for remote user - works only locally
>
> any firewalls involved?
>
> On Fri, 3 Apr 2020 at 23:13, Alvaro  wrote:
>
> > ...i mean:  turnserver.conf
> >
> >
> > ..
> >
> >
> > El vie, 03-04-2020 a las 18:09 +0200, Alvaro escribió:
> > > ...in Centos 7 turn.config file is in:
> > >
> > > /etc/coturn
> > >
> > >
> > > .
> > >
> > >
> > > El vie, 03-04-2020 a las 18:01 +0200, Geffert, Otfried escribió:
> > > > Hi Maxim,
> > > >
> > > > thanks for the quick reply !
> > > >
> > > > He used several browsers, started with Safari, then Firefox, then
> > > > Chrome.
> > > > Regarding audio & video: same behaviour.
> > > >
> > > > Best regartds,
> > > > Otfried
> > > >
> > > > - Original Message -
> > > > From: "Maxim Solodovnik" 
> > > > To: "user" 
> > > > Sent: Friday, 3 April, 2020 17:53:36
> > > > Subject: Re: no audio, no video for remote user - works only
> > > > locally
> > > >
> > > > Hello,
> > > >
> > > > what browser your colleague with Mac is using? Safari? Is it better
> > > > with
> > > > some other browser?
> > > > Do you have TURN server configured? (or you both under the same
> > > > NAt?)
> > > >
> > > >
> > > > On Fri, 3 Apr 2020 at 22:41, Geffert, Otfried  > > > .d
> > > > e>
> > > > wrote:
> > > >
> > > > > Dear all,
> > > > >
> > > > > I installed OpenMeetings 5.0.0-M3 on a fresh CentOS 7
> > > > > following Alvaro Bustos detailed installation pdf.
> > > > >
> > > > > Installation as such worked fine, :-)
> > > > > Audio & video locally works fine.
> > > > > I was suprised of the rich functionality.
> > > > >
> > > > > But testing it with a colleague ( who has a Mac )
> > > > > never gave us the audio and video of the other person -
> > > > > even after one hour of poking around.
> > > > >
> > > > > Locally it worked for him, he could see his picture and the adio
> > > > > level
> > > > > was going up/down for him.
> > > > > The same happened on my side :-(
> > > > >
> > > > > I have no idea of what is wrong.
> > > > > Can someone give a hint ?
> > > > >
> > > > > Best regards,
> > > > > Otfried
> > > > >
> > > > > --
> > > > > Otfried Geffert
> > > > > Hard~ & Software Engineer @ DESYs CFEL theory group
> > > > > __https://desy-theory.cfel.de/
> > > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Maxim
> >
>
>
> --
> Best regards,
> Maxim
> --
> Otfried Geffert
> Hard~ & Software Engineer @ DESYs CFEL theory group, Tel. +49 40 8998-6312
> __https://desy-theory.cfel.de/

Re: inconsistencies between browsers/OSs

[YUP]

Hi, it could be a problem of UDP ports. Can you check whether UDP
ports are open or close in your firewall?
Regards,
Yarema

On Thu, Apr 2, 2020 at 9:10 PM Orm Finnendahl
 wrote:
>
> Hi,
>
>  finally our OM server is working with https behind the firewall and
> NAT, ldap ist working too and we were able to succefully establish a
> stable conference between two linux boxes running firefox with
> audio/video (yey!).
>
> om is really amazing work, thanks to everyone, who contributed!
>
> Unfortunately we get varying success regarding audio/video with other
> OS/browser combinations: On OSX it seems to work with firefox but with
> Safari audio/video works locally, but the remote linux user is
> invisible/inaudible for the OSX user. With other OSX users and on a
> Windows/Firefox <-> Linux/Firefox combination, video and audio of the
> other side isn't working on both machines, etc...
>
> Is this a known issue? I searched the ML archives and the Web and
> couldn't find relevant information. Are there any recommendations how
> to troubleshoot the problems?
>
> It seems quite inconsistent and I don't know yet whether it's a setup
> problem on the user's/administrator's side. All participants of two
> part conferences state that they see their own audio/video and see the
> empty video frame of the other participant whitout hearing anything
> although seeing the green button of the other participant flash.
>
> We are using 5.0.0-M3, Revision b739f87
>
> --
> Orm

Re: Openmeetings Docker behind reverse proxy

[YUP]

Hi,
Please try my config for proxy pass in nginx. My nginx listen port
2443 with ssl, openmeetings runs in docker with standart ports
exposed:

server {
listen   2443 ssl http2;
listen [::]:2443 ssl http2;
server_name  localhost;

  location /openmeetings {
proxy_pass https://localhost:5443/openmeetings;
proxy_set_header Host $host;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}

You can also add kurento if you wish:

location /kurento {
# prevents 502 bad gateway error
proxy_buffers 8 32k;
proxy_buffer_size 64k;
# redirect all HTTP traffic to localhost:8088;
proxy_pass http://127.0.0.1:/kurento;
# enables WS support
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_read_timeout 9;
}

On Thu, Apr 2, 2020 at 3:01 PM Arndt, Wolfgang  wrote:
>
> Hi,
>
> when i read this right i have to modify conf/jee-container.xml
>
> in the container.
>
> I cannot find a file like that in there.
>
>
>
> Second: I have to proxy websockets, too.
>
>
>
> I have no idea, how to doi this with 
> https://github.com/nginx-proxy/nginx-proxy
>
>
>
> Wolfgang
>
>
>
>
>
>
>
>
>
>
> Von: Maxim Solodovnik 
> Gesendet: Donnerstag, 2. April 2020 13:51
> An: Openmeetings user-list 
> Betreff: Re: Openmeetings Docker behind reverse proxy
>
>
>
> https://stackoverflow.com/questions/51721771/apache-openmeetings-4-0-4-csrf-attack-when-using-apache2-as-proxypass
>
> + search in this ML :)))
>
>
>
> On Thu, 2 Apr 2020 at 18:19, Arndt, Wolfgang  wrote:
>
> Hi,
>
> my Openmeetings docker is working now. So i took the next step:
>
>
>
> I use the nginx-letsencrypt ssl proxy 
> (https://hub.docker.com/r/jrcs/letsencrypt-nginx-proxy-companion/) to 
> auto-generate certs. This is working with other containers.
>
>
>
> As in the grafana expample from the page above , i start the OM-Docker 
> container with an additional -e "VIRTUAL_PORT=5080"
>
>
>
> Now i can connect via the proxy to my OM container, the login page opens but 
> i cannot login.
>
>
>
>
>
> INFO  04-02 10:59:37.346 o.a.w.p.h.CsrfPreventionRequestCycleListener:779 
> [nio-5080-exec-6] - Possible CSRF attack, request URL: 
> http://om.x.de/openmeetings/wicket/bookmarkable/org.apache.openmeetings.web.pages.auth.SignInPage,
>  Origin: https://om.x.de, action: aborted with error 400 Origin does not 
> correspond to request
>
>
>
>
>
> Wolfgang
>
>
>
>
> --
>
> WBR
> Maxim aka solomax

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[YUP]

Moment, do you use turn for OM or for KMS?


On Tue, Mar 31, 2020 at 8:07 PM Maxim Solodovnik 
wrote:

> as well as demo-next
>
> On Wed, 1 Apr 2020 at 01:06, Maxim Solodovnik 
> wrote:
>
>> OM docker doen't have turn URL in KMS configs
>>
>> On Wed, 1 Apr 2020 at 01:05, YUP  wrote:
>>
>>> Can you check if kurento server knows about turn server:
>>> docker exec -it OM_container_id bash
>>> grep turnURL /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini
>>> It should show uncommented turnURL
>>>
>>> On Tue, Mar 31, 2020 at 7:45 PM Maxim Solodovnik 
>>> wrote:
>>>
>>>> can you remove mon/max ports?
>>>>
>>>> On Wed, 1 Apr 2020 at 00:43, Arndt, Wolfgang 
>>>> wrote:
>>>>
>>>>> Demo works
>>>>>
>>>>>
>>>>>
>>>>> *Von:* Maxim Solodovnik 
>>>>> *Gesendet:* Dienstag, 31. März 2020 19:32
>>>>> *An:* Openmeetings user-list 
>>>>> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>>>>>
>>>>>
>>>>>
>>>>> yep,
>>>>>
>>>>> its puzzling
>>>>>
>>>>>
>>>>>
>>>>> well, I'm out of ideas :(
>>>>>
>>>>>
>>>>>
>>>>> can you check if demo-next works for you?
>>>>>
>>>>>
>>>>>
>>>>> On Wed, 1 Apr 2020 at 00:30, Arndt, Wolfgang 
>>>>> wrote:
>>>>>
>>>>> With chrom no picture, too,
>>>>>
>>>>>
>>>>>
>>>>> I cannot interprete chrome://webrtc-internals
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *Von:* Maxim Solodovnik 
>>>>> *Gesendet:* Dienstag, 31. März 2020 19:25
>>>>> *An:* Openmeetings user-list 
>>>>> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>>>>>
>>>>>
>>>>>
>>>>> Is it browser independent?
>>>>>
>>>>> Any insite from chrome://webrtc-internals ?
>>>>>
>>>>>
>>>>>
>>>>> On Wed, 1 Apr 2020 at 00:22, YUP  wrote:
>>>>>
>>>>> add realm too. Sometime coturn doesn't work without real parameter.
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Mar 31, 2020 at 7:12 PM Maxim Solodovnik 
>>>>> wrote:
>>>>>
>>>>> please add this `lt-cred-mech` param and restart coturn
>>>>>
>>>>>
>>>>>
>>>>> On Wed, 1 Apr 2020 at 00:09, Arndt, Wolfgang 
>>>>> wrote:
>>>>>
>>>>> Now i have exactly your config.
>>>>>
>>>>> No OM picture ☹
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Mit freundlichem Gruß
>>>>> Wolfgang Arndt
>>>>> Leiter des EDV-Service
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Lernen fördern Unternehmensverbund
>>>>> Breite Straße 4-6
>>>>> 49477 Ibbenbüren
>>>>> Fon 05451 99916-201
>>>>> Fax 02572 95010
>>>>> www.lernenfoerdern.de
>>>>> ar...@lernenfoerdern.de
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Lernen fördern e. V., Kreisverband Steinfurt
>>>>>
>>>>> Sitz: Breite Straße 10, 49477 Ibbenbüren | Geschäftsführender
>>>>> Vorstand: Bernhard Jäschke, Ludger Lünenborg
>>>>> Registergericht: Amtsgericht Steinfurt | Registernummer: VR 10644
>>>>>
>>>>> - Zugelassener Träger der Arbeitsförderung nach AZAV -
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Kinderland gGmbH
>>>>>
>>>>> Sitz: Breite Straße 10, 49477 Ibbenbüren | Geschäftsführer: Bernhard
>>>>> Jäschke
>>>>> Gesellschafter: Lernen fördern e.V. | Registergericht: Amtsgericht
>>>>> Steinfurt | Registernummer: HRB 5682
>>>>>
>

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[YUP]

Can you check if kurento server knows about turn server:
docker exec -it OM_container_id bash
grep turnURL /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini
It should show uncommented turnURL

On Tue, Mar 31, 2020 at 7:45 PM Maxim Solodovnik 
wrote:

> can you remove mon/max ports?
>
> On Wed, 1 Apr 2020 at 00:43, Arndt, Wolfgang 
> wrote:
>
>> Demo works
>>
>>
>>
>> *Von:* Maxim Solodovnik 
>> *Gesendet:* Dienstag, 31. März 2020 19:32
>> *An:* Openmeetings user-list 
>> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>>
>>
>>
>> yep,
>>
>> its puzzling
>>
>>
>>
>> well, I'm out of ideas :(
>>
>>
>>
>> can you check if demo-next works for you?
>>
>>
>>
>> On Wed, 1 Apr 2020 at 00:30, Arndt, Wolfgang 
>> wrote:
>>
>> With chrom no picture, too,
>>
>>
>>
>> I cannot interprete chrome://webrtc-internals
>>
>>
>>
>>
>>
>>
>>
>> *Von:* Maxim Solodovnik 
>> *Gesendet:* Dienstag, 31. März 2020 19:25
>> *An:* Openmeetings user-list 
>> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>>
>>
>>
>> Is it browser independent?
>>
>> Any insite from chrome://webrtc-internals ?
>>
>>
>>
>> On Wed, 1 Apr 2020 at 00:22, YUP  wrote:
>>
>> add realm too. Sometime coturn doesn't work without real parameter.
>>
>>
>>
>> On Tue, Mar 31, 2020 at 7:12 PM Maxim Solodovnik 
>> wrote:
>>
>> please add this `lt-cred-mech` param and restart coturn
>>
>>
>>
>> On Wed, 1 Apr 2020 at 00:09, Arndt, Wolfgang 
>> wrote:
>>
>> Now i have exactly your config.
>>
>> No OM picture ☹
>>
>>
>>
>>
>>
>>
>>
>> Mit freundlichem Gruß
>> Wolfgang Arndt
>> Leiter des EDV-Service
>>
>>
>>
>>
>>
>> Lernen fördern Unternehmensverbund
>> Breite Straße 4-6
>> 49477 Ibbenbüren
>> Fon 05451 99916-201
>> Fax 02572 95010
>> www.lernenfoerdern.de
>> ar...@lernenfoerdern.de
>>
>>
>>
>>
>>
>>
>>
>> Lernen fördern e. V., Kreisverband Steinfurt
>>
>> Sitz: Breite Straße 10, 49477 Ibbenbüren | Geschäftsführender Vorstand:
>> Bernhard Jäschke, Ludger Lünenborg
>> Registergericht: Amtsgericht Steinfurt | Registernummer: VR 10644
>>
>> - Zugelassener Träger der Arbeitsförderung nach AZAV -
>>
>>
>>
>>
>>
>> Kinderland gGmbH
>>
>> Sitz: Breite Straße 10, 49477 Ibbenbüren | Geschäftsführer: Bernhard
>> Jäschke
>> Gesellschafter: Lernen fördern e.V. | Registergericht: Amtsgericht
>> Steinfurt | Registernummer: HRB 5682
>>
>>
>>
>>
>>
>> Lernen fördern - Dienstleistungen gGmbH
>>
>> Sitz: Breite Straße 10, 49477 Ibbenbüren | Geschäftsführer: Bernhard
>> Jäschke, Ludger Lünenborg
>> Gesellschafter: Lernen fördern e. V. | Registergericht: Amtsgericht
>> Steinfurt | Registernummer: HRB 6025
>>
>>
>>
>>
>>
>> Top-Arbeitgeber im Kreis Steinfurt | Betriebsplus 5.0
>>
>> Mitglied im Paritätischen
>>
>> Zertifiziertes Energiemanagementsystem DIN EN ISO 50001
>>
>>
>>
>> *Von:* Maxim Solodovnik 
>> *Gesendet:* Dienstag, 31. März 2020 18:58
>> *An:* Openmeetings user-list 
>> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>>
>>
>>
>> OK
>>
>>
>>
>> Here is your config
>>
>> listening-port=3478
>>
>> verbose
>>
>> fingerprint
>>
>> user=kurento:kurento
>>
>> simple-log
>>
>> log-file=/var/log/turn.log
>>
>> min-port=49152
>>
>> max-port=55000
>>
>>
>>
>> Here is what I propose to try:
>>
>> listening-port=3478
>>
>> verbose
>>
>> fingerprint
>>
>> use-auth-secret
>>
>> static-auth-secret=somegibberishtext
>>
>> simple-log
>>
>> log-file=/var/log/turn.log
>>
>> min-port=49152
>>
>> max-port=55000
>>
>>
>>
>> I also have this param, but everything should work without it
>>
>> realm=subdomain.domain.xxx
>>
>>
>>
>> then:
>>
>> OM params:
>>
>> turn_url - same
>>
>> turn_user=any###you can use john or kurento or whatever
>>
>> turn_pass=somegibberishtext
>>
>>
>

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[YUP]

check kurento logs in the time whren you use it:
ls /var/log/kurento-media-server
tail -f /var/log/log_file_of_the_kureno_server


On Tue, Mar 31, 2020 at 7:36 PM Arndt, Wolfgang 
wrote:

> root@bd041c4c8805:/opt# ps xuaw | grep kurento
>
> nobody 501  0.1  0.2 2709200 37628 ?   Sl   17:05   0:02
> /usr/bin/kurento-media-server
>
>
>
>
>
>
>
> *Von:* YUP 
> *Gesendet:* Dienstag, 31. März 2020 19:34
> *An:* user@openmeetings.apache.org
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> Are you sure  kurento is working?
>
>
>
> sudo docker container ls
>
> find openmeetings container
>
> sudo docker -it openmeetings_container_id bash
>
> Enter bash, check if kurento working:
>
> ps xuaw | grep kurento
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Tue, Mar 31, 2020 at 7:30 PM Arndt, Wolfgang 
> wrote:
>
> With chrom no picture, too,
>
>
>
> I cannot interprete chrome://webrtc-internals
>
>
>
>
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Dienstag, 31. März 2020 19:25
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> Is it browser independent?
>
> Any insite from chrome://webrtc-internals ?
>
>
>
> On Wed, 1 Apr 2020 at 00:22, YUP  wrote:
>
> add realm too. Sometime coturn doesn't work without real parameter.
>
>
>
> On Tue, Mar 31, 2020 at 7:12 PM Maxim Solodovnik 
> wrote:
>
> please add this `lt-cred-mech` param and restart coturn
>
>
>
> On Wed, 1 Apr 2020 at 00:09, Arndt, Wolfgang 
> wrote:
>
> Now i have exactly your config.
>
> No OM picture ☹
>
>
>
>
>
>
>
> Mit freundlichem Gruß
> Wolfgang Arndt
> Leiter des EDV-Service
>
>
>
>
>
> Lernen fördern Unternehmensverbund
> Breite Straße 4-6
> 49477 Ibbenbüren
> Fon 05451 99916-201
> Fax 02572 95010
> www.lernenfoerdern.de
> ar...@lernenfoerdern.de
>
>
>
>
>
>
>
> Lernen fördern e. V., Kreisverband Steinfurt
>
> Sitz: Breite Straße 10, 49477 Ibbenbüren | Geschäftsführender Vorstand:
> Bernhard Jäschke, Ludger Lünenborg
> Registergericht: Amtsgericht Steinfurt | Registernummer: VR 10644
>
> - Zugelassener Träger der Arbeitsförderung nach AZAV -
>
>
>
>
>
> Kinderland gGmbH
>
> Sitz: Breite Straße 10, 49477 Ibbenbüren | Geschäftsführer: Bernhard
> Jäschke
> Gesellschafter: Lernen fördern e.V. | Registergericht: Amtsgericht
> Steinfurt | Registernummer: HRB 5682
>
>
>
>
>
> Lernen fördern - Dienstleistungen gGmbH
>
> Sitz: Breite Straße 10, 49477 Ibbenbüren | Geschäftsführer: Bernhard
> Jäschke, Ludger Lünenborg
> Gesellschafter: Lernen fördern e. V. | Registergericht: Amtsgericht
> Steinfurt | Registernummer: HRB 6025
>
>
>
>
>
> Top-Arbeitgeber im Kreis Steinfurt | Betriebsplus 5.0
>
> Mitglied im Paritätischen
>
> Zertifiziertes Energiemanagementsystem DIN EN ISO 50001
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Dienstag, 31. März 2020 18:58
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> OK
>
>
>
> Here is your config
>
> listening-port=3478
>
> verbose
>
> fingerprint
>
> user=kurento:kurento
>
> simple-log
>
> log-file=/var/log/turn.log
>
> min-port=49152
>
> max-port=55000
>
>
>
> Here is what I propose to try:
>
> listening-port=3478
>
> verbose
>
> fingerprint
>
> use-auth-secret
>
> static-auth-secret=somegibberishtext
>
> simple-log
>
> log-file=/var/log/turn.log
>
> min-port=49152
>
> max-port=55000
>
>
>
> I also have this param, but everything should work without it
>
> realm=subdomain.domain.xxx
>
>
>
> then:
>
> OM params:
>
> turn_url - same
>
> turn_user=any###you can use john or kurento or whatever
>
> turn_pass=somegibberishtext
>
>
>
> On Tue, 31 Mar 2020 at 23:49, Arndt, Wolfgang 
> wrote:
>
> In that config there are no user infos…
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Dienstag, 31. März 2020 18:48
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> turn_url will be the same
>
> turn_user and turn_pass are per your choice :)
>
>
>
> On Tue, 31 Mar 2020 at 23:46, Arndt, Wolfgang 
> wrote:
>
> I have to restart them om container,too.
>
>
> How do i set the env parameters for that?
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Dienstag, 31. März 2020 18:42

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[YUP]

Are you sure  kurento is working?

sudo docker container ls
find openmeetings container
sudo docker -it openmeetings_container_id bash
Enter bash, check if kurento working:
ps xuaw | grep kurento






On Tue, Mar 31, 2020 at 7:30 PM Arndt, Wolfgang 
wrote:

> With chrom no picture, too,
>
>
>
> I cannot interprete chrome://webrtc-internals
>
>
>
>
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Dienstag, 31. März 2020 19:25
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> Is it browser independent?
>
> Any insite from chrome://webrtc-internals ?
>
>
>
> On Wed, 1 Apr 2020 at 00:22, YUP  wrote:
>
> add realm too. Sometime coturn doesn't work without real parameter.
>
>
>
> On Tue, Mar 31, 2020 at 7:12 PM Maxim Solodovnik 
> wrote:
>
> please add this `lt-cred-mech` param and restart coturn
>
>
>
> On Wed, 1 Apr 2020 at 00:09, Arndt, Wolfgang 
> wrote:
>
> Now i have exactly your config.
>
> No OM picture ☹
>
>
>
>
>
>
>
> Mit freundlichem Gruß
> Wolfgang Arndt
> Leiter des EDV-Service
>
>
>
>
>
> Lernen fördern Unternehmensverbund
> Breite Straße 4-6
> 49477 Ibbenbüren
> Fon 05451 99916-201
> Fax 02572 95010
> www.lernenfoerdern.de
> ar...@lernenfoerdern.de
>
>
>
>
>
>
>
> Lernen fördern e. V., Kreisverband Steinfurt
>
> Sitz: Breite Straße 10, 49477 Ibbenbüren | Geschäftsführender Vorstand:
> Bernhard Jäschke, Ludger Lünenborg
> Registergericht: Amtsgericht Steinfurt | Registernummer: VR 10644
>
> - Zugelassener Träger der Arbeitsförderung nach AZAV -
>
>
>
>
>
> Kinderland gGmbH
>
> Sitz: Breite Straße 10, 49477 Ibbenbüren | Geschäftsführer: Bernhard
> Jäschke
> Gesellschafter: Lernen fördern e.V. | Registergericht: Amtsgericht
> Steinfurt | Registernummer: HRB 5682
>
>
>
>
>
> Lernen fördern - Dienstleistungen gGmbH
>
> Sitz: Breite Straße 10, 49477 Ibbenbüren | Geschäftsführer: Bernhard
> Jäschke, Ludger Lünenborg
> Gesellschafter: Lernen fördern e. V. | Registergericht: Amtsgericht
> Steinfurt | Registernummer: HRB 6025
>
>
>
>
>
> Top-Arbeitgeber im Kreis Steinfurt | Betriebsplus 5.0
>
> Mitglied im Paritätischen
>
> Zertifiziertes Energiemanagementsystem DIN EN ISO 50001
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Dienstag, 31. März 2020 18:58
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> OK
>
>
>
> Here is your config
>
> listening-port=3478
>
> verbose
>
> fingerprint
>
> user=kurento:kurento
>
> simple-log
>
> log-file=/var/log/turn.log
>
> min-port=49152
>
> max-port=55000
>
>
>
> Here is what I propose to try:
>
> listening-port=3478
>
> verbose
>
> fingerprint
>
> use-auth-secret
>
> static-auth-secret=somegibberishtext
>
> simple-log
>
> log-file=/var/log/turn.log
>
> min-port=49152
>
> max-port=55000
>
>
>
> I also have this param, but everything should work without it
>
> realm=subdomain.domain.xxx
>
>
>
> then:
>
> OM params:
>
> turn_url - same
>
> turn_user=any###you can use john or kurento or whatever
>
> turn_pass=somegibberishtext
>
>
>
> On Tue, 31 Mar 2020 at 23:49, Arndt, Wolfgang 
> wrote:
>
> In that config there are no user infos…
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Dienstag, 31. März 2020 18:48
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> turn_url will be the same
>
> turn_user and turn_pass are per your choice :)
>
>
>
> On Tue, 31 Mar 2020 at 23:46, Arndt, Wolfgang 
> wrote:
>
> I have to restart them om container,too.
>
>
> How do i set the env parameters for that?
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Dienstag, 31. März 2020 18:42
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> Please try config from here https://markmail.org/message/3dgy62lj3m74mogy
>
>
>
> On Tue, 31 Mar 2020 at 23:40, Arndt, Wolfgang 
> wrote:
>
> This is my coturn config.
>
>
>
> listening-port=3478
>
> verbose
>
> fingerprint
>
> user=kurento:kurento
>
> simple-log
>
> log-file=/var/log/turn.log
>
> min-port=49152
>
> max-port=55000
>
>
>
>
>
> I started a docker container with
>
>
>
> docker run -d --network=host \
>
> -v $(pwd)/my.conf:/etc/coturn/turnserver.c

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[YUP]

add realm too. Sometime coturn doesn't work without real parameter.

On Tue, Mar 31, 2020 at 7:12 PM Maxim Solodovnik 
wrote:

> please add this `lt-cred-mech` param and restart coturn
>
> On Wed, 1 Apr 2020 at 00:09, Arndt, Wolfgang 
> wrote:
>
>> Now i have exactly your config.
>>
>> No OM picture ☹
>>
>>
>>
>>
>>
>>
>>
>> Mit freundlichem Gruß
>> Wolfgang Arndt
>> Leiter des EDV-Service
>>
>>
>>
>>
>>
>> Lernen fördern Unternehmensverbund
>> Breite Straße 4-6
>> 49477 Ibbenbüren
>> Fon 05451 99916-201
>> Fax 02572 95010
>> www.lernenfoerdern.de
>> ar...@lernenfoerdern.de
>>
>>
>>
>>
>>
>>
>>
>> Lernen fördern e. V., Kreisverband Steinfurt
>>
>> Sitz: Breite Straße 10, 49477 Ibbenbüren | Geschäftsführender Vorstand:
>> Bernhard Jäschke, Ludger Lünenborg
>> Registergericht: Amtsgericht Steinfurt | Registernummer: VR 10644
>>
>> - Zugelassener Träger der Arbeitsförderung nach AZAV -
>>
>>
>>
>>
>>
>> Kinderland gGmbH
>>
>> Sitz: Breite Straße 10, 49477 Ibbenbüren | Geschäftsführer: Bernhard
>> Jäschke
>> Gesellschafter: Lernen fördern e.V. | Registergericht: Amtsgericht
>> Steinfurt | Registernummer: HRB 5682
>>
>>
>>
>>
>>
>> Lernen fördern - Dienstleistungen gGmbH
>>
>> Sitz: Breite Straße 10, 49477 Ibbenbüren | Geschäftsführer: Bernhard
>> Jäschke, Ludger Lünenborg
>> Gesellschafter: Lernen fördern e. V. | Registergericht: Amtsgericht
>> Steinfurt | Registernummer: HRB 6025
>>
>>
>>
>>
>>
>> Top-Arbeitgeber im Kreis Steinfurt | Betriebsplus 5.0
>>
>> Mitglied im Paritätischen
>>
>> Zertifiziertes Energiemanagementsystem DIN EN ISO 50001
>>
>>
>>
>> *Von:* Maxim Solodovnik 
>> *Gesendet:* Dienstag, 31. März 2020 18:58
>> *An:* Openmeetings user-list 
>> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>>
>>
>>
>> OK
>>
>>
>>
>> Here is your config
>>
>> listening-port=3478
>>
>> verbose
>>
>> fingerprint
>>
>> user=kurento:kurento
>>
>> simple-log
>>
>> log-file=/var/log/turn.log
>>
>> min-port=49152
>>
>> max-port=55000
>>
>>
>>
>> Here is what I propose to try:
>>
>> listening-port=3478
>>
>> verbose
>>
>> fingerprint
>>
>> use-auth-secret
>>
>> static-auth-secret=somegibberishtext
>>
>> simple-log
>>
>> log-file=/var/log/turn.log
>>
>> min-port=49152
>>
>> max-port=55000
>>
>>
>>
>> I also have this param, but everything should work without it
>>
>> realm=subdomain.domain.xxx
>>
>>
>>
>> then:
>>
>> OM params:
>>
>> turn_url - same
>>
>> turn_user=any###you can use john or kurento or whatever
>>
>> turn_pass=somegibberishtext
>>
>>
>>
>> On Tue, 31 Mar 2020 at 23:49, Arndt, Wolfgang 
>> wrote:
>>
>> In that config there are no user infos…
>>
>>
>>
>> *Von:* Maxim Solodovnik 
>> *Gesendet:* Dienstag, 31. März 2020 18:48
>> *An:* Openmeetings user-list 
>> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>>
>>
>>
>> turn_url will be the same
>>
>> turn_user and turn_pass are per your choice :)
>>
>>
>>
>> On Tue, 31 Mar 2020 at 23:46, Arndt, Wolfgang 
>> wrote:
>>
>> I have to restart them om container,too.
>>
>>
>> How do i set the env parameters for that?
>>
>>
>>
>> *Von:* Maxim Solodovnik 
>> *Gesendet:* Dienstag, 31. März 2020 18:42
>> *An:* Openmeetings user-list 
>> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>>
>>
>>
>> Please try config from here https://markmail.org/message/3dgy62lj3m74mogy
>>
>>
>>
>> On Tue, 31 Mar 2020 at 23:40, Arndt, Wolfgang 
>> wrote:
>>
>> This is my coturn config.
>>
>>
>>
>> listening-port=3478
>>
>> verbose
>>
>> fingerprint
>>
>> user=kurento:kurento
>>
>> simple-log
>>
>> log-file=/var/log/turn.log
>>
>> min-port=49152
>>
>> max-port=55000
>>
>>
>>
>>
>>
>> I started a docker container with
>>
>>
>>
>> docker run -d --network=host \
>>
>> -v $(pwd)/my.conf:/etc/coturn/turnserver.conf \
>>
>> instrumentisto/coturn
>>
>>
>>
>>
>>
>> No picture in OM.
>>
>>
>>
>>
>>
>> *Von:* Maxim Solodovnik 
>> *Gesendet:* Dienstag, 31. März 2020 18:37
>> *An:* Openmeetings user-list 
>> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>>
>>
>>
>> So you added missing params to coturn config
>>
>> restarted it
>>
>> And there is no picture in OM?
>>
>>
>>
>> On Tue, 31 Mar 2020 at 23:33, Arndt, Wolfgang 
>> wrote:
>>
>> No changes. It is not working!
>>
>>
>>
>> Test on
>> https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/
>> is working
>>
>>
>>
>> I get 8 candidates the last 4 are my home external ip and my office
>> external ip. with 2 udp ports
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> WBR
>> Maxim aka solomax
>>
>>
>>
>>
>> --
>>
>> WBR
>> Maxim aka solomax
>>
>>
>>
>>
>> --
>>
>> WBR
>> Maxim aka solomax
>>
>>
>>
>>
>> --
>>
>> WBR
>> Maxim aka solomax
>>
>
>
> --
> WBR
> Maxim aka solomax
>

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[YUP]

Hi,
You should check open ports in your firewall, both tcp and udp. At
least those needed for normal run of OM+kurento:
3478 TCP-UDP IN
5443 TCP IN
 TCP IN
49152:65535 UDP IN-OUT
You can do it using nmap.
My OM is behind office firewall too and I experienced the same
behavior. In my case only 443 port is open and all UDP are closed.

On Tue, Mar 31, 2020 at 4:31 PM Arndt, Wolfgang  wrote:
>
> Hi @ all,
>
>
>
> i wanted to setup our own openmeetings server with docker.
>
>
>
> I try for days now to get it working, but it drives me mad now.
>
> I read a lot of documentation but i cannot find the right way.
>
>
>
> Our Network:
>
> Dockerserver has ip: 10.50.100.13 and is behind a pfsense firewall with nat 
> in our office
>
>
>
>
>
> My Homeoffice-PC and a laptop (corona sucks!) is connected via a second 
> pfsense to the internet.
>
>
>
> Both pfsenses are connected via OpenVPN, so i can reach the 
> Openmeetings-Webinterface via 10.50.100.13:5443/openmeetings Port  on the 
> dockerhost is reachable, too. Every traffic between my home and office is 
> allowed.
>
>
>
> I can login from my desktop PC@home and from my laptop@home. On every machine 
> i can see myself, but i cant see the partner. Audio isn´t working also.
>
>
>
> I tried to setup a turnserver on my dockerhost as well:
>
>
>
> docker pull instrumentisto/coturn
> vi /home/turnserver/turnserver.conf
> listening-port=3478
> relay-ip=xxx.xxx.xxx.xxx
> external-ip=xxx.xxx.xxx.xxx
> relay-threads=50
> min-port=41369
> max-port=65535
> user=kurento:kurento
> lt-cred-mech
>
> docker run -d --network=host -v 
> /home/turnserver/turnserver.conf:/etc/coturn/turnserver.conf --name 
> turnserver instrumentisto/coturn -r=xxx.xxx.xxx.xxx:3478
>
> xxx.xxx.xxx.xxx above is the external ip from my office.
>
> I made a portforwarding from my Office-Pfsense for tcp/upd 3478 to dockerhost.
>
> Openmeeting docker is started:
>
> docker run -i --rm --expose=5443 --expose= -p 5443:5443 -p : -e 
> TURN_URL="turn:10.50.100.13:3478" -e TURN_USER="kurento" -e 
> TURN_PASS="kurento" apache/openmeetings:5.0.0-M3
>
>
>
> Is there any documentation that could help me?
>
> Thx
>
> Wolfgang
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

Re: New tutorial installation SSL certificates and Coturn for OpenMeetings 5.0.0-M3

[YUP]

OK, so without udp it will not work... That is the reason why my
installation will not work behind firewall with the only 5443 and 
ports opened.

Yarema

On Mon, Mar 30, 2020 at 1:35 PM Maxim Solodovnik  wrote:
>
> Section #8 states:
>
> We need open some ports in the router and the firewall for the servers access.
> These are:
> 3478   TCP-UDP  IN
> 5443   TCP   IN
>    TCP   IN
> 49152:65535 UDP IN-OUT
>
>
> On Mon, 30 Mar 2020 at 18:27, YUP  wrote:
>>
>> Thanks for the answer. I see that user "kurento" was created when
>> kurent-media-server was installed.
>> I have one more question: 5443 and  ports are open, all other
>> ports tcp and udp are closed, will audio and video work? How it affect
>> media server and OM?
>>
>> Best,
>> Yarema
>>
>> On Mon, Mar 30, 2020 at 1:08 PM Alvaro  wrote:
>> >
>> > ...is add a new point. Please download again the tutorial.
>> >
>> > Thanks
>> >
>> > Alvaro
>> >
>> >
>> >
>> > ..
>> >
>> > El dom, 29-03-2020 a las 16:33 +0200, Alvaro escribió:
>> >
>> >
>> > ...and is not two without three...
>> >
>> > I re-uploaded the tuto fot thirt time.
>> >
>> > Please download again if does before:
>> >
>> > https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeetings%205.0.0-M3.pdf
>> >
>> > Thank you
>> >
>> > Alvaro
>> >
>> >
>> > 
>> >
>> >
>> > El dom, 29-03-2020 a las 12:27 +0200, Alvaro escribió:
>> >
>> > Ok, is re-uploaded the tutorial modified.
>> >
>> > I must to say that for the first version of this guide,
>> > i asked to Maxim to test with me the right functioning
>> > of our cams and the microphones, and the result was OK.
>> > But don't asked to him test the letsencrypt functioning.
>> >
>> > So the guilt is only mine.
>> > I am sorry.
>> >
>> > Here can download directly the guide second version,
>> > with letsencrypt tested for me and working right:
>> >
>> > https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeetings%205.0.0-M3.pdf
>> >
>> > Thank you
>> >
>> > Alvaro
>> >
>> >
>> > --
>> >
>> > El dom, 29-03-2020 a las 08:09 +0700, Maxim Solodovnik escribió:
>> >
>> > Nope, `application.base.url` is not the case
>> >
>> > Is https://:5443 accessible? (maybe you have renamed `openmeetings` 
>> > context name?)
>> > Any errors in catalina.out or other log files in log folder?
>> >
>> > On Sun, 29 Mar 2020 at 03:24, stefanx  wrote:
>> >
>> >
>> >
>> > https://:5443/openmeetings/ : HTTP Status 404 – Not Found
>> >
>> > Perhaps "application.base.url" in the Openmeetings configuration now is 
>> > wrong ?
>> >
>> > But I now cannot change application.base.url, except with mysql db 
>> > modification ?
>> >
>> >
>> > Am 28.03.20 um 04:12 schrieb Maxim Solodovnik:
>> > > 404 at what URL?
>> > >
>> > > On Sat, 28 Mar 2020 at 03:19, stefanx > > > <mailto:stef...@lrz.uni-muenchen.de>> wrote:
>> > >
>> > > I followed this instruction, the letsencrpyt installation is ok, by 
>> > > now I get "HTTP Status 404 – Not Found"
>> > >
>> > > Any ideas ?
>> > >
>> > > Am 27.03.20 um 17:20 schrieb Alvaro:
>> > > >
>> > > > Hello,
>> > > >
>> > > > It is at your disposal a new tutorial called:
>> > > >
>> > > >
>> > > > Installation SSL certificates and Coturn for OpenMeetings 
>> > > 5.0.0-M3.pdf
>> > > >
>> > > >
>> > > > It is tested with an OpenMeetings 5 server installed on a pc
>> > > > at home, after NAT router; and each in the room saw and heard the 
>> > > others
>> > > > cameras and your own correctly.
>> > > > Also in the tests done, we have uploaded files, recorded video
>> > > > and shared desktop without any error.
>> > > >
>> > > > You can download the tutorial directly from here:
>> > > >
>> > > > 
>> > > https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeetings%205.0.0-M3.pdf
>> > > >
>> > > > ...or find it here:
>> > > >
>> > > > 
>> > > https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools
>> > > >
>> > > > Best regards
>> > > >
>> > > > Alvaro
>> > > >
>> > > >
>> > > >
>> > > > -
>> > >
>> > >
>> > >
>> > > --
>> > > WBR
>> > > Maxim aka solomax
>> >
>> >
>> >
>> >
>> > --
>> > WBR
>> > Maxim aka solomax
>
>
>
> --
> WBR
> Maxim aka solomax

Re: New tutorial installation SSL certificates and Coturn for OpenMeetings 5.0.0-M3

[YUP]

Thanks for the answer. I see that user "kurento" was created when
kurent-media-server was installed.
I have one more question: 5443 and  ports are open, all other
ports tcp and udp are closed, will audio and video work? How it affect
media server and OM?

Best,
Yarema

On Mon, Mar 30, 2020 at 1:08 PM Alvaro  wrote:
>
> ...is add a new point. Please download again the tutorial.
>
> Thanks
>
> Alvaro
>
>
>
> ..
>
> El dom, 29-03-2020 a las 16:33 +0200, Alvaro escribió:
>
>
> ...and is not two without three...
>
> I re-uploaded the tuto fot thirt time.
>
> Please download again if does before:
>
> https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeetings%205.0.0-M3.pdf
>
> Thank you
>
> Alvaro
>
>
> 
>
>
> El dom, 29-03-2020 a las 12:27 +0200, Alvaro escribió:
>
> Ok, is re-uploaded the tutorial modified.
>
> I must to say that for the first version of this guide,
> i asked to Maxim to test with me the right functioning
> of our cams and the microphones, and the result was OK.
> But don't asked to him test the letsencrypt functioning.
>
> So the guilt is only mine.
> I am sorry.
>
> Here can download directly the guide second version,
> with letsencrypt tested for me and working right:
>
> https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeetings%205.0.0-M3.pdf
>
> Thank you
>
> Alvaro
>
>
> --
>
> El dom, 29-03-2020 a las 08:09 +0700, Maxim Solodovnik escribió:
>
> Nope, `application.base.url` is not the case
>
> Is https://:5443 accessible? (maybe you have renamed `openmeetings` 
> context name?)
> Any errors in catalina.out or other log files in log folder?
>
> On Sun, 29 Mar 2020 at 03:24, stefanx  wrote:
>
>
>
> https://:5443/openmeetings/ : HTTP Status 404 – Not Found
>
> Perhaps "application.base.url" in the Openmeetings configuration now is wrong 
> ?
>
> But I now cannot change application.base.url, except with mysql db 
> modification ?
>
>
> Am 28.03.20 um 04:12 schrieb Maxim Solodovnik:
> > 404 at what URL?
> >
> > On Sat, 28 Mar 2020 at 03:19, stefanx  > > wrote:
> >
> > I followed this instruction, the letsencrpyt installation is ok, by now 
> > I get "HTTP Status 404 – Not Found"
> >
> > Any ideas ?
> >
> > Am 27.03.20 um 17:20 schrieb Alvaro:
> > >
> > > Hello,
> > >
> > > It is at your disposal a new tutorial called:
> > >
> > >
> > > Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M3.pdf
> > >
> > >
> > > It is tested with an OpenMeetings 5 server installed on a pc
> > > at home, after NAT router; and each in the room saw and heard the 
> > others
> > > cameras and your own correctly.
> > > Also in the tests done, we have uploaded files, recorded video
> > > and shared desktop without any error.
> > >
> > > You can download the tutorial directly from here:
> > >
> > > 
> > https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeetings%205.0.0-M3.pdf
> > >
> > > ...or find it here:
> > >
> > > 
> > https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools
> > >
> > > Best regards
> > >
> > > Alvaro
> > >
> > >
> > >
> > > -
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
>
>
>
>
> --
> WBR
> Maxim aka solomax

Re: New tutorial installation SSL certificates and Coturn for OpenMeetings 5.0.0-M3

[YUP]

Hi Alvaro,
I have a few comments regarding your tutorial.
1. You gave permission to user "kurento" but you didn't create this user before.
2. Why do you need to grant user "kurento" the openmeetings working directory?
3. Under which daemon users run OM and kurento in your installation,
are they different or the same?
4. How did you test your installation behind NAT? Did you use other
user from another domain than yours?
5. Why do you need  tcp port and UDP ports open? As far I
understand TURN server is used when kurento server is behind nat and
serves as a meeting point for clients from different networks. Please
correct me if I am wrong, I'm just trying to understand how it works
and how to use it in my setup.
Thanks,
Yarema



On Sun, Mar 29, 2020 at 10:02 PM stefanx  wrote:
>
>
> Now it works, I've made a failure in
> /opt/open503/webapps/openmeetings/WEB-INF/classes/applicationContext.xml
>
> Am 29.03.20 um 03:09 schrieb Maxim Solodovnik:
> > Nope, `application.base.url` is not the case
> >
> > Is https://:5443 accessible? (maybe you have renamed `openmeetings` 
> > context name?)
> > Any errors in catalina.out or other log files in log folder?
> >
> > On Sun, 29 Mar 2020 at 03:24, stefanx  > > wrote:
> >
> >
> >
> > https://:5443/openmeetings/ : HTTP Status 404 – Not Found
> >
> > Perhaps "application.base.url" in the Openmeetings configuration now is 
> > wrong ?
> >
> > But I now cannot change application.base.url, except with mysql db 
> > modification ?
> >
> >
> > Am 28.03.20 um 04:12 schrieb Maxim Solodovnik:
> > > 404 at what URL?
> > >
> > > On Sat, 28 Mar 2020 at 03:19, stefanx  >   > >> wrote:
> > >
> > > I followed this instruction, the letsencrpyt installation is ok, 
> > by now I get "HTTP Status 404 – Not Found"
> > >
> > > Any ideas ?
> > >
> > > Am 27.03.20 um 17:20 schrieb Alvaro:
> > > >
> > > > Hello,
> > > >
> > > > It is at your disposal a new tutorial called:
> > > >
> > > >
> > > > Installation SSL certificates and Coturn for OpenMeetings 
> > 5.0.0-M3.pdf
> > > >
> > > >
> > > > It is tested with an OpenMeetings 5 server installed on a pc
> > > > at home, after NAT router; and each in the room saw and heard 
> > the others
> > > > cameras and your own correctly.
> > > > Also in the tests done, we have uploaded files, recorded video
> > > > and shared desktop without any error.
> > > >
> > > > You can download the tutorial directly from here:
> > > >
> > > > 
> > https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeetings%205.0.0-M3.pdf
> > > >
> > > > ...or find it here:
> > > >
> > > > 
> > https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools
> > > >
> > > > Best regards
> > > >
> > > > Alvaro
> > > >
> > > >
> > > >
> > > > -
> > >
> > >
> > >
> > > --
> > > WBR
> > > Maxim aka solomax
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
>

Re: Openmeetings, kurento and TURN behind NAT

[YUP]

BTW, just wondering, why in the full version of OM in docker the
kurento server doesn't have turn-environments, but have it for OM? It
should be in the line in the file
/etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini
with
turnURL=:@:[?transport=]

If kurento server runs in docker, it is very easy via KMS_TURN_URL.

If I understand correctly, OM connects to kurento media server which
next connects to turn server, turn-server is something like a meeting
point for different streams from different clients. Please correct me.
I'm trying to figure out how to correctly setup OM in my environment.

Regards,
Yarema



On Sun, Mar 29, 2020 at 9:37 AM YUP  wrote:
>
> It's ok, at least now I know what the problem is.
> Best,
> Yarema
>
> On Sun, Mar 29, 2020 at 5:25 AM Maxim Solodovnik  wrote:
> >
> > I'm installing KMS inside docker to avoid this
> > Not sure if I can help with your advanced config :(
> >
> > On Sun, Mar 29, 2020, 08:57 YUP  wrote:
> >>
> >> Hi Maxim,
> >> Probably I found what caused that issue with *.webm files. I run
> >> openmeetings in a docker container which load dependent kurento
> >> container (see my docker-compose.yml file in my first email).
> >> Something is wrong with communication between them, maybe permission
> >> issue, different users, don't know now.
> >>
> >> > it would be more reasonable to have
> >> > listening-port=80
> >> > in this case (due to it insecure)
> >>
> >> Good advice, I forgot that firewall allows connection to 80 port too :)
> >>
> >> Regards,
> >> Yarema

Re: Openmeetings, kurento and TURN behind NAT

[YUP]

It's ok, at least now I know what the problem is.
Best,
Yarema

On Sun, Mar 29, 2020 at 5:25 AM Maxim Solodovnik  wrote:
>
> I'm installing KMS inside docker to avoid this
> Not sure if I can help with your advanced config :(
>
> On Sun, Mar 29, 2020, 08:57 YUP  wrote:
>>
>> Hi Maxim,
>> Probably I found what caused that issue with *.webm files. I run
>> openmeetings in a docker container which load dependent kurento
>> container (see my docker-compose.yml file in my first email).
>> Something is wrong with communication between them, maybe permission
>> issue, different users, don't know now.
>>
>> > it would be more reasonable to have
>> > listening-port=80
>> > in this case (due to it insecure)
>>
>> Good advice, I forgot that firewall allows connection to 80 port too :)
>>
>> Regards,
>> Yarema

Re: Openmeetings, kurento and TURN behind NAT

[YUP]

Hi Maxim,
Probably I found what caused that issue with *.webm files. I run
openmeetings in a docker container which load dependent kurento
container (see my docker-compose.yml file in my first email).
Something is wrong with communication between them, maybe permission
issue, different users, don't know now.

> it would be more reasonable to have
> listening-port=80
> in this case (due to it insecure)

Good advice, I forgot that firewall allows connection to 80 port too :)

Regards,
Yarema

Re: Openmeetings, kurento and TURN behind NAT

[YUP]

Maxim,
Finally I managed to launch openmeetings with kurento and coturn. The
problem was in coturn server which didn't work as expected. I
installed coturn server on my private laptop (no firewall and NAT)
which listens on port 443, with the following configuration:

listening-port=443
tls-listening-port=5349
verbose
lt-cred-mech
user=kurento:kurento
realm=my_openmeetings_server_domain
log-file=/var/log/turnserver/turn.log

After that all openmeetings users can see each other cameras and hear
each other. The only problem remain, that session recording files are
wav file, not avi. Do you have a clue what is the reason is? Coul it
be a ffmpeg issue?

Best,
Yarema


On Thu, Mar 19, 2020 at 9:43 PM YUP  wrote:
>
> Maxim,
> I made a mistake, in nginx configuration section for openmetings port
> should be 5443 instead of 5080, sorry for that.
> I also forgot to mention that only tcp requests are allowed in our
> firewall, udp if prohibited, as far as know.
> Can you examine my configs and say what is wrong?
>
> Regards,
> Yarema
>
>   location /openmeetings {
> proxy_pass http://localhost:5080/openmeetings;
>
> proxy_set_header Host $host;
> proxy_http_version 1.1;
> proxy_set_header Upgrade $http_upgrade;
> proxy_set_header Connection "upgrade";
>
> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
> proxy_set_header Referer 'https://$host/openmeetings/';
> proxy_set_header X-Real-IP $remote_addr;
> }
>
> On Mon, Mar 16, 2020 at 5:01 PM YUP  wrote:
> >
> > Please take your time.
> > I gonna describe my set up briefly .
> >
> > Initial data:
> > External nat has address external_nat_ip
> > All external ports are closed except 443
> > From inside allowed only http connections to ports 80, 8080, 443 and 22
> >
> > Openmeetings runs in docker, I use docker-compose with the following
> > docker-compose.yml:
> >
> > version: '3.7'
> > services:
> >   openmeetings:
> > image: apache/openmeetings:min-5.0.0-M3
> > ports:
> >   - "5080:5080"
> >   - "5443:5443"
> > volumes:
> >   - ~/openmeetings/omdata:/opt/omdata
> >   - ~/openmeetings/logs:/opt/openmeetings/logs
> > environment:
> >   - OM_KURENTO_WS_URL=ws://kurento:/kurento
> >   - TURN_USER=kurento
> >   - TURN_PASS=kurento
> >   - TURN_URL=external_nat_ip?transport=tcp
> >   - OM_DB_TYPE=mysql
> >   - OM_DB_HOST=172.17.0.1
> >   - OM_DB_PORT=3306
> >   - OM_DB_USER=om_user
> >   - OM_DB_PASS=om_passwd
> >   - OM_DB_NAME=openmeetings
> > depends_on:
> >   - kurento
> >   - coturn
> > restart: unless-stopped
> >   kurento:
> > image: kurento/kurento-media-server
> > ports:
> >   - ":"
> > environment:
> >   - KMS_TURN_URL=kurento:kurento@external_nat_ip?transport=tcp
> > restart: unless-stopped
> >   coturn:
> > image: kurento/coturn-auth
> > ports:
> >   - "3478:3478"
> > environment:
> >   - LISTENING_PORT=3478
> >   - REALM=kurento.org
> >   - USER=kurento
> >   - PASSWORD=kurento
> > restart: unless-stopped
> >
> > I use sslh https://github.com/yrutschle/sslh to connect do different
> > services behind nat with the following configuration:
> >
> > verbose: true
> > timeout: 18000;
> > listen:
> > (
> > { host: "internal_nat_ip"; port: "443"; }
> > );
> > protocols:
> > (
> > # ssh:
> >  { name: "ssh"; service: "ssh"; host: "localhost"; port: "22";
> > probe: "builtin"; },
> > # openvpn:
> >  { name: "openvpn"; host: "localhost"; port: "1194"; probe: "builtin"; 
> > },
> > # nginx:
> >  { name: "ssl"; host: "localhost"; port: "2443"; probe: "builtin";
> > log_level: 0;},
> > # coturn:
> >  { name: "regex"; host: "localhost"; port: "3478"; regex_patterns:
> > [ "\x21\x12\xa4\x42" ]; }
> > );
> > transparent: true;
> >
> >
> > And nginx configuration (there are another services, I left only
> > openmeetings and kurento (do I really need to have kurento websocket
> > outside nat?))
> >
> >
> > server {
> > listen   2443 ssl http2;
> > list

Share turn server for testing

[YUP]

Hi,
Can somebody share your turn server for testing for a one day? I need
to test my setup.
Turn server should listen on port 443 and allow tcp only. My
openmeetings server is behind restrict firewall, only 443,22 and 80
ports are allowed for outcoming tcp traffic, and only 443 port is
allowed for incoming tcp traffic.
I'm trying to set up openmeetings+kurento server which can work under
the conditions mentioned above.
Regards,
Yarema

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

Yes, the openmeeting server is behind restrictive firewall with the only
one 443 port opened fo incoming connections ofrom outside and only 80,
8080, 22 and 443 opened for http requests from inside. Consequently, when I
am not in the same network of the openmeeting server the mentioned issue is
happening. I understood it when tried to configure kurento and turn server.
I seems to me that turn server need more open ports for media streams, I
can't put them all into one 443 "hole" even by means of advanced traffic
balancer. I don't know how...
Regards,
Yarema

On Tue, Mar 24, 2020, 06:26 Maxim Solodovnik  wrote:

> Is this still an issue?
>
> On Mon, 23 Sep 2019 at 12:20, YUP  wrote:
> >
> > My OM section in nginx config file looks as follows:
> >
> >   location /openmeetings {
> > proxy_pass https://localhost:5443/openmeetings;
> > proxy_http_version 1.1;
> > proxy_set_header Upgrade $http_upgrade;
> > proxy_set_header Connection "upgrade";
> > proxy_set_header Host $host;
> > proxy_set_header X-Real-IP $remote_addr;
> > proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
> > proxy_set_header X-Forwarded-Proto $scheme;
> > proxy_set_header X-Forwarded-Protocol $scheme;
> > proxy_set_header X-Forwarded-Host $http_host;
> > }
> >
> > нд, 22 вер. 2019 о 17:10 YUP  пише:
> > >
> > > Hi again,
> > > There are a few things which I discovered:
> > > 1. When I install openmeetings locally and KMS in docker (using
> > > provided instruction for Archlinux) on my laptop with archlinux and
> > > without (!) nginx and proxy_pass it runs out of the box without any
> > > problems and records everything I want. But:
> > > 2. If i do the same but with nginx as a proxy, the behavior is the
> > > same as I described in my first email.
> > > 3. When I install full version of openmeetings with mysql and kurento
> > > by means of docker on host machine with archlinux, the kurento server
> > > is dead. The reason is very simple, the start script can't define max
> > > size of the open file. I don't know why it happen for Archlinux.  As a
> > > workaround it is enough to enter running container with openmeetings,
> > > comment line with DAEMON_MAX_FILE=... in kurento configuration file
> > > /etc/default/kurento-media-server, save and start kms: service
> > > kurento-media-server  start. Then kurento server starts without
> > > errors. But with nginx and proxy_pass recording doesn't work, and
> > > works without proxy_pass.
> > > 4. For some understandable reasons I have only port 443 opened to the
> > > world, so a method how to get OM work with this environment would be
> > > highly appreciated.
> > > Regards,
> > > Yarema
> > >
> > > нд, 22 вер. 2019 о 04:04 Maxim Solodovnik  пише:
> > > >
> > > > This actually make no sense :(
> > > > I always thought docker should work the same for different machines
> > > >
> > > > This is my start command and first lines of the output:
> > > >
> > > > `docker run -i --rm --name om-server-full --expose=5443
> --expose= -p 5443:5443 -p :
> openmeetings-docker-images.bintray.io/server-full:latest`
> <http://openmeetings-docker-images.bintray.io/server-full:latest>
> > > >  * Stopping MySQL database server mysqld
> > > >...done.
> > > >  * Starting MySQL database server mysqld
> > > >...done.
> > > > OM server of type full will be run
> > > >  * Start Kurento Media Server
> > > >  * Directory '/var/log/kurento-media-server' is not owned by 'nobody'
> > > >  * Changed owner of '/var/log/kurento-media-server' to 'nobody'
> > > >  * Configure Kernel resource limits for Kurento Media Server
> > > >...done.
> > > >
> > > > This is the line the KMS is being started:
> > > >
> https://github.com/openmeetings/openmeetings-docker/blob/master/scripts/om.sh#L44
> > > >
> > > > Have no idea what is going on :(
> > > >
> > > >
> > > > On Sun, 22 Sep 2019 at 01:29, YUP  wrote:
> > > >>
> > > >> I checked your image, and got the same result, kurento is dead. I
> > > >> gonna give up
> > > >>
> > > >> $ docker info
> > > >> Client:
> > > >>  Debug Mode: false
> > > >

Re: only local cam is working

[YUP]

Looking forward to the results of your testings, Maxim!

On Fri, Mar 20, 2020 at 1:02 PM Maxim Solodovnik  wrote:
>
> Well,
>
> TURN server is a MUST in case of any router/firewall for any of the 
> participants
> And it requires much more ports to handle "hard" cases
> I'll do some investigations, but the worst cases require one socket
> per stream so I doubt it can be done by one proxy server
> We will see :))
>
> On Thu, 19 Mar 2020 at 15:46, YUP  wrote:
> >
> > It seams to me that it is the same problem as I have. Difference is only 
> > the one port 443 is opened in my case. I'm interested in being able to know 
> > if the correctly configured turn server it will help.
> > Best,
> > Yarema
> >
> > On Thu, Mar 19, 2020, 09:24  wrote:
> >>
> >> Hello Maxim,
> >>
> >> it's a cloud setup, a simple virtual machine with ports 443 and  
> >> opened. I didn't setup
> >> any TURN server, I just followed the great intall guide on ubuntu 18.04 
> >> LTS by Alvaro.
> >>
> >> thanks for investigate on my problem
> >>
> >> Alain
> >>
> >>
> >> De : Maxim Solodovnik 
> >> À : Openmeetings user-list 
> >> Sujet : Re: only local cam is working
> >> Date : 19/03/2020 03:40:15 Europe/Paris
> >>
> >> Hello Alain,
> >>
> >> usually this happens if your TURN server is not working properly
> >> Is this the case?
> >>
> >> On Thu, 19 Mar 2020 at 00:04,  wrote:
> >> >
> >> > Hello all,
> >> >
> >> > I upgraded my 5.0.0-M2 to an M3 setup because on all participants only 
> >> > the local cam was showing. It resolve the problem
> >> > for a few days ( maybe 2 weeks ) but now my M3 is having the save 
> >> > problem. I've tried to reinstall everything
> >> > ( except OS) but no luck. I am on GMT+1, i can invite you to see the 
> >> > problem.
> >> >
> >> > take care of you all
> >> >
> >> > Alain
> >> >
> >>
> >>
> >> --
> >> WBR
> >> Maxim aka solomax
>
>
>
> --
> WBR
> Maxim aka solomax

Re: Openmeetings, kurento and TURN behind NAT

[YUP]

Maxim,
I made a mistake, in nginx configuration section for openmetings port
should be 5443 instead of 5080, sorry for that.
I also forgot to mention that only tcp requests are allowed in our
firewall, udp if prohibited, as far as know.
Can you examine my configs and say what is wrong?

Regards,
Yarema

  location /openmeetings {
proxy_pass http://localhost:5080/openmeetings;

proxy_set_header Host $host;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Referer 'https://$host/openmeetings/';
proxy_set_header X-Real-IP $remote_addr;
}

On Mon, Mar 16, 2020 at 5:01 PM YUP  wrote:
>
> Please take your time.
> I gonna describe my set up briefly .
>
> Initial data:
> External nat has address external_nat_ip
> All external ports are closed except 443
> From inside allowed only http connections to ports 80, 8080, 443 and 22
>
> Openmeetings runs in docker, I use docker-compose with the following
> docker-compose.yml:
>
> version: '3.7'
> services:
>   openmeetings:
> image: apache/openmeetings:min-5.0.0-M3
> ports:
>   - "5080:5080"
>   - "5443:5443"
> volumes:
>   - ~/openmeetings/omdata:/opt/omdata
>   - ~/openmeetings/logs:/opt/openmeetings/logs
> environment:
>   - OM_KURENTO_WS_URL=ws://kurento:/kurento
>   - TURN_USER=kurento
>   - TURN_PASS=kurento
>   - TURN_URL=external_nat_ip?transport=tcp
>   - OM_DB_TYPE=mysql
>   - OM_DB_HOST=172.17.0.1
>   - OM_DB_PORT=3306
>   - OM_DB_USER=om_user
>   - OM_DB_PASS=om_passwd
>   - OM_DB_NAME=openmeetings
> depends_on:
>   - kurento
>   - coturn
> restart: unless-stopped
>   kurento:
> image: kurento/kurento-media-server
> ports:
>   - ":"
> environment:
>   - KMS_TURN_URL=kurento:kurento@external_nat_ip?transport=tcp
> restart: unless-stopped
>   coturn:
> image: kurento/coturn-auth
> ports:
>   - "3478:3478"
> environment:
>   - LISTENING_PORT=3478
>   - REALM=kurento.org
>   - USER=kurento
>   - PASSWORD=kurento
> restart: unless-stopped
>
> I use sslh https://github.com/yrutschle/sslh to connect do different
> services behind nat with the following configuration:
>
> verbose: true
> timeout: 18000;
> listen:
> (
> { host: "internal_nat_ip"; port: "443"; }
> );
> protocols:
> (
> # ssh:
>  { name: "ssh"; service: "ssh"; host: "localhost"; port: "22";
> probe: "builtin"; },
> # openvpn:
>  { name: "openvpn"; host: "localhost"; port: "1194"; probe: "builtin"; },
> # nginx:
>  { name: "ssl"; host: "localhost"; port: "2443"; probe: "builtin";
> log_level: 0;},
> # coturn:
>  { name: "regex"; host: "localhost"; port: "3478"; regex_patterns:
> [ "\x21\x12\xa4\x42" ]; }
> );
> transparent: true;
>
>
> And nginx configuration (there are another services, I left only
> openmeetings and kurento (do I really need to have kurento websocket
> outside nat?))
>
>
> server {
> listen   2443 ssl http2;
> listen [::]:2443 ssl http2;
> server_name  localhost;
>
> autoindex on;
> root   /srv/http/;
> index index.php index.html index.htm;
>
> #ssl_certificate  /etc/httpd/conf/server.crt;
> #ssl_certificate_key  /etc/httpd/conf/server.key;
>
> include conf/001-certbot.conf;
>
> #ssl on;
> ssl_session_cache  builtin:1000  shared:SSL:10m;
> ssl_protocols  TLSv1 TLSv1.1; #TLSv1.2;
> #ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4;
> #ssl_prefer_server_ciphers on;
>
>
>  proxy_headers_hash_max_size 512;
>  proxy_headers_hash_bucket_size 128;
>
> location ~ [^/]\.php(/|$) {
> fastcgi_split_path_info  ^(.+\.php)(/.+)$;
> fastcgi_indexindex.php;
> fastcgi_pass unix:/run/php-fpm/php-fpm.sock;
> include fastcgi.conf;
> fastcgi_param   PATH_INFO   $fastcgi_path_info;
> fastcgi_param   SCRIPT_FILENAME $document_root$fastcgi_script_name;
> }
>
> # User directories, e.g. http://example.com/~user/ :
> location ~ ^/~(.+?)(/.*)?$ {
> alias /home/$1/public_html$2;
> index index.html index.htm;
> autoindex on;
> 

Re: only local cam is working

[YUP]

It seams to me that it is the same problem as I have. Difference is only
the one port 443 is opened in my case. I'm interested in being able to know
if the correctly configured turn server it will help.
Best,
Yarema

On Thu, Mar 19, 2020, 09:24  wrote:

> Hello Maxim,
>
> it's a cloud setup, a simple virtual machine with ports 443 and 
> opened. I didn't setup
> any TURN server, I just followed the great intall guide on ubuntu 18.04
> LTS by Alvaro.
>
> thanks for investigate on my problem
>
> Alain
>
>
> De : Maxim Solodovnik 
> À : Openmeetings user-list 
> Sujet : Re: only local cam is working
> Date : 19/03/2020 03:40:15 Europe/Paris
>
> Hello Alain,
>
> usually this happens if your TURN server is not working properly
> Is this the case?
>
> On Thu, 19 Mar 2020 at 00:04,  wrote:
> >
> > Hello all,
> >
> > I upgraded my 5.0.0-M2 to an M3 setup because on all participants only
> the local cam was showing. It resolve the problem
> > for a few days ( maybe 2 weeks ) but now my M3 is having the save
> problem. I've tried to reinstall everything
> > ( except OS) but no luck. I am on GMT+1, i can invite you to see the
> problem.
> >
> > take care of you all
> >
> > Alain
> >
>
>
> --
> WBR
> Maxim aka solomax
>
>

Re: Openmeetings, kurento and TURN behind NAT

[YUP]

et_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_read_timeout 9;
}

add_header X-Frame-Options SAMEORIGIN;
add_header X-Content-Type-Options nosniff;
}



On Mon, Mar 16, 2020 at 1:39 PM Maxim Solodovnik  wrote:
>
> Hello Yarema,
>
> sorry for keeping silence
> I'll try to investigate this config later this week
> To much day time job right now :(
>
> Please share your further findings here if any :)
>
> On Mon, 16 Mar 2020 at 09:04, YUP  wrote:
> >
> > Maxim,
> > I was also managed to install coturn on external server which listen
> > on port 443. Kurento connects to this port (via TURN_URL,
> > TURN_USER,TURN_PASS), I can see it in logs. I see in logs that
> > openmeetings connects to kurento. But I don't understand why all my
> > construction not working as needed? I still can't make settings test,
> > record and play sample, two users can't see each other videos from
> > cameras.
> > Here I should to see to find the solution?
> >
> > On Sun, Mar 15, 2020 at 7:23 PM YUP  wrote:
> > >
> > > I was able to connect to kurento websocket which is proxified by
> > > nginx, the solution was very simple, put wss instead of https,
> > > probably for some reasons openmeetings needs to have ws or wss in the
> > > input url:
> > > - OM_KURENTO_WS_URL=wss://external_server_ip_address/kurento
> > > But it is not solved the issue with recording audio/video in test and
> > > different users.
> > >
> > > On Sun, Mar 15, 2020 at 10:16 AM YUP  wrote:
> > > >
> > > > No, it is not a reason, checked.
> > > >
> > > > On Sun, Mar 15, 2020 at 10:10 AM YUP  wrote:
> > > > >
> > > > > Server has self-signed certificate, can it be a reason?
> > > > >
> > > > > On Sun, Mar 15, 2020 at 9:38 AM YUP  wrote:
> > > > > >
> > > > > > Just to inform you, I made proxified kurento websocket in nginx and 
> > > > > > I
> > > > > > can connect to it:
> > > > > > $ wscat -n --connect  https://external_server_ip_address/kurento
> > > > > > (node:24082) [DEP0123] DeprecationWarning: Setting the TLS 
> > > > > > ServerName
> > > > > > to an IP address is not permitted by RFC 6066. This will be ignored 
> > > > > > in
> > > > > > a future version.
> > > > > > Connected (press CTRL+C to quit)
> > > > > > >
> > > > > >
> > > > > > I set
> > > > > > - OM_KURENTO_WS_URL=https://external_server_ip_address/kurento
> > > > > > but got
> > > > > > o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] - Fail to create
> > > > > > Kurento client, will re-try in 1 ms
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Sun, Mar 15, 2020 at 8:56 AM YUP  wrote:
> > > > > > >
> > > > > > > Can we just proxify kurento websocket? Something like this
> > > > > > > https://gist.github.com/steve-ng/ed6de1fa702ef70bd6ce ?
> > > > > > >
> > > > > > > On Sun, Mar 15, 2020 at 8:41 AM Maxim Solodovnik 
> > > > > > >  wrote:
> > > > > > > >
> > > > > > > > It seems I misread your previous email "all ports except 443, 
> > > > > > > > 80, 8080 and 22."
> > > > > > > > I'm afraid you need more open ports ...
> > > > > > > >
> > > > > > > > I'm not sure but I would investigate if KMS/TURN URLs can be 
> > > > > > > > set up
> > > > > > > > for context i.e.
> > > > > > > > yourserver:4278/turn, yourserver:/kms in this case you can 
> > > > > > > > proxy them 
> > > > > > > >
> > > > > > > > On Sun, 15 Mar 2020 at 14:32, YUP  wrote:
> > > > > > > > >
> > > > > > > > > It nothing changes, only 443 is open to the world.
> > > > > > > > >
> > > > > > > > > On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik 
> > > > > > > > >  wrote:
> > > > > > > > > >
> > > > > > > > > > Maybe you can set up KM

Re: Openmeetings, kurento and TURN behind NAT

[YUP]

Maxim,
I was also managed to install coturn on external server which listen
on port 443. Kurento connects to this port (via TURN_URL,
TURN_USER,TURN_PASS), I can see it in logs. I see in logs that
openmeetings connects to kurento. But I don't understand why all my
construction not working as needed? I still can't make settings test,
record and play sample, two users can't see each other videos from
cameras.
Here I should to see to find the solution?

On Sun, Mar 15, 2020 at 7:23 PM YUP  wrote:
>
> I was able to connect to kurento websocket which is proxified by
> nginx, the solution was very simple, put wss instead of https,
> probably for some reasons openmeetings needs to have ws or wss in the
> input url:
> - OM_KURENTO_WS_URL=wss://external_server_ip_address/kurento
> But it is not solved the issue with recording audio/video in test and
> different users.
>
> On Sun, Mar 15, 2020 at 10:16 AM YUP  wrote:
> >
> > No, it is not a reason, checked.
> >
> > On Sun, Mar 15, 2020 at 10:10 AM YUP  wrote:
> > >
> > > Server has self-signed certificate, can it be a reason?
> > >
> > > On Sun, Mar 15, 2020 at 9:38 AM YUP  wrote:
> > > >
> > > > Just to inform you, I made proxified kurento websocket in nginx and I
> > > > can connect to it:
> > > > $ wscat -n --connect  https://external_server_ip_address/kurento
> > > > (node:24082) [DEP0123] DeprecationWarning: Setting the TLS ServerName
> > > > to an IP address is not permitted by RFC 6066. This will be ignored in
> > > > a future version.
> > > > Connected (press CTRL+C to quit)
> > > > >
> > > >
> > > > I set
> > > > - OM_KURENTO_WS_URL=https://external_server_ip_address/kurento
> > > > but got
> > > > o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] - Fail to create
> > > > Kurento client, will re-try in 1 ms
> > > >
> > > >
> > > >
> > > > On Sun, Mar 15, 2020 at 8:56 AM YUP  wrote:
> > > > >
> > > > > Can we just proxify kurento websocket? Something like this
> > > > > https://gist.github.com/steve-ng/ed6de1fa702ef70bd6ce ?
> > > > >
> > > > > On Sun, Mar 15, 2020 at 8:41 AM Maxim Solodovnik 
> > > > >  wrote:
> > > > > >
> > > > > > It seems I misread your previous email "all ports except 443, 80, 
> > > > > > 8080 and 22."
> > > > > > I'm afraid you need more open ports ...
> > > > > >
> > > > > > I'm not sure but I would investigate if KMS/TURN URLs can be set up
> > > > > > for context i.e.
> > > > > > yourserver:4278/turn, yourserver:/kms in this case you can 
> > > > > > proxy them 
> > > > > >
> > > > > > On Sun, 15 Mar 2020 at 14:32, YUP  wrote:
> > > > > > >
> > > > > > > It nothing changes, only 443 is open to the world.
> > > > > > >
> > > > > > > On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik 
> > > > > > >  wrote:
> > > > > > > >
> > > > > > > > Maybe you can set up KMS to use 8080?
> > > > > > > > TURN requires more open port to handle "totally closed" 
> > > > > > > > networks ...
> > > > > > > >
> > > > > > > > On Sun, 15 Mar 2020 at 14:18, YUP  wrote:
> > > > > > > > >
> > > > > > > > > It seems to me that I found what is happening. Firewall 
> > > > > > > > > blocks all non
> > > > > > > > > http requests out to all ports except 443, 80, 8080 and 22. 
> > > > > > > > > That is
> > > > > > > > > why I don't have connection to outside turn ans stun servers. 
> > > > > > > > > Is it
> > > > > > > > > possible to connect to those server in such conditions? 
> > > > > > > > > Tunnels?
> > > > > > > > >
> > > > > > > > > On Fri, Mar 13, 2020 at 1:09 AM YUP  
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > Hello all,
> > > > > > > > > > Could someone help me with configuration of my OM setup? 
> > > > > > > > > > A

Re: Openmeetings, kurento and TURN behind NAT

[YUP]

I was able to connect to kurento websocket which is proxified by
nginx, the solution was very simple, put wss instead of https,
probably for some reasons openmeetings needs to have ws or wss in the
input url:
- OM_KURENTO_WS_URL=wss://external_server_ip_address/kurento
But it is not solved the issue with recording audio/video in test and
different users.

On Sun, Mar 15, 2020 at 10:16 AM YUP  wrote:
>
> No, it is not a reason, checked.
>
> On Sun, Mar 15, 2020 at 10:10 AM YUP  wrote:
> >
> > Server has self-signed certificate, can it be a reason?
> >
> > On Sun, Mar 15, 2020 at 9:38 AM YUP  wrote:
> > >
> > > Just to inform you, I made proxified kurento websocket in nginx and I
> > > can connect to it:
> > > $ wscat -n --connect  https://external_server_ip_address/kurento
> > > (node:24082) [DEP0123] DeprecationWarning: Setting the TLS ServerName
> > > to an IP address is not permitted by RFC 6066. This will be ignored in
> > > a future version.
> > > Connected (press CTRL+C to quit)
> > > >
> > >
> > > I set
> > > - OM_KURENTO_WS_URL=https://external_server_ip_address/kurento
> > > but got
> > > o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] - Fail to create
> > > Kurento client, will re-try in 1 ms
> > >
> > >
> > >
> > > On Sun, Mar 15, 2020 at 8:56 AM YUP  wrote:
> > > >
> > > > Can we just proxify kurento websocket? Something like this
> > > > https://gist.github.com/steve-ng/ed6de1fa702ef70bd6ce ?
> > > >
> > > > On Sun, Mar 15, 2020 at 8:41 AM Maxim Solodovnik  
> > > > wrote:
> > > > >
> > > > > It seems I misread your previous email "all ports except 443, 80, 
> > > > > 8080 and 22."
> > > > > I'm afraid you need more open ports ...
> > > > >
> > > > > I'm not sure but I would investigate if KMS/TURN URLs can be set up
> > > > > for context i.e.
> > > > > yourserver:4278/turn, yourserver:/kms in this case you can proxy 
> > > > > them 
> > > > >
> > > > > On Sun, 15 Mar 2020 at 14:32, YUP  wrote:
> > > > > >
> > > > > > It nothing changes, only 443 is open to the world.
> > > > > >
> > > > > > On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik 
> > > > > >  wrote:
> > > > > > >
> > > > > > > Maybe you can set up KMS to use 8080?
> > > > > > > TURN requires more open port to handle "totally closed" networks 
> > > > > > > ...
> > > > > > >
> > > > > > > On Sun, 15 Mar 2020 at 14:18, YUP  wrote:
> > > > > > > >
> > > > > > > > It seems to me that I found what is happening. Firewall blocks 
> > > > > > > > all non
> > > > > > > > http requests out to all ports except 443, 80, 8080 and 22. 
> > > > > > > > That is
> > > > > > > > why I don't have connection to outside turn ans stun servers. 
> > > > > > > > Is it
> > > > > > > > possible to connect to those server in such conditions? Tunnels?
> > > > > > > >
> > > > > > > > On Fri, Mar 13, 2020 at 1:09 AM YUP  wrote:
> > > > > > > > >
> > > > > > > > > Hello all,
> > > > > > > > > Could someone help me with configuration of my OM setup? Any 
> > > > > > > > > help will
> > > > > > > > > be  greatly appreciated.
> > > > > > > > > I have a server which is for several reasons behind NAT, only 
> > > > > > > > > 443 port
> > > > > > > > > is open. There is sslh balancer, which redirect external 
> > > > > > > > > traffic to
> > > > > > > > > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 
> > > > > > > > > minimal
> > > > > > > > > installed in container behind nginx proxy and works well, 
> > > > > > > > > except audio
> > > > > > > > > and video. When I perform setup check after logged in (video 
> > > > > > > > > camera
> > > > > > > > > and microphone) I can see myself in ca

Re: Openmeetings, kurento and TURN behind NAT

[YUP]

No, it is not a reason, checked.

On Sun, Mar 15, 2020 at 10:10 AM YUP  wrote:
>
> Server has self-signed certificate, can it be a reason?
>
> On Sun, Mar 15, 2020 at 9:38 AM YUP  wrote:
> >
> > Just to inform you, I made proxified kurento websocket in nginx and I
> > can connect to it:
> > $ wscat -n --connect  https://external_server_ip_address/kurento
> > (node:24082) [DEP0123] DeprecationWarning: Setting the TLS ServerName
> > to an IP address is not permitted by RFC 6066. This will be ignored in
> > a future version.
> > Connected (press CTRL+C to quit)
> > >
> >
> > I set
> > - OM_KURENTO_WS_URL=https://external_server_ip_address/kurento
> > but got
> > o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] - Fail to create
> > Kurento client, will re-try in 1 ms
> >
> >
> >
> > On Sun, Mar 15, 2020 at 8:56 AM YUP  wrote:
> > >
> > > Can we just proxify kurento websocket? Something like this
> > > https://gist.github.com/steve-ng/ed6de1fa702ef70bd6ce ?
> > >
> > > On Sun, Mar 15, 2020 at 8:41 AM Maxim Solodovnik  
> > > wrote:
> > > >
> > > > It seems I misread your previous email "all ports except 443, 80, 8080 
> > > > and 22."
> > > > I'm afraid you need more open ports ...
> > > >
> > > > I'm not sure but I would investigate if KMS/TURN URLs can be set up
> > > > for context i.e.
> > > > yourserver:4278/turn, yourserver:/kms in this case you can proxy 
> > > > them 
> > > >
> > > > On Sun, 15 Mar 2020 at 14:32, YUP  wrote:
> > > > >
> > > > > It nothing changes, only 443 is open to the world.
> > > > >
> > > > > On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik 
> > > > >  wrote:
> > > > > >
> > > > > > Maybe you can set up KMS to use 8080?
> > > > > > TURN requires more open port to handle "totally closed" networks ...
> > > > > >
> > > > > > On Sun, 15 Mar 2020 at 14:18, YUP  wrote:
> > > > > > >
> > > > > > > It seems to me that I found what is happening. Firewall blocks 
> > > > > > > all non
> > > > > > > http requests out to all ports except 443, 80, 8080 and 22. That 
> > > > > > > is
> > > > > > > why I don't have connection to outside turn ans stun servers. Is 
> > > > > > > it
> > > > > > > possible to connect to those server in such conditions? Tunnels?
> > > > > > >
> > > > > > > On Fri, Mar 13, 2020 at 1:09 AM YUP  wrote:
> > > > > > > >
> > > > > > > > Hello all,
> > > > > > > > Could someone help me with configuration of my OM setup? Any 
> > > > > > > > help will
> > > > > > > > be  greatly appreciated.
> > > > > > > > I have a server which is for several reasons behind NAT, only 
> > > > > > > > 443 port
> > > > > > > > is open. There is sslh balancer, which redirect external 
> > > > > > > > traffic to
> > > > > > > > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 
> > > > > > > > minimal
> > > > > > > > installed in container behind nginx proxy and works well, 
> > > > > > > > except audio
> > > > > > > > and video. When I perform setup check after logged in (video 
> > > > > > > > camera
> > > > > > > > and microphone) I can see myself in camera and can also see 
> > > > > > > > increasing
> > > > > > > > and decreasing green line, which indicate microphone level, but 
> > > > > > > > I
> > > > > > > > can't save and replay the testing record. As far I understand 
> > > > > > > > the
> > > > > > > > problem is in NAT, so I had to use kurento server with TURN 
> > > > > > > > server. I
> > > > > > > > did that by adding the environment variables for kurento server 
> > > > > > > > in
> > > > > > > > docker container with the corresponding data for 
> > > > > > > > turn.anyfirewall.com:
> > > > > > > >
&

Re: Openmeetings, kurento and TURN behind NAT

[YUP]

Server has self-signed certificate, can it be a reason?

On Sun, Mar 15, 2020 at 9:38 AM YUP  wrote:
>
> Just to inform you, I made proxified kurento websocket in nginx and I
> can connect to it:
> $ wscat -n --connect  https://external_server_ip_address/kurento
> (node:24082) [DEP0123] DeprecationWarning: Setting the TLS ServerName
> to an IP address is not permitted by RFC 6066. This will be ignored in
> a future version.
> Connected (press CTRL+C to quit)
> >
>
> I set
> - OM_KURENTO_WS_URL=https://external_server_ip_address/kurento
> but got
> o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] - Fail to create
> Kurento client, will re-try in 10000 ms
>
>
>
> On Sun, Mar 15, 2020 at 8:56 AM YUP  wrote:
> >
> > Can we just proxify kurento websocket? Something like this
> > https://gist.github.com/steve-ng/ed6de1fa702ef70bd6ce ?
> >
> > On Sun, Mar 15, 2020 at 8:41 AM Maxim Solodovnik  
> > wrote:
> > >
> > > It seems I misread your previous email "all ports except 443, 80, 8080 
> > > and 22."
> > > I'm afraid you need more open ports ...
> > >
> > > I'm not sure but I would investigate if KMS/TURN URLs can be set up
> > > for context i.e.
> > > yourserver:4278/turn, yourserver:/kms in this case you can proxy them 
> > > 
> > >
> > > On Sun, 15 Mar 2020 at 14:32, YUP  wrote:
> > > >
> > > > It nothing changes, only 443 is open to the world.
> > > >
> > > > On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik  
> > > > wrote:
> > > > >
> > > > > Maybe you can set up KMS to use 8080?
> > > > > TURN requires more open port to handle "totally closed" networks ...
> > > > >
> > > > > On Sun, 15 Mar 2020 at 14:18, YUP  wrote:
> > > > > >
> > > > > > It seems to me that I found what is happening. Firewall blocks all 
> > > > > > non
> > > > > > http requests out to all ports except 443, 80, 8080 and 22. That is
> > > > > > why I don't have connection to outside turn ans stun servers. Is it
> > > > > > possible to connect to those server in such conditions? Tunnels?
> > > > > >
> > > > > > On Fri, Mar 13, 2020 at 1:09 AM YUP  wrote:
> > > > > > >
> > > > > > > Hello all,
> > > > > > > Could someone help me with configuration of my OM setup? Any help 
> > > > > > > will
> > > > > > > be  greatly appreciated.
> > > > > > > I have a server which is for several reasons behind NAT, only 443 
> > > > > > > port
> > > > > > > is open. There is sslh balancer, which redirect external traffic 
> > > > > > > to
> > > > > > > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 
> > > > > > > minimal
> > > > > > > installed in container behind nginx proxy and works well, except 
> > > > > > > audio
> > > > > > > and video. When I perform setup check after logged in (video 
> > > > > > > camera
> > > > > > > and microphone) I can see myself in camera and can also see 
> > > > > > > increasing
> > > > > > > and decreasing green line, which indicate microphone level, but I
> > > > > > > can't save and replay the testing record. As far I understand the
> > > > > > > problem is in NAT, so I had to use kurento server with TURN 
> > > > > > > server. I
> > > > > > > did that by adding the environment variables for kurento server in
> > > > > > > docker container with the corresponding data for 
> > > > > > > turn.anyfirewall.com:
> > > > > > >
> > > > > > >  - KMS_STUN_IP=130.211.143.110
> > > > > > >  - KMS_STUN_PORT=443
> > > > > > >  - KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp
> > > > > > > and the same for openmeetings docker container:
> > > > > > >
> > > > > > >   - TURN_USER=webrtc
> > > > > > >   - TURN_PASS=webrtc
> > > > > > >   - TURN_URL=130.211.143.110:443?transport=tcp
> > > > > > >
> > > > > > > After restarting it allowed me immediately to perform network test
> > > > > > > (except ip ping), but not resolved the issue with camera and
> > > > > > > microphone.
> > > > > > > When I connect to OM server with help of vpn (so I and OM server 
> > > > > > > are
> > > > > > > in the same network) everything works as needed. I can save and 
> > > > > > > replay
> > > > > > > video, I can hear myself, two OM users connected by vpn to OM 
> > > > > > > server
> > > > > > > can talk to each other, etc. But it is not an option use vpn
> > > > > > > connection...
> > > > > > > I spent two days to find what I did wrong. I tried another TURN 
> > > > > > > and
> > > > > > > STUN servers, different type of configurations and so on, nothing
> > > > > > > helped.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Yarema
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > WBR
> > > > > Maxim aka solomax
> > >
> > >
> > >
> > > --
> > > WBR
> > > Maxim aka solomax

Re: Openmeetings, kurento and TURN behind NAT

[YUP]

Just to inform you, I made proxified kurento websocket in nginx and I
can connect to it:
$ wscat -n --connect  https://external_server_ip_address/kurento
(node:24082) [DEP0123] DeprecationWarning: Setting the TLS ServerName
to an IP address is not permitted by RFC 6066. This will be ignored in
a future version.
Connected (press CTRL+C to quit)
>

I set
- OM_KURENTO_WS_URL=https://external_server_ip_address/kurento
but got
o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] - Fail to create
Kurento client, will re-try in 1 ms



On Sun, Mar 15, 2020 at 8:56 AM YUP  wrote:
>
> Can we just proxify kurento websocket? Something like this
> https://gist.github.com/steve-ng/ed6de1fa702ef70bd6ce ?
>
> On Sun, Mar 15, 2020 at 8:41 AM Maxim Solodovnik  wrote:
> >
> > It seems I misread your previous email "all ports except 443, 80, 8080 and 
> > 22."
> > I'm afraid you need more open ports ...
> >
> > I'm not sure but I would investigate if KMS/TURN URLs can be set up
> > for context i.e.
> > yourserver:4278/turn, yourserver:/kms in this case you can proxy them 
> > 
> >
> > On Sun, 15 Mar 2020 at 14:32, YUP  wrote:
> > >
> > > It nothing changes, only 443 is open to the world.
> > >
> > > On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik  
> > > wrote:
> > > >
> > > > Maybe you can set up KMS to use 8080?
> > > > TURN requires more open port to handle "totally closed" networks ...
> > > >
> > > > On Sun, 15 Mar 2020 at 14:18, YUP  wrote:
> > > > >
> > > > > It seems to me that I found what is happening. Firewall blocks all non
> > > > > http requests out to all ports except 443, 80, 8080 and 22. That is
> > > > > why I don't have connection to outside turn ans stun servers. Is it
> > > > > possible to connect to those server in such conditions? Tunnels?
> > > > >
> > > > > On Fri, Mar 13, 2020 at 1:09 AM YUP  wrote:
> > > > > >
> > > > > > Hello all,
> > > > > > Could someone help me with configuration of my OM setup? Any help 
> > > > > > will
> > > > > > be  greatly appreciated.
> > > > > > I have a server which is for several reasons behind NAT, only 443 
> > > > > > port
> > > > > > is open. There is sslh balancer, which redirect external traffic to
> > > > > > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 
> > > > > > minimal
> > > > > > installed in container behind nginx proxy and works well, except 
> > > > > > audio
> > > > > > and video. When I perform setup check after logged in (video camera
> > > > > > and microphone) I can see myself in camera and can also see 
> > > > > > increasing
> > > > > > and decreasing green line, which indicate microphone level, but I
> > > > > > can't save and replay the testing record. As far I understand the
> > > > > > problem is in NAT, so I had to use kurento server with TURN server. 
> > > > > > I
> > > > > > did that by adding the environment variables for kurento server in
> > > > > > docker container with the corresponding data for 
> > > > > > turn.anyfirewall.com:
> > > > > >
> > > > > >  - KMS_STUN_IP=130.211.143.110
> > > > > >  - KMS_STUN_PORT=443
> > > > > >  - KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp
> > > > > > and the same for openmeetings docker container:
> > > > > >
> > > > > >   - TURN_USER=webrtc
> > > > > >   - TURN_PASS=webrtc
> > > > > >   - TURN_URL=130.211.143.110:443?transport=tcp
> > > > > >
> > > > > > After restarting it allowed me immediately to perform network test
> > > > > > (except ip ping), but not resolved the issue with camera and
> > > > > > microphone.
> > > > > > When I connect to OM server with help of vpn (so I and OM server are
> > > > > > in the same network) everything works as needed. I can save and 
> > > > > > replay
> > > > > > video, I can hear myself, two OM users connected by vpn to OM server
> > > > > > can talk to each other, etc. But it is not an option use vpn
> > > > > > connection...
> > > > > > I spent two days to find what I did wrong. I tried another TURN and
> > > > > > STUN servers, different type of configurations and so on, nothing
> > > > > > helped.
> > > > > >
> > > > > > Regards,
> > > > > > Yarema
> > > >
> > > >
> > > >
> > > > --
> > > > WBR
> > > > Maxim aka solomax
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax

Re: Openmeetings, kurento and TURN behind NAT

[YUP]

Can we just proxify kurento websocket? Something like this
https://gist.github.com/steve-ng/ed6de1fa702ef70bd6ce ?

On Sun, Mar 15, 2020 at 8:41 AM Maxim Solodovnik  wrote:
>
> It seems I misread your previous email "all ports except 443, 80, 8080 and 
> 22."
> I'm afraid you need more open ports ...
>
> I'm not sure but I would investigate if KMS/TURN URLs can be set up
> for context i.e.
> yourserver:4278/turn, yourserver:/kms in this case you can proxy them 
>
> On Sun, 15 Mar 2020 at 14:32, YUP  wrote:
> >
> > It nothing changes, only 443 is open to the world.
> >
> > On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik  
> > wrote:
> > >
> > > Maybe you can set up KMS to use 8080?
> > > TURN requires more open port to handle "totally closed" networks ...
> > >
> > > On Sun, 15 Mar 2020 at 14:18, YUP  wrote:
> > > >
> > > > It seems to me that I found what is happening. Firewall blocks all non
> > > > http requests out to all ports except 443, 80, 8080 and 22. That is
> > > > why I don't have connection to outside turn ans stun servers. Is it
> > > > possible to connect to those server in such conditions? Tunnels?
> > > >
> > > > On Fri, Mar 13, 2020 at 1:09 AM YUP  wrote:
> > > > >
> > > > > Hello all,
> > > > > Could someone help me with configuration of my OM setup? Any help will
> > > > > be  greatly appreciated.
> > > > > I have a server which is for several reasons behind NAT, only 443 port
> > > > > is open. There is sslh balancer, which redirect external traffic to
> > > > > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 minimal
> > > > > installed in container behind nginx proxy and works well, except audio
> > > > > and video. When I perform setup check after logged in (video camera
> > > > > and microphone) I can see myself in camera and can also see increasing
> > > > > and decreasing green line, which indicate microphone level, but I
> > > > > can't save and replay the testing record. As far I understand the
> > > > > problem is in NAT, so I had to use kurento server with TURN server. I
> > > > > did that by adding the environment variables for kurento server in
> > > > > docker container with the corresponding data for turn.anyfirewall.com:
> > > > >
> > > > >  - KMS_STUN_IP=130.211.143.110
> > > > >  - KMS_STUN_PORT=443
> > > > >  - KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp
> > > > > and the same for openmeetings docker container:
> > > > >
> > > > >   - TURN_USER=webrtc
> > > > >   - TURN_PASS=webrtc
> > > > >   - TURN_URL=130.211.143.110:443?transport=tcp
> > > > >
> > > > > After restarting it allowed me immediately to perform network test
> > > > > (except ip ping), but not resolved the issue with camera and
> > > > > microphone.
> > > > > When I connect to OM server with help of vpn (so I and OM server are
> > > > > in the same network) everything works as needed. I can save and replay
> > > > > video, I can hear myself, two OM users connected by vpn to OM server
> > > > > can talk to each other, etc. But it is not an option use vpn
> > > > > connection...
> > > > > I spent two days to find what I did wrong. I tried another TURN and
> > > > > STUN servers, different type of configurations and so on, nothing
> > > > > helped.
> > > > >
> > > > > Regards,
> > > > > Yarema
> > >
> > >
> > >
> > > --
> > > WBR
> > > Maxim aka solomax
>
>
>
> --
> WBR
> Maxim aka solomax

Re: Openmeetings, kurento and TURN behind NAT

[YUP]

It nothing changes, only 443 is open to the world.

On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik  wrote:
>
> Maybe you can set up KMS to use 8080?
> TURN requires more open port to handle "totally closed" networks ...
>
> On Sun, 15 Mar 2020 at 14:18, YUP  wrote:
> >
> > It seems to me that I found what is happening. Firewall blocks all non
> > http requests out to all ports except 443, 80, 8080 and 22. That is
> > why I don't have connection to outside turn ans stun servers. Is it
> > possible to connect to those server in such conditions? Tunnels?
> >
> > On Fri, Mar 13, 2020 at 1:09 AM YUP  wrote:
> > >
> > > Hello all,
> > > Could someone help me with configuration of my OM setup? Any help will
> > > be  greatly appreciated.
> > > I have a server which is for several reasons behind NAT, only 443 port
> > > is open. There is sslh balancer, which redirect external traffic to
> > > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 minimal
> > > installed in container behind nginx proxy and works well, except audio
> > > and video. When I perform setup check after logged in (video camera
> > > and microphone) I can see myself in camera and can also see increasing
> > > and decreasing green line, which indicate microphone level, but I
> > > can't save and replay the testing record. As far I understand the
> > > problem is in NAT, so I had to use kurento server with TURN server. I
> > > did that by adding the environment variables for kurento server in
> > > docker container with the corresponding data for turn.anyfirewall.com:
> > >
> > >  - KMS_STUN_IP=130.211.143.110
> > >  - KMS_STUN_PORT=443
> > >  - KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp
> > > and the same for openmeetings docker container:
> > >
> > >   - TURN_USER=webrtc
> > >   - TURN_PASS=webrtc
> > >   - TURN_URL=130.211.143.110:443?transport=tcp
> > >
> > > After restarting it allowed me immediately to perform network test
> > > (except ip ping), but not resolved the issue with camera and
> > > microphone.
> > > When I connect to OM server with help of vpn (so I and OM server are
> > > in the same network) everything works as needed. I can save and replay
> > > video, I can hear myself, two OM users connected by vpn to OM server
> > > can talk to each other, etc. But it is not an option use vpn
> > > connection...
> > > I spent two days to find what I did wrong. I tried another TURN and
> > > STUN servers, different type of configurations and so on, nothing
> > > helped.
> > >
> > > Regards,
> > > Yarema
>
>
>
> --
> WBR
> Maxim aka solomax

Re: Openmeetings, kurento and TURN behind NAT

[YUP]

It seems to me that I found what is happening. Firewall blocks all non
http requests out to all ports except 443, 80, 8080 and 22. That is
why I don't have connection to outside turn ans stun servers. Is it
possible to connect to those server in such conditions? Tunnels?

On Fri, Mar 13, 2020 at 1:09 AM YUP  wrote:
>
> Hello all,
> Could someone help me with configuration of my OM setup? Any help will
> be  greatly appreciated.
> I have a server which is for several reasons behind NAT, only 443 port
> is open. There is sslh balancer, which redirect external traffic to
> different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 minimal
> installed in container behind nginx proxy and works well, except audio
> and video. When I perform setup check after logged in (video camera
> and microphone) I can see myself in camera and can also see increasing
> and decreasing green line, which indicate microphone level, but I
> can't save and replay the testing record. As far I understand the
> problem is in NAT, so I had to use kurento server with TURN server. I
> did that by adding the environment variables for kurento server in
> docker container with the corresponding data for turn.anyfirewall.com:
>
>  - KMS_STUN_IP=130.211.143.110
>  - KMS_STUN_PORT=443
>  - KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp
> and the same for openmeetings docker container:
>
>   - TURN_USER=webrtc
>   - TURN_PASS=webrtc
>   - TURN_URL=130.211.143.110:443?transport=tcp
>
> After restarting it allowed me immediately to perform network test
> (except ip ping), but not resolved the issue with camera and
> microphone.
> When I connect to OM server with help of vpn (so I and OM server are
> in the same network) everything works as needed. I can save and replay
> video, I can hear myself, two OM users connected by vpn to OM server
> can talk to each other, etc. But it is not an option use vpn
> connection...
> I spent two days to find what I did wrong. I tried another TURN and
> STUN servers, different type of configurations and so on, nothing
> helped.
>
> Regards,
> Yarema

Openmeetings, kurento and TURN behind NAT

[YUP]

Hello all,
Could someone help me with configuration of my OM setup? Any help will
be  greatly appreciated.
I have a server which is for several reasons behind NAT, only 443 port
is open. There is sslh balancer, which redirect external traffic to
different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 minimal
installed in container behind nginx proxy and works well, except audio
and video. When I perform setup check after logged in (video camera
and microphone) I can see myself in camera and can also see increasing
and decreasing green line, which indicate microphone level, but I
can't save and replay the testing record. As far I understand the
problem is in NAT, so I had to use kurento server with TURN server. I
did that by adding the environment variables for kurento server in
docker container with the corresponding data for turn.anyfirewall.com:

 - KMS_STUN_IP=130.211.143.110
 - KMS_STUN_PORT=443
 - KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp
and the same for openmeetings docker container:

  - TURN_USER=webrtc
  - TURN_PASS=webrtc
  - TURN_URL=130.211.143.110:443?transport=tcp

After restarting it allowed me immediately to perform network test
(except ip ping), but not resolved the issue with camera and
microphone.
When I connect to OM server with help of vpn (so I and OM server are
in the same network) everything works as needed. I can save and replay
video, I can hear myself, two OM users connected by vpn to OM server
can talk to each other, etc. But it is not an option use vpn
connection...
I spent two days to find what I did wrong. I tried another TURN and
STUN servers, different type of configurations and so on, nothing
helped.

Regards,
Yarema

Re: A bug in OM 5.0.0-M2

[YUP]

Confirm this. I've just created new user and deleted this new account.
Account was deleted, but in "user" tab a note "Purged
a7edd95b-a256-47ea-" still remains.

вт, 24 вер. 2019 о 16:34 Jibsan Joel Rosa Toirac  пише:
>
> Hello I want to share with you this, it might be a bug on the OM 5.0.0-M2 on 
> the .tar.gz file on the official site and in the .iso file too. When you try 
> to delete an user, you have the option "Purge" to completely delete the user 
> but it leave a code on the row where used to be the information about that 
> user on the Users List. This not happen in OM 4.0.0 and when you delete 
> several users, the list start to seems a little "nasty" so I'm happy to share 
> this with you and I hope this can be fixed soon.
>
> Greetings to all.
>
> Jibsan.

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

My OM section in nginx config file looks as follows:

  location /openmeetings {
proxy_pass https://localhost:5443/openmeetings;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Protocol $scheme;
proxy_set_header X-Forwarded-Host $http_host;
}

нд, 22 вер. 2019 о 17:10 YUP  пише:
>
> Hi again,
> There are a few things which I discovered:
> 1. When I install openmeetings locally and KMS in docker (using
> provided instruction for Archlinux) on my laptop with archlinux and
> without (!) nginx and proxy_pass it runs out of the box without any
> problems and records everything I want. But:
> 2. If i do the same but with nginx as a proxy, the behavior is the
> same as I described in my first email.
> 3. When I install full version of openmeetings with mysql and kurento
> by means of docker on host machine with archlinux, the kurento server
> is dead. The reason is very simple, the start script can't define max
> size of the open file. I don't know why it happen for Archlinux.  As a
> workaround it is enough to enter running container with openmeetings,
> comment line with DAEMON_MAX_FILE=... in kurento configuration file
> /etc/default/kurento-media-server, save and start kms: service
> kurento-media-server  start. Then kurento server starts without
> errors. But with nginx and proxy_pass recording doesn't work, and
> works without proxy_pass.
> 4. For some understandable reasons I have only port 443 opened to the
> world, so a method how to get OM work with this environment would be
> highly appreciated.
> Regards,
> Yarema
>
> нд, 22 вер. 2019 о 04:04 Maxim Solodovnik  пише:
> >
> > This actually make no sense :(
> > I always thought docker should work the same for different machines
> >
> > This is my start command and first lines of the output:
> >
> > `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
> > 5443:5443 -p : 
> > openmeetings-docker-images.bintray.io/server-full:latest`
> >  * Stopping MySQL database server mysqld
> >...done.
> >  * Starting MySQL database server mysqld
> >...done.
> > OM server of type full will be run
> >  * Start Kurento Media Server
> >  * Directory '/var/log/kurento-media-server' is not owned by 'nobody'
> >  * Changed owner of '/var/log/kurento-media-server' to 'nobody'
> >  * Configure Kernel resource limits for Kurento Media Server
> >...done.
> >
> > This is the line the KMS is being started:
> > https://github.com/openmeetings/openmeetings-docker/blob/master/scripts/om.sh#L44
> >
> > Have no idea what is going on :(
> >
> >
> > On Sun, 22 Sep 2019 at 01:29, YUP  wrote:
> >>
> >> I checked your image, and got the same result, kurento is dead. I
> >> gonna give up
> >>
> >> $ docker info
> >> Client:
> >>  Debug Mode: false
> >>
> >> Server:
> >>  Containers: 4
> >>   Running: 4
> >>   Paused: 0
> >>   Stopped: 0
> >>  Images: 45
> >>  Server Version: 19.03.2-ce
> >>  Storage Driver: overlay2
> >>   Backing Filesystem: extfs
> >>   Supports d_type: true
> >>   Native Overlay Diff: false
> >>  Logging Driver: json-file
> >>  Cgroup Driver: cgroupfs
> >>  Plugins:
> >>   Volume: local
> >>   Network: bridge host ipvlan macvlan null overlay
> >>   Log: awslogs fluentd gcplogs gelf journald json-file local
> >> logentries splunk syslog
> >>  Swarm: inactive
> >>  Runtimes: runc
> >>  Default Runtime: runc
> >>  Init Binary: docker-init
> >>  containerd version: d50db0a42053864a270f648048f9a8b4f24eced3.m
> >>  runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
> >>  init version: fec3683
> >>  Security Options:
> >>   seccomp
> >>Profile: default
> >>  Kernel Version: 4.19.73-1-lts
> >>  Operating System: Arch Linux
> >>  OSType: linux
> >>  Architecture: x86_64
> >>  CPUs: 2
> >>  Total Memory: 3.789GiB
> >>  Name: archmoodle
> >>  ID: SJE6:7KPL:M7AE:H6RE:CDR6:RK2K:Q2PQ:CD6W:DJOO:V4LZ:2ILL:NCWY
> >>  Docker Root Dir: /home/docker
> >>  Debug Mode: false
> >>  Registry: https://index.docker.io/v1/
> >>  Labels:
&g

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

Hi again,
There are a few things which I discovered:
1. When I install openmeetings locally and KMS in docker (using
provided instruction for Archlinux) on my laptop with archlinux and
without (!) nginx and proxy_pass it runs out of the box without any
problems and records everything I want. But:
2. If i do the same but with nginx as a proxy, the behavior is the
same as I described in my first email.
3. When I install full version of openmeetings with mysql and kurento
by means of docker on host machine with archlinux, the kurento server
is dead. The reason is very simple, the start script can't define max
size of the open file. I don't know why it happen for Archlinux.  As a
workaround it is enough to enter running container with openmeetings,
comment line with DAEMON_MAX_FILE=... in kurento configuration file
/etc/default/kurento-media-server, save and start kms: service
kurento-media-server  start. Then kurento server starts without
errors. But with nginx and proxy_pass recording doesn't work, and
works without proxy_pass.
4. For some understandable reasons I have only port 443 opened to the
world, so a method how to get OM work with this environment would be
highly appreciated.
Regards,
Yarema

нд, 22 вер. 2019 о 04:04 Maxim Solodovnik  пише:
>
> This actually make no sense :(
> I always thought docker should work the same for different machines
>
> This is my start command and first lines of the output:
>
> `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
> 5443:5443 -p : 
> openmeetings-docker-images.bintray.io/server-full:latest`
>  * Stopping MySQL database server mysqld
>...done.
>  * Starting MySQL database server mysqld
>...done.
> OM server of type full will be run
>  * Start Kurento Media Server
>  * Directory '/var/log/kurento-media-server' is not owned by 'nobody'
>  * Changed owner of '/var/log/kurento-media-server' to 'nobody'
>  * Configure Kernel resource limits for Kurento Media Server
>...done.
>
> This is the line the KMS is being started:
> https://github.com/openmeetings/openmeetings-docker/blob/master/scripts/om.sh#L44
>
> Have no idea what is going on :(
>
>
> On Sun, 22 Sep 2019 at 01:29, YUP  wrote:
>>
>> I checked your image, and got the same result, kurento is dead. I
>> gonna give up
>>
>> $ docker info
>> Client:
>>  Debug Mode: false
>>
>> Server:
>>  Containers: 4
>>   Running: 4
>>   Paused: 0
>>   Stopped: 0
>>  Images: 45
>>  Server Version: 19.03.2-ce
>>  Storage Driver: overlay2
>>   Backing Filesystem: extfs
>>   Supports d_type: true
>>   Native Overlay Diff: false
>>  Logging Driver: json-file
>>  Cgroup Driver: cgroupfs
>>  Plugins:
>>   Volume: local
>>   Network: bridge host ipvlan macvlan null overlay
>>   Log: awslogs fluentd gcplogs gelf journald json-file local
>> logentries splunk syslog
>>  Swarm: inactive
>>  Runtimes: runc
>>  Default Runtime: runc
>>  Init Binary: docker-init
>>  containerd version: d50db0a42053864a270f648048f9a8b4f24eced3.m
>>  runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
>>  init version: fec3683
>>  Security Options:
>>   seccomp
>>Profile: default
>>  Kernel Version: 4.19.73-1-lts
>>  Operating System: Arch Linux
>>  OSType: linux
>>  Architecture: x86_64
>>  CPUs: 2
>>  Total Memory: 3.789GiB
>>  Name: archmoodle
>>  ID: SJE6:7KPL:M7AE:H6RE:CDR6:RK2K:Q2PQ:CD6W:DJOO:V4LZ:2ILL:NCWY
>>  Docker Root Dir: /home/docker
>>  Debug Mode: false
>>  Registry: https://index.docker.io/v1/
>>  Labels:
>>  Experimental: false
>>  Insecure Registries:
>>   127.0.0.0/8
>>  Live Restore Enabled: false
>>
>> сб, 21 вер. 2019 о 19:00 Maxim Solodovnik  пише:
>> >
>> > `docker info`
>> >
>> > Server Version: 19.03.2
>> >
>> >
>> > The image is uploaded, everything works as expected
>> > Just have double-checked
>> > `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
>> > 5443:5443 -p : 
>> > openmeetings-docker-images.bintray.io/server-full:latest`
>> >
>> > On Sat, 21 Sep 2019 at 23:43, YUP  wrote:
>> >>
>> >> BTW, what version of docker do you use?
>> >> $ docker info
>> >>
>> >> сб, 21 вер. 2019 о 18:30 YUP  пише:
>> >> >
>> >> > Great, thanks!
>> >> >
>> >> > сб, 21 вер. 2019 о 18:29 Maxim Solodovnik  пише:
>> >> > >
>> >> > > Well
>> >> > > I can upload my im

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

I checked your image, and got the same result, kurento is dead. I
gonna give up

$ docker info
Client:
 Debug Mode: false

Server:
 Containers: 4
  Running: 4
  Paused: 0
  Stopped: 0
 Images: 45
 Server Version: 19.03.2-ce
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local
logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: d50db0a42053864a270f648048f9a8b4f24eced3.m
 runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.19.73-1-lts
 Operating System: Arch Linux
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 3.789GiB
 Name: archmoodle
 ID: SJE6:7KPL:M7AE:H6RE:CDR6:RK2K:Q2PQ:CD6W:DJOO:V4LZ:2ILL:NCWY
 Docker Root Dir: /home/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

сб, 21 вер. 2019 о 19:00 Maxim Solodovnik  пише:
>
> `docker info`
>
> Server Version: 19.03.2
>
>
> The image is uploaded, everything works as expected
> Just have double-checked
> `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
> 5443:5443 -p : 
> openmeetings-docker-images.bintray.io/server-full:latest`
>
> On Sat, 21 Sep 2019 at 23:43, YUP  wrote:
>>
>> BTW, what version of docker do you use?
>> $ docker info
>>
>> сб, 21 вер. 2019 о 18:30 YUP  пише:
>> >
>> > Great, thanks!
>> >
>> > сб, 21 вер. 2019 о 18:29 Maxim Solodovnik  пише:
>> > >
>> > > Well
>> > > I can upload my image to the bintray
>> > > And you can try it
>> > > Will do it tomorrow
>> > >
>> > > On Sat, Sep 21, 2019, 23:14 YUP  wrote:
>> > >>
>> > >> So something is wrong with Archlinux as a host machine and OM in
>> > >> docker. But it is nonsense, created image should not depend from host
>> > >> machine and om+mysql+kurento must run the same way...
>> > >>
>> > >> сб, 21 вер. 2019 о 18:03 Maxim Solodovnik  пише:
>> > >> >
>> > >> > Kurento and mysql are both started right before om
>> > >> > It is very clear from the logs
>> > >> > And both video and recording works in om :)
>> > >> >
>> > >> > On Sat, Sep 21, 2019, 22:55 YUP  wrote:
>> > >> >>
>> > >> >> OK. Please enter your container with running OM:
>> > >> >>
>> > >> >> docker exec -it CONTAINER_ID bash
>> > >> >> and then check whether kurento running:
>> > >> >> ps xuaw | grep kurento
>> > >> >> or
>> > >> >> service kurento-media-server status
>> > >> >> and post the result, please.
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >> сб, 21 вер. 2019 о 16:59 Maxim Solodovnik  
>> > >> >> пише:
>> > >> >> >
>> > >> >> > `docker build -t om-server-full --build-arg BUILD_TYPE=full .`
>> > >> >> > `docker run -i --rm --name om-server-full --expose=5443 
>> > >> >> > --expose= -p 5443:5443 -p : -e OM_TYPE=full -it 
>> > >> >> > om-server-full`
>> > >> >> >
>> > >> >> > works as expected :)
>> > >> >> >
>> > >> >> > On Sat, 21 Sep 2019 at 20:37, YUP  wrote:
>> > >> >> >>
>> > >> >> >> > Will provide you with the complete list of commands I run
>> > >> >> >> Thanks, it will be useful!
>> > >> >> >>
>> > >> >> >> > BTW just found this thread: 
>> > >> >> >> > https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
>> > >> >> >> > Might be useful for nginx users
>> > >> >> >>
>> > >> >> >> I'll check it.
>> > >> >> >> Regards,
>> > >> >> >> Yarema
>> > >> >> >
>> > >> >> >
>> > >> >> >
>> > >> >> > --
>> > >> >> > WBR
>> > >> >> > Maxim aka solomax
>
>
>
> --
> WBR
> Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

Great, thanks!

сб, 21 вер. 2019 о 18:29 Maxim Solodovnik  пише:
>
> Well
> I can upload my image to the bintray
> And you can try it
> Will do it tomorrow
>
> On Sat, Sep 21, 2019, 23:14 YUP  wrote:
>>
>> So something is wrong with Archlinux as a host machine and OM in
>> docker. But it is nonsense, created image should not depend from host
>> machine and om+mysql+kurento must run the same way...
>>
>> сб, 21 вер. 2019 о 18:03 Maxim Solodovnik  пише:
>> >
>> > Kurento and mysql are both started right before om
>> > It is very clear from the logs
>> > And both video and recording works in om :)
>> >
>> > On Sat, Sep 21, 2019, 22:55 YUP  wrote:
>> >>
>> >> OK. Please enter your container with running OM:
>> >>
>> >> docker exec -it CONTAINER_ID bash
>> >> and then check whether kurento running:
>> >> ps xuaw | grep kurento
>> >> or
>> >> service kurento-media-server status
>> >> and post the result, please.
>> >>
>> >>
>> >>
>> >>
>> >> сб, 21 вер. 2019 о 16:59 Maxim Solodovnik  пише:
>> >> >
>> >> > `docker build -t om-server-full --build-arg BUILD_TYPE=full .`
>> >> > `docker run -i --rm --name om-server-full --expose=5443 --expose= 
>> >> > -p 5443:5443 -p : -e OM_TYPE=full -it om-server-full`
>> >> >
>> >> > works as expected :)
>> >> >
>> >> > On Sat, 21 Sep 2019 at 20:37, YUP  wrote:
>> >> >>
>> >> >> > Will provide you with the complete list of commands I run
>> >> >> Thanks, it will be useful!
>> >> >>
>> >> >> > BTW just found this thread: 
>> >> >> > https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
>> >> >> > Might be useful for nginx users
>> >> >>
>> >> >> I'll check it.
>> >> >> Regards,
>> >> >> Yarema
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > WBR
>> >> > Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

I've just installed on another Archlinux machine and result was the
same, kurento won't start. Damn.

сб, 21 вер. 2019 о 18:13 YUP  пише:
>
> So something is wrong with Archlinux as a host machine and OM in
> docker. But it is nonsense, created image should not depend from host
> machine and om+mysql+kurento must run the same way...
>
> сб, 21 вер. 2019 о 18:03 Maxim Solodovnik  пише:
> >
> > Kurento and mysql are both started right before om
> > It is very clear from the logs
> > And both video and recording works in om :)
> >
> > On Sat, Sep 21, 2019, 22:55 YUP  wrote:
> >>
> >> OK. Please enter your container with running OM:
> >>
> >> docker exec -it CONTAINER_ID bash
> >> and then check whether kurento running:
> >> ps xuaw | grep kurento
> >> or
> >> service kurento-media-server status
> >> and post the result, please.
> >>
> >>
> >>
> >>
> >> сб, 21 вер. 2019 о 16:59 Maxim Solodovnik  пише:
> >> >
> >> > `docker build -t om-server-full --build-arg BUILD_TYPE=full .`
> >> > `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
> >> > 5443:5443 -p : -e OM_TYPE=full -it om-server-full`
> >> >
> >> > works as expected :)
> >> >
> >> > On Sat, 21 Sep 2019 at 20:37, YUP  wrote:
> >> >>
> >> >> > Will provide you with the complete list of commands I run
> >> >> Thanks, it will be useful!
> >> >>
> >> >> > BTW just found this thread: 
> >> >> > https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
> >> >> > Might be useful for nginx users
> >> >>
> >> >> I'll check it.
> >> >> Regards,
> >> >> Yarema
> >> >
> >> >
> >> >
> >> > --
> >> > WBR
> >> > Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

So something is wrong with Archlinux as a host machine and OM in
docker. But it is nonsense, created image should not depend from host
machine and om+mysql+kurento must run the same way...

сб, 21 вер. 2019 о 18:03 Maxim Solodovnik  пише:
>
> Kurento and mysql are both started right before om
> It is very clear from the logs
> And both video and recording works in om :)
>
> On Sat, Sep 21, 2019, 22:55 YUP  wrote:
>>
>> OK. Please enter your container with running OM:
>>
>> docker exec -it CONTAINER_ID bash
>> and then check whether kurento running:
>> ps xuaw | grep kurento
>> or
>> service kurento-media-server status
>> and post the result, please.
>>
>>
>>
>>
>> сб, 21 вер. 2019 о 16:59 Maxim Solodovnik  пише:
>> >
>> > `docker build -t om-server-full --build-arg BUILD_TYPE=full .`
>> > `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
>> > 5443:5443 -p : -e OM_TYPE=full -it om-server-full`
>> >
>> > works as expected :)
>> >
>> > On Sat, 21 Sep 2019 at 20:37, YUP  wrote:
>> >>
>> >> > Will provide you with the complete list of commands I run
>> >> Thanks, it will be useful!
>> >>
>> >> > BTW just found this thread: 
>> >> > https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
>> >> > Might be useful for nginx users
>> >>
>> >> I'll check it.
>> >> Regards,
>> >> Yarema
>> >
>> >
>> >
>> > --
>> > WBR
>> > Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

OK. Please enter your container with running OM:

docker exec -it CONTAINER_ID bash
and then check whether kurento running:
ps xuaw | grep kurento
or
service kurento-media-server status
and post the result, please.




сб, 21 вер. 2019 о 16:59 Maxim Solodovnik  пише:
>
> `docker build -t om-server-full --build-arg BUILD_TYPE=full .`
> `docker run -i --rm --name om-server-full --expose=5443 --expose= -p 
> 5443:5443 -p : -e OM_TYPE=full -it om-server-full`
>
> works as expected :)
>
> On Sat, 21 Sep 2019 at 20:37, YUP  wrote:
>>
>> > Will provide you with the complete list of commands I run
>> Thanks, it will be useful!
>>
>> > BTW just found this thread: 
>> > https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
>> > Might be useful for nginx users
>>
>> I'll check it.
>> Regards,
>> Yarema
>
>
>
> --
> WBR
> Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

> Will provide you with the complete list of commands I run
Thanks, it will be useful!

> BTW just found this thread: 
> https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
> Might be useful for nginx users

I'll check it.
Regards,
Yarema

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

Yes, it is latest master with om 5.0.0-M2.

On Sat, Sep 21, 2019, 08:56 Maxim Solodovnik  wrote:

> Are you using latest master?
> It works for me as expected
>
> On Sat, Sep 21, 2019, 11:32 YUP  wrote:
>
>> Installing OM 5.0.0-M2 docker:
>>
>> $ docker build -t om-server-full --build-arg BUILD_TYPE=full .
>> $ docker run --expose= -p 5443:5443 -p : -e OM_TYPE=full
>> -it om-server-full
>>
>> 
>>
>> DEBUG 09-21 04:23:25.988 o.a.o.i.ImportInitvalues:360 [main] -
>> Configurations ADDED
>> INFO  09-21 04:23:26.379 o.a.o.d.d.u.UserDao:290 [main] - [get]: No
>> user id given
>> DEBUG 09-21 04:23:26.711 o.a.o.u.c.CryptProvider:39 [main] - get::
>> configKeyCryptClassName:
>> org.apache.openmeetings.util.crypt.SCryptImplemen
>> tation
>> INFO  09-21 04:23:27.169 o.k.j.c.JsonRpcClientNettyWebSocket:191
>> [pool-1-thread-1] - [KurentoClient]  Connecting native client
>> INFO  09-21 04:23:27.169 o.k.j.c.JsonRpcClientNettyWebSocket:220
>> [pool-1-thread-1] - [KurentoClient]  Creating new NioEventLoopGroup
>> INFO  09-21 04:23:27.229 o.k.j.c.JsonRpcClientNettyWebSocket:234
>> [ntLoopGroup-8-1] - [KurentoClient]  Initiating new Netty channel.
>> Will crea
>> te new handler too!
>> WARN  09-21 04:23:27.293 o.k.j.c.JsonRpcClientNettyWebSocket:308
>> [pool-1-thread-1] - [KurentoClient]  Trying to close a
>> JsonRpcClientNettyWeb
>> Socket with channel == null
>> WARN  09-21 04:23:27.295 o.k.j.c.JsonRpcClient:270 [beatExec-e17-t0] -
>> [KurentoClient]  Error sending heartbeat to server. Exception: Interru
>> ptedException while trying to acquire lock
>> WARN  09-21 04:23:27.297 o.k.j.c.JsonRpcClient:287 [beatExec-e17-t0] -
>> [KurentoClient]  Stopping heartbeat and closing client: failure during
>>  heartbeat mechanism
>> WARN  09-21 04:23:27.295 o.a.o.c.r.KurentoHandler:124
>> [pool-1-thread-1] - Fail to create Kurento client, will re-try in
>> 1 ms
>> ..
>>
>> That's it. Kurento server doesn't work.
>>
>>
>>
>> сб, 21 вер. 2019 о 06:02 YUP  пише:
>> >
>> > Gonna try...
>> >
>> > сб, 21 вер. 2019 о 04:11 Maxim Solodovnik  пише:
>> > >
>> > > Just have updated master at
>> https://github.com/openmeetings/openmeetings-docker
>> > > Tests recordings works for me as expected
>> > >
>> > > On Fri, 20 Sep 2019 at 20:56, Maxim Solodovnik 
>> wrote:
>> > >>
>> > >> Actually current master is still M1 
>> > >> And it was working last time I test it :)
>> > >> Checking it right now
>> > >>
>> > >> On Fri, Sep 20, 2019, 20:53 YUP  wrote:
>> > >>>
>> > >>> Sure, it should start, but it doesn't. Something is wrong with
>> environment in ubuntu in docker, that is why commands
>> /etc/init.d/kurento-media-server start or service kurento-media-server
>> start fails.
>> > >>>
>> > >>>
>> > >>> On Fri, Sep 20, 2019, 15:47 Maxim Solodovnik 
>> wrote:
>> > >>>>
>> > >>>> Actually https://github.com/openmeetings/openmeetings-docker
>> > >>>> Is a little bit outdated (will update it to M2 ASAP)
>> > >>>> KMS currently being started every time docker is started
>> > >>>> please check
>> https://github.com/openmeetings/openmeetings-docker/blob/master/scripts/om.sh
>> > >>>>
>> > >>>> On Fri, 20 Sep 2019 at 19:59, YUP  wrote:
>> > >>>>>
>> > >>>>> I'm not using KMS in a standalone docker. I'm using docker with
>> > >>>>> OM+mysql+kurento:
>> > >>>>>
>> > >>>>> docker build -t om-server-full --build-arg BUILD_TYPE=full .
>> > >>>>>
>> > >>>>> пт, 20 вер. 2019 о 14:56 Maxim Solodovnik 
>> пише:
>> > >>>>> >
>> > >>>>> > Why do you using KMS in docker in Ubuntu?
>> > >>>>> >
>> > >>>>> > On Fri, 20 Sep 2019 at 19:54, YUP  wrote:
>> > >>>>> >>
>> > >>>>> >> Well, I reinstalled Openmeetings full version
>> > >>>>> >> (ubuntu+OM+mysql+kurento)  in a docker, and I have to say that
>> > >>>>> >> installation of Kurento Media Server
>> &g

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

Installing OM 5.0.0-M2 docker:

$ docker build -t om-server-full --build-arg BUILD_TYPE=full .
$ docker run --expose= -p 5443:5443 -p : -e OM_TYPE=full
-it om-server-full



DEBUG 09-21 04:23:25.988 o.a.o.i.ImportInitvalues:360 [main] -
Configurations ADDED
INFO  09-21 04:23:26.379 o.a.o.d.d.u.UserDao:290 [main] - [get]: No
user id given
DEBUG 09-21 04:23:26.711 o.a.o.u.c.CryptProvider:39 [main] - get::
configKeyCryptClassName:
org.apache.openmeetings.util.crypt.SCryptImplemen
tation
INFO  09-21 04:23:27.169 o.k.j.c.JsonRpcClientNettyWebSocket:191
[pool-1-thread-1] - [KurentoClient]  Connecting native client
INFO  09-21 04:23:27.169 o.k.j.c.JsonRpcClientNettyWebSocket:220
[pool-1-thread-1] - [KurentoClient]  Creating new NioEventLoopGroup
INFO  09-21 04:23:27.229 o.k.j.c.JsonRpcClientNettyWebSocket:234
[ntLoopGroup-8-1] - [KurentoClient]  Initiating new Netty channel.
Will crea
te new handler too!
WARN  09-21 04:23:27.293 o.k.j.c.JsonRpcClientNettyWebSocket:308
[pool-1-thread-1] - [KurentoClient]  Trying to close a
JsonRpcClientNettyWeb
Socket with channel == null
WARN  09-21 04:23:27.295 o.k.j.c.JsonRpcClient:270 [beatExec-e17-t0] -
[KurentoClient]  Error sending heartbeat to server. Exception: Interru
ptedException while trying to acquire lock
WARN  09-21 04:23:27.297 o.k.j.c.JsonRpcClient:287 [beatExec-e17-t0] -
[KurentoClient]  Stopping heartbeat and closing client: failure during
 heartbeat mechanism
WARN  09-21 04:23:27.295 o.a.o.c.r.KurentoHandler:124
[pool-1-thread-1] - Fail to create Kurento client, will re-try in
1 ms
..

That's it. Kurento server doesn't work.



сб, 21 вер. 2019 о 06:02 YUP  пише:
>
> Gonna try...
>
> сб, 21 вер. 2019 о 04:11 Maxim Solodovnik  пише:
> >
> > Just have updated master at 
> > https://github.com/openmeetings/openmeetings-docker
> > Tests recordings works for me as expected
> >
> > On Fri, 20 Sep 2019 at 20:56, Maxim Solodovnik  wrote:
> >>
> >> Actually current master is still M1 
> >> And it was working last time I test it :)
> >> Checking it right now
> >>
> >> On Fri, Sep 20, 2019, 20:53 YUP  wrote:
> >>>
> >>> Sure, it should start, but it doesn't. Something is wrong with 
> >>> environment in ubuntu in docker, that is why commands 
> >>> /etc/init.d/kurento-media-server start or service kurento-media-server 
> >>> start fails.
> >>>
> >>>
> >>> On Fri, Sep 20, 2019, 15:47 Maxim Solodovnik  wrote:
> >>>>
> >>>> Actually https://github.com/openmeetings/openmeetings-docker
> >>>> Is a little bit outdated (will update it to M2 ASAP)
> >>>> KMS currently being started every time docker is started
> >>>> please check 
> >>>> https://github.com/openmeetings/openmeetings-docker/blob/master/scripts/om.sh
> >>>>
> >>>> On Fri, 20 Sep 2019 at 19:59, YUP  wrote:
> >>>>>
> >>>>> I'm not using KMS in a standalone docker. I'm using docker with
> >>>>> OM+mysql+kurento:
> >>>>>
> >>>>> docker build -t om-server-full --build-arg BUILD_TYPE=full .
> >>>>>
> >>>>> пт, 20 вер. 2019 о 14:56 Maxim Solodovnik  пише:
> >>>>> >
> >>>>> > Why do you using KMS in docker in Ubuntu?
> >>>>> >
> >>>>> > On Fri, 20 Sep 2019 at 19:54, YUP  wrote:
> >>>>> >>
> >>>>> >> Well, I reinstalled Openmeetings full version
> >>>>> >> (ubuntu+OM+mysql+kurento)  in a docker, and I have to say that
> >>>>> >> installation of Kurento Media Server
> >>>>> >> is broken. Kurrento have never started. Something is wrong with
> >>>>> >> kurento init script, or most likely with ubuntu installation.
> >>>>> >> You can easily check it. Steps to reproduce:
> >>>>> >> 1. Install OM full using instructions
> >>>>> >> 2. Start container
> >>>>> >> 3. Enter container: docker exec -it  bash
> >>>>> >> 4. Check whether kurento runs:
> >>>>> >> ps xuaw | grep kurento
> >>>>> >> or try to start service:
> >>>>> >> service kurento-media-server start
> >>>>> >> This gives error:
> >>>>> >>  * Start Kurento Media Server
> >>>>> >>  * Configure Kernel resource limits for Kurento Media Server

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

Gonna try...

сб, 21 вер. 2019 о 04:11 Maxim Solodovnik  пише:
>
> Just have updated master at 
> https://github.com/openmeetings/openmeetings-docker
> Tests recordings works for me as expected
>
> On Fri, 20 Sep 2019 at 20:56, Maxim Solodovnik  wrote:
>>
>> Actually current master is still M1 
>> And it was working last time I test it :)
>> Checking it right now
>>
>> On Fri, Sep 20, 2019, 20:53 YUP  wrote:
>>>
>>> Sure, it should start, but it doesn't. Something is wrong with environment 
>>> in ubuntu in docker, that is why commands /etc/init.d/kurento-media-server 
>>> start or service kurento-media-server start fails.
>>>
>>>
>>> On Fri, Sep 20, 2019, 15:47 Maxim Solodovnik  wrote:
>>>>
>>>> Actually https://github.com/openmeetings/openmeetings-docker
>>>> Is a little bit outdated (will update it to M2 ASAP)
>>>> KMS currently being started every time docker is started
>>>> please check 
>>>> https://github.com/openmeetings/openmeetings-docker/blob/master/scripts/om.sh
>>>>
>>>> On Fri, 20 Sep 2019 at 19:59, YUP  wrote:
>>>>>
>>>>> I'm not using KMS in a standalone docker. I'm using docker with
>>>>> OM+mysql+kurento:
>>>>>
>>>>> docker build -t om-server-full --build-arg BUILD_TYPE=full .
>>>>>
>>>>> пт, 20 вер. 2019 о 14:56 Maxim Solodovnik  пише:
>>>>> >
>>>>> > Why do you using KMS in docker in Ubuntu?
>>>>> >
>>>>> > On Fri, 20 Sep 2019 at 19:54, YUP  wrote:
>>>>> >>
>>>>> >> Well, I reinstalled Openmeetings full version
>>>>> >> (ubuntu+OM+mysql+kurento)  in a docker, and I have to say that
>>>>> >> installation of Kurento Media Server
>>>>> >> is broken. Kurrento have never started. Something is wrong with
>>>>> >> kurento init script, or most likely with ubuntu installation.
>>>>> >> You can easily check it. Steps to reproduce:
>>>>> >> 1. Install OM full using instructions
>>>>> >> 2. Start container
>>>>> >> 3. Enter container: docker exec -it  bash
>>>>> >> 4. Check whether kurento runs:
>>>>> >> ps xuaw | grep kurento
>>>>> >> or try to start service:
>>>>> >> service kurento-media-server start
>>>>> >> This gives error:
>>>>> >>  * Start Kurento Media Server
>>>>> >>  * Configure Kernel resource limits for Kurento Media Server
>>>>> >> /etc/init.d/kurento-media-server: 118:
>>>>> >> /etc/init.d/kurento-media-server: Pipe call failed
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> 3.
>>>>> >>
>>>>> >> пт, 20 вер. 2019 о 12:07 YUP  пише:
>>>>> >> >
>>>>> >> > You gave me a hint. Ill check it.
>>>>> >> >
>>>>> >> > пт, 20 вер. 2019 о 09:17 Maxim Solodovnik  
>>>>> >> > пише:
>>>>> >> > >
>>>>> >> > > WebM files are being written by KMS
>>>>> >> > > Maybe you get some info from KMS logs on your system?
>>>>> >> > >
>>>>> >> > > (I'm using Ubuntu on daily basis, never saw such behavior)
>>>>> >> > >
>>>>> >> > > On Fri, 20 Sep 2019 at 14:13, YUP  wrote:
>>>>> >> > >>
>>>>> >> > >> nobody:nogroup
>>>>> >> > >>
>>>>> >> > >> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik  
>>>>> >> > >> пише:
>>>>> >> > >> >
>>>>> >> > >> > Can you check files have correct owner?
>>>>> >> > >> >
>>>>> >> > >> > On Fri, 20 Sep 2019 at 14:09, YUP  wrote:
>>>>> >> > >> >>
>>>>> >> > >> >> That's right, they are placed in correct places, but have 0 
>>>>> >> > >> >> bytes.
>>>>&g

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

Sure, it should start, but it doesn't. Something is wrong with environment
in ubuntu in docker, that is why commands /etc/init.d/kurento-media-server
start or service kurento-media-server start fails.


On Fri, Sep 20, 2019, 15:47 Maxim Solodovnik  wrote:

> Actually https://github.com/openmeetings/openmeetings-docker
> Is a little bit outdated (will update it to M2 ASAP)
> KMS currently being started every time docker is started
> please check
> https://github.com/openmeetings/openmeetings-docker/blob/master/scripts/om.sh
>
> On Fri, 20 Sep 2019 at 19:59, YUP  wrote:
>
>> I'm not using KMS in a standalone docker. I'm using docker with
>> OM+mysql+kurento:
>>
>> docker build -t om-server-full --build-arg BUILD_TYPE=full .
>>
>> пт, 20 вер. 2019 о 14:56 Maxim Solodovnik  пише:
>> >
>> > Why do you using KMS in docker in Ubuntu?
>> >
>> > On Fri, 20 Sep 2019 at 19:54, YUP  wrote:
>> >>
>> >> Well, I reinstalled Openmeetings full version
>> >> (ubuntu+OM+mysql+kurento)  in a docker, and I have to say that
>> >> installation of Kurento Media Server
>> >> is broken. Kurrento have never started. Something is wrong with
>> >> kurento init script, or most likely with ubuntu installation.
>> >> You can easily check it. Steps to reproduce:
>> >> 1. Install OM full using instructions
>> >> 2. Start container
>> >> 3. Enter container: docker exec -it  bash
>> >> 4. Check whether kurento runs:
>> >> ps xuaw | grep kurento
>> >> or try to start service:
>> >> service kurento-media-server start
>> >> This gives error:
>> >>  * Start Kurento Media Server
>> >>  * Configure Kernel resource limits for Kurento Media Server
>> >> /etc/init.d/kurento-media-server: 118:
>> >> /etc/init.d/kurento-media-server: Pipe call failed
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> 3.
>> >>
>> >> пт, 20 вер. 2019 о 12:07 YUP  пише:
>> >> >
>> >> > You gave me a hint. Ill check it.
>> >> >
>> >> > пт, 20 вер. 2019 о 09:17 Maxim Solodovnik 
>> пише:
>> >> > >
>> >> > > WebM files are being written by KMS
>> >> > > Maybe you get some info from KMS logs on your system?
>> >> > >
>> >> > > (I'm using Ubuntu on daily basis, never saw such behavior)
>> >> > >
>> >> > > On Fri, 20 Sep 2019 at 14:13, YUP  wrote:
>> >> > >>
>> >> > >> nobody:nogroup
>> >> > >>
>> >> > >> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik 
>> пише:
>> >> > >> >
>> >> > >> > Can you check files have correct owner?
>> >> > >> >
>> >> > >> > On Fri, 20 Sep 2019 at 14:09, YUP  wrote:
>> >> > >> >>
>> >> > >> >> That's right, they are placed in correct places, but have 0
>> bytes.
>> >> > >> >>
>> >> > >> >> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik <
>> solomax...@gmail.com> пише:
>> >> > >> >> >
>> >> > >> >> > Hello Yarema,
>> >> > >> >> >
>> >> > >> >> > so `webm` files are being created in correct place? but they
>> are empty?
>> >> > >> >> >
>> >> > >> >> > On Fri, 20 Sep 2019 at 04:19, YUP 
>> wrote:
>> >> > >> >> >>
>> >> > >> >> >> Hi,
>> >> > >> >> >> I installed full OM by means of docker on archlinux host
>> machine,
>> >> > >> >> >> using provided instruction. I even managed to work
>> >> > >> >> >> kurento-media-server, which doesn't work out of a box in OM
>> container.
>> >> > >> >> >> When I try to test recordings in camera setting window or
>> session
>> >> > >> >> >> recording, I get only empty webm files.
>> >> > >> >> >> Then I installed OM normally, i.e. without docker, but the
>> result was
>> >> > >> >> >> the same as in docker version.
>> >> > >> >> >> I forgot to mention that I am using OM behind nginx as a
>> reverse
>> >> > >> >> >> proxy. Everything works correctly except recordings.
>> >> > >> >> >> Does anyone noticed the same behaviour? Have I missed
>> something? Or it is a bug?
>> >> > >> >> >> Regards,
>> >> > >> >> >> Yarema
>> >> > >> >> >
>> >> > >> >> >
>> >> > >> >> >
>> >> > >> >> > --
>> >> > >> >> > WBR
>> >> > >> >> > Maxim aka solomax
>> >> > >> >
>> >> > >> >
>> >> > >> >
>> >> > >> > --
>> >> > >> > WBR
>> >> > >> > Maxim aka solomax
>> >> > >
>> >> > >
>> >> > >
>> >> > > --
>> >> > > WBR
>> >> > > Maxim aka solomax
>> >
>> >
>> >
>> > --
>> > WBR
>> > Maxim aka solomax
>>
>
>
> --
> WBR
> Maxim aka solomax
>

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

I'm not using KMS in a standalone docker. I'm using docker with
OM+mysql+kurento:

docker build -t om-server-full --build-arg BUILD_TYPE=full .

пт, 20 вер. 2019 о 14:56 Maxim Solodovnik  пише:
>
> Why do you using KMS in docker in Ubuntu?
>
> On Fri, 20 Sep 2019 at 19:54, YUP  wrote:
>>
>> Well, I reinstalled Openmeetings full version
>> (ubuntu+OM+mysql+kurento)  in a docker, and I have to say that
>> installation of Kurento Media Server
>> is broken. Kurrento have never started. Something is wrong with
>> kurento init script, or most likely with ubuntu installation.
>> You can easily check it. Steps to reproduce:
>> 1. Install OM full using instructions
>> 2. Start container
>> 3. Enter container: docker exec -it  bash
>> 4. Check whether kurento runs:
>> ps xuaw | grep kurento
>> or try to start service:
>> service kurento-media-server start
>> This gives error:
>>  * Start Kurento Media Server
>>  * Configure Kernel resource limits for Kurento Media Server
>> /etc/init.d/kurento-media-server: 118:
>> /etc/init.d/kurento-media-server: Pipe call failed
>>
>>
>>
>>
>>
>>
>>
>>
>> 3.
>>
>> пт, 20 вер. 2019 о 12:07 YUP  пише:
>> >
>> > You gave me a hint. Ill check it.
>> >
>> > пт, 20 вер. 2019 о 09:17 Maxim Solodovnik  пише:
>> > >
>> > > WebM files are being written by KMS
>> > > Maybe you get some info from KMS logs on your system?
>> > >
>> > > (I'm using Ubuntu on daily basis, never saw such behavior)
>> > >
>> > > On Fri, 20 Sep 2019 at 14:13, YUP  wrote:
>> > >>
>> > >> nobody:nogroup
>> > >>
>> > >> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik  пише:
>> > >> >
>> > >> > Can you check files have correct owner?
>> > >> >
>> > >> > On Fri, 20 Sep 2019 at 14:09, YUP  wrote:
>> > >> >>
>> > >> >> That's right, they are placed in correct places, but have 0 bytes.
>> > >> >>
>> > >> >> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik  
>> > >> >> пише:
>> > >> >> >
>> > >> >> > Hello Yarema,
>> > >> >> >
>> > >> >> > so `webm` files are being created in correct place? but they are 
>> > >> >> > empty?
>> > >> >> >
>> > >> >> > On Fri, 20 Sep 2019 at 04:19, YUP  wrote:
>> > >> >> >>
>> > >> >> >> Hi,
>> > >> >> >> I installed full OM by means of docker on archlinux host machine,
>> > >> >> >> using provided instruction. I even managed to work
>> > >> >> >> kurento-media-server, which doesn't work out of a box in OM 
>> > >> >> >> container.
>> > >> >> >> When I try to test recordings in camera setting window or session
>> > >> >> >> recording, I get only empty webm files.
>> > >> >> >> Then I installed OM normally, i.e. without docker, but the result 
>> > >> >> >> was
>> > >> >> >> the same as in docker version.
>> > >> >> >> I forgot to mention that I am using OM behind nginx as a reverse
>> > >> >> >> proxy. Everything works correctly except recordings.
>> > >> >> >> Does anyone noticed the same behaviour? Have I missed something? 
>> > >> >> >> Or it is a bug?
>> > >> >> >> Regards,
>> > >> >> >> Yarema
>> > >> >> >
>> > >> >> >
>> > >> >> >
>> > >> >> > --
>> > >> >> > WBR
>> > >> >> > Maxim aka solomax
>> > >> >
>> > >> >
>> > >> >
>> > >> > --
>> > >> > WBR
>> > >> > Maxim aka solomax
>> > >
>> > >
>> > >
>> > > --
>> > > WBR
>> > > Maxim aka solomax
>
>
>
> --
> WBR
> Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

Well, I reinstalled Openmeetings full version
(ubuntu+OM+mysql+kurento)  in a docker, and I have to say that
installation of Kurento Media Server
is broken. Kurrento have never started. Something is wrong with
kurento init script, or most likely with ubuntu installation.
You can easily check it. Steps to reproduce:
1. Install OM full using instructions
2. Start container
3. Enter container: docker exec -it  bash
4. Check whether kurento runs:
ps xuaw | grep kurento
or try to start service:
service kurento-media-server start
This gives error:
 * Start Kurento Media Server
 * Configure Kernel resource limits for Kurento Media Server
/etc/init.d/kurento-media-server: 118:
/etc/init.d/kurento-media-server: Pipe call failed








3.

пт, 20 вер. 2019 о 12:07 YUP  пише:
>
> You gave me a hint. Ill check it.
>
> пт, 20 вер. 2019 о 09:17 Maxim Solodovnik  пише:
> >
> > WebM files are being written by KMS
> > Maybe you get some info from KMS logs on your system?
> >
> > (I'm using Ubuntu on daily basis, never saw such behavior)
> >
> > On Fri, 20 Sep 2019 at 14:13, YUP  wrote:
> >>
> >> nobody:nogroup
> >>
> >> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik  пише:
> >> >
> >> > Can you check files have correct owner?
> >> >
> >> > On Fri, 20 Sep 2019 at 14:09, YUP  wrote:
> >> >>
> >> >> That's right, they are placed in correct places, but have 0 bytes.
> >> >>
> >> >> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik  пише:
> >> >> >
> >> >> > Hello Yarema,
> >> >> >
> >> >> > so `webm` files are being created in correct place? but they are 
> >> >> > empty?
> >> >> >
> >> >> > On Fri, 20 Sep 2019 at 04:19, YUP  wrote:
> >> >> >>
> >> >> >> Hi,
> >> >> >> I installed full OM by means of docker on archlinux host machine,
> >> >> >> using provided instruction. I even managed to work
> >> >> >> kurento-media-server, which doesn't work out of a box in OM 
> >> >> >> container.
> >> >> >> When I try to test recordings in camera setting window or session
> >> >> >> recording, I get only empty webm files.
> >> >> >> Then I installed OM normally, i.e. without docker, but the result was
> >> >> >> the same as in docker version.
> >> >> >> I forgot to mention that I am using OM behind nginx as a reverse
> >> >> >> proxy. Everything works correctly except recordings.
> >> >> >> Does anyone noticed the same behaviour? Have I missed something? Or 
> >> >> >> it is a bug?
> >> >> >> Regards,
> >> >> >> Yarema
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > WBR
> >> >> > Maxim aka solomax
> >> >
> >> >
> >> >
> >> > --
> >> > WBR
> >> > Maxim aka solomax
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

You gave me a hint. Ill check it.

пт, 20 вер. 2019 о 09:17 Maxim Solodovnik  пише:
>
> WebM files are being written by KMS
> Maybe you get some info from KMS logs on your system?
>
> (I'm using Ubuntu on daily basis, never saw such behavior)
>
> On Fri, 20 Sep 2019 at 14:13, YUP  wrote:
>>
>> nobody:nogroup
>>
>> пт, 20 вер. 2019 о 09:11 Maxim Solodovnik  пише:
>> >
>> > Can you check files have correct owner?
>> >
>> > On Fri, 20 Sep 2019 at 14:09, YUP  wrote:
>> >>
>> >> That's right, they are placed in correct places, but have 0 bytes.
>> >>
>> >> пт, 20 вер. 2019 о 09:06 Maxim Solodovnik  пише:
>> >> >
>> >> > Hello Yarema,
>> >> >
>> >> > so `webm` files are being created in correct place? but they are empty?
>> >> >
>> >> > On Fri, 20 Sep 2019 at 04:19, YUP  wrote:
>> >> >>
>> >> >> Hi,
>> >> >> I installed full OM by means of docker on archlinux host machine,
>> >> >> using provided instruction. I even managed to work
>> >> >> kurento-media-server, which doesn't work out of a box in OM container.
>> >> >> When I try to test recordings in camera setting window or session
>> >> >> recording, I get only empty webm files.
>> >> >> Then I installed OM normally, i.e. without docker, but the result was
>> >> >> the same as in docker version.
>> >> >> I forgot to mention that I am using OM behind nginx as a reverse
>> >> >> proxy. Everything works correctly except recordings.
>> >> >> Does anyone noticed the same behaviour? Have I missed something? Or it 
>> >> >> is a bug?
>> >> >> Regards,
>> >> >> Yarema
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > WBR
>> >> > Maxim aka solomax
>> >
>> >
>> >
>> > --
>> > WBR
>> > Maxim aka solomax
>
>
>
> --
> WBR
> Maxim aka solomax

Re: Empty Recording files in OM 5.0.0-M2

[YUP]

That's right, they are placed in correct places, but have 0 bytes.

пт, 20 вер. 2019 о 09:06 Maxim Solodovnik  пише:
>
> Hello Yarema,
>
> so `webm` files are being created in correct place? but they are empty?
>
> On Fri, 20 Sep 2019 at 04:19, YUP  wrote:
>>
>> Hi,
>> I installed full OM by means of docker on archlinux host machine,
>> using provided instruction. I even managed to work
>> kurento-media-server, which doesn't work out of a box in OM container.
>> When I try to test recordings in camera setting window or session
>> recording, I get only empty webm files.
>> Then I installed OM normally, i.e. without docker, but the result was
>> the same as in docker version.
>> I forgot to mention that I am using OM behind nginx as a reverse
>> proxy. Everything works correctly except recordings.
>> Does anyone noticed the same behaviour? Have I missed something? Or it is a 
>> bug?
>> Regards,
>> Yarema
>
>
>
> --
> WBR
> Maxim aka solomax

Empty Recording files in OM 5.0.0-M2

[YUP]

Hi,
I installed full OM by means of docker on archlinux host machine,
using provided instruction. I even managed to work
kurento-media-server, which doesn't work out of a box in OM container.
When I try to test recordings in camera setting window or session
recording, I get only empty webm files.
Then I installed OM normally, i.e. without docker, but the result was
the same as in docker version.
I forgot to mention that I am using OM behind nginx as a reverse
proxy. Everything works correctly except recordings.
Does anyone noticed the same behaviour? Have I missed something? Or it is a bug?
Regards,
Yarema