As I wrote in other thread you can run chrome/chromium with following flags for testing
chromium-browser --user-data-dir=/tmp/delme0 --disable-infobars --no-default-browser-check --use-fake-device-for-media-stream --use-fake-ui-for-media-stream --use-fake-mjpeg-decode-accelerator --use-file-for-fake-video-capture=bridge_far_qcif.y4m ' https://om.alteametasoft.com:8443/next/hash?invitation=fca76e9a-f648-47e7-b00e-a9fdc274f8cf&language=1 ' The full list of flags is available here https://peter.sh/experiments/chromium-command-line-switches/ On Mon, 2 Nov 2020 at 06:30, [email protected] <[email protected]> wrote: > It looks like some new certificate issue with Chrome and self-signed > certificates > > Cheers > Seb > > Sebastian Wagner > Director Arrakeen Solutions > http://arrakeen-solutions.co.nz/ > < > https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url > > > < > https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url > > > > > On Sun, 1 Nov 2020 at 14:57, Maxim Solodovnik <[email protected]> > wrote: > > > Hello Sebastian, > > > > no changes at all > > locally I have KMS in Docker and OM > > (I'm using Tomcat) > > everything works as expected > > > > my docker command look like this > > docker run -v > > /home/solomax/work/openmeetings/data:/home/solomax/work/openmeetings/data > > -p 8888:8888 kurento/kurento-media-server-exp:bionic-gstreamer > > > > you can try to use > > docker run -v > > /home/solomax/work/openmeetings/data:/home/solomax/work/openmeetings/data > > --network host kurento/kurento-media-server-exp:bionic-gstreamer > > > > to ensure this is not port issue > > > > > > On Sun, 1 Nov 2020 at 07:00, [email protected] < > [email protected]> > > wrote: > > > > > With the change to move turn server config to openmeetings.properties > > file, > > > does it affect how you run OpenMeetings locally with Kurento ? > > > > > > I'm running it using embedded Jetty: mvn install -P > > allModules,quick,mysql > > > jetty:run-exploded -Dwicket.configuration=DEVELOPMENT > > > > > > and then Kurento in another shell with: docker run -p 8888:8888 > > > kurento/kurento-media-server > > > > > > In the OpenMeetings log file I got: > > > INFO 11-01 12:54:33.813 o.a.o.c.r.KurentoHandler:181 > [ool-24-thread-1] - > > > !!! Kurento connected > > > > > > But opening a browser session on https://$MY_IP:5443/openmeetings, > login > > > and navigating to a room, starting audio/video > > > => Firefox: Media server connection for user firstname lastname is > > failed, > > > will try to re-connect > > > => Chrome: Nothing, no blue Media Server success message and also no > > error > > > message > > > > > > There is no exception or error in any of the logs, nor JS error in the > > > browser. > > > Kurento log: https://pastebin.ubuntu.com/p/RZjtfxPf5h/ > > > OpenMeetings log: https://pastebin.ubuntu.com/p/Gp8cZ7Xc7n/ > > > > > > Was there maybe something in the openmeetings.properties file that > > requires > > > changing to point to a local running Kurento instance ? > > > > > > Thanks > > > Seb > > > > > > Sebastian Wagner > > > Director Arrakeen Solutions > > > http://arrakeen-solutions.co.nz/ > > > < > > > > > > https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url > > > > > > > < > > > > > > https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url > > > > > > > > > > > > > -- > > Best regards, > > Maxim > > > -- Best regards, Maxim
