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
hap
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;
>
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
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
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-f
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
`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:
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
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 nonsens
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 r
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+mys
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
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:
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-
`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
> 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
Double-checking it right now
Will provide you with the complete list of commands I run
BTW just found this thread:
https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ
Might be useful for nginx users
On Sat, 21 Sep 2019 at 14:23, YUP wrote:
> Yes, it is latest master with om 5.0.0-M
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_TYP
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
>
>
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] -
Configurat
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
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 Fr
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-serve
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
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 w
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
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
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. St
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:
>>
>> nobo
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 co
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
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 ar
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
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 wor
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.
T
35 matches
Mail list logo
