Re: Media server connection is failed, will try to re-connect
Hello Thomas can you privately send me your openmeetings.log According to Audio/Video settings dialog correct TURN server is being used now And media connection is established but test recording seems to not work :( On Fri, 31 Mar 2023 at 07:40, Maxim Solodovnik wrote: > > I'll check a bit later today > > from mobile (sorry for typos ;) > > > On Fri, Mar 31, 2023, 00:19 Thomas Scholzen wrote: >> >> Hi Maxim, >> >> I installed build 235 as you suggested but can still not get any video to >> other clients. No error messages though. >> >> Any ideas? >> >> Best regards >> Thomas >> >> Am 29.03.23 um 05:59 schrieb Maxim Solodovnik: >> >> https://issues.apache.org/jira/browse/OPENMEETINGS-2763 >> >> My bad :( >> 7.0.0 don't use TURN server config set up in OM and uses freeice all >> the time :((( >> >> This is fixed, >> >> I can suggest to set up build 235+ from here: >> https://ci-builds.apache.org/job/OpenMeetings/job/openmeetings/ >> (no import/export will be required, just config changes) >> >> Or wait for release of 7.1.0 (hopefully will be released in couple of weeks) >> >> build 235 is installed at >> https://demo-openmeetings.apache.org/openmeetings/ and works as >> expected >> >> sorry for inconvenience :( >> >> On Wed, 29 Mar 2023 at 03:11, Thomas Scholzen wrote: >> >> Hi Maxim, >> >> I switched now to a direct kurento installation and get less error messages. >> However, I can not get media transmission from other users. I tried >> different versions of server.xml without success. Finally, I went back to >> the version which was working under 6.0.0 (although I am not sure if I mixed >> it up; see attachment). >> >> You can connect to my server under: https://openmeetings.buche17.de/ >> >> Username: maxim >> Password: $olomax666 >> >> I tried the backup restore again (command line) on the current system and >> this time it worked ! >> >> Thanks again for your help >> Thomas >> >> Am 28.03.23 um 17:09 schrieb Maxim Solodovnik: >> >> According HTTPD config: >> >> everything looks great >> >> Locations like `` was required by Flash version and >> can now be dropped >> >> Such config require `$OM_HOME/conf/server.xml` modification, but I'm >> sure you did it >> >> You can send me private email, and I'll try to check if your server works >> for me >> >> On Tue, 28 Mar 2023 at 22:01, Maxim Solodovnik wrote: >> >> On Tue, 28 Mar 2023 at 21:32, Thomas Scholzen wrote: >> >> Hi Maxim, >> >> the size of the backup was ~ 4 GB. When the upgrade failed, >> >> Was there anything suspicious in the logs? >> >> I reinstalled OM 7.0.0. When having problems, I also reinstalled coturn & >> docker (plus km). When all failed I asked you ;-). The (re) installation was >> done on the same server on which OM 6.0.0 was running before. >> >> can you check if https://demo-openmeetings.apache.org/openmeetings >> works for you? >> >> My coturn config looks like follows: >> >> fingerprint >> lt-cred-mech >> use-auth-secret >> static-auth-secret=*** >> realm=demo-openmeetings.apache.org >> stale-nonce=0 >> proc-user=nobody >> proc-group=nogroup >> >> >> OM config >> ## Kurento ## >> kurento.ws.url=ws://127.0.0.1:/kurento >> kurento.turn.url=PUBLIC_IP:3478 >> kurento.turn.user=demo-user >> kurento.turn.secret=*** >> kurento.turn.mode=rest >> >> >> >> Please ensure "PUBLIC_IP:3478" is available to the world (connections >> happens via UDP by default) >> >> Kind regards >> Thomas >> >> >> Am 28.03.2023 15:52, schrieb Maxim Solodovnik: >> >> >> >> from mobile (sorry for typos ;) >> >> >> On Tue, Mar 28, 2023, 20:33 Thomas Scholzen wrote: >> >> Hi Maxim, >> >> thanks for the fast response. I used the command line for migration, and it >> did not work (restoreing backup just hangs forever). >> >> >> Sounds like the error of backup create/restore tool :( >> I would like to have it 100% bulletproof >> >> What is the size of your backup? >> Do you have anything suspicious in the logs? >> >> >> But no problem there, I should clean up the installation anyway ;-). >> >> My server is not a VM but bare metall. So I have to live with the >> interference of other services. >> >> As you suggested, I will try kurento without docker and see how it goes. >> >> >> So you have re-installed om+kms+coturn at your server? (I would update om >> only ...) >> Or set up new server? >> >> >> >> Thanks for you kind help >> Thomas >> >> >> Am 28.03.2023 11:27, schrieb Maxim Solodovnik: >> >> Hello Thomas, >> >> On Tue, 28 Mar 2023 at 15:41, Thomas Scholzen wrote: >> >> >> Hi Maxim, >> >> I just migrated from OM 6.00 to 7.00. After the upgrade did not work (too >> much stuff in the backup) >> >> >> I believe you can use command line admin in such case >> https://openmeetings.apache.org/CommandLineAdmin.html >> >> I went for a fresh installation. I installed OM 7.0.0, kurento via docker >> and coturn. However, I get "Media server connection for user XXX is failed,
Re: Media server connection is failed, will try to re-connect
I'll check a bit later today from mobile (sorry for typos ;) On Fri, Mar 31, 2023, 00:19 Thomas Scholzen wrote: > Hi Maxim, > > I installed build 235 as you suggested but can still not get any video to > other clients. No error messages though. > > Any ideas? > > Best regards > Thomas > Am 29.03.23 um 05:59 schrieb Maxim Solodovnik: > > https://issues.apache.org/jira/browse/OPENMEETINGS-2763 > > My bad :( > 7.0.0 don't use TURN server config set up in OM and uses freeice all > the time :((( > > This is fixed, > > I can suggest to set up build 235+ from > here:https://ci-builds.apache.org/job/OpenMeetings/job/openmeetings/ > (no import/export will be required, just config changes) > > Or wait for release of 7.1.0 (hopefully will be released in couple of weeks) > > build 235 is installed athttps://demo-openmeetings.apache.org/openmeetings/ > and works as > expected > > sorry for inconvenience :( > > On Wed, 29 Mar 2023 at 03:11, Thomas Scholzen > wrote: > > > Hi Maxim, > > I switched now to a direct kurento installation and get less error messages. > However, I can not get media transmission from other users. I tried different > versions of server.xml without success. Finally, I went back to the version > which was working under 6.0.0 (although I am not sure if I mixed it up; see > attachment). > > You can connect to my server under: https://openmeetings.buche17.de/ > > Username: maxim > Password: $olomax666 > > I tried the backup restore again (command line) on the current system and > this time it worked ! > > Thanks again for your help > Thomas > > Am 28.03.23 um 17:09 schrieb Maxim Solodovnik: > > According HTTPD config: > > everything looks great > > Locations like `` was required by Flash version and > can now be dropped > > Such config require `$OM_HOME/conf/server.xml` modification, but I'm > sure you did it > > You can send me private email, and I'll try to check if your server works for > me > > On Tue, 28 Mar 2023 at 22:01, Maxim Solodovnik > wrote: > > On Tue, 28 Mar 2023 at 21:32, Thomas Scholzen > wrote: > > Hi Maxim, > > the size of the backup was ~ 4 GB. When the upgrade failed, > > Was there anything suspicious in the logs? > > I reinstalled OM 7.0.0. When having problems, I also reinstalled coturn & > docker (plus km). When all failed I asked you ;-). The (re) installation was > done on the same server on which OM 6.0.0 was running before. > > can you check if https://demo-openmeetings.apache.org/openmeetings > works for you? > > My coturn config looks like follows: > > fingerprint > lt-cred-mech > use-auth-secret > static-auth-secret=*** > realm=demo-openmeetings.apache.org > stale-nonce=0 > proc-user=nobody > proc-group=nogroup > > > OM config > ## Kurento ## > kurento.ws.url=ws://127.0.0.1:/kurento > kurento.turn.url=PUBLIC_IP:3478 > kurento.turn.user=demo-user > kurento.turn.secret=*** > kurento.turn.mode=rest > > > > Please ensure "PUBLIC_IP:3478" is available to the world (connections > happens via UDP by default) > > Kind regards > Thomas > > > Am 28.03.2023 15:52, schrieb Maxim Solodovnik: > > > > from mobile (sorry for typos ;) > > > On Tue, Mar 28, 2023, 20:33 Thomas Scholzen > wrote: > > Hi Maxim, > > thanks for the fast response. I used the command line for migration, and it > did not work (restoreing backup just hangs forever). > > > Sounds like the error of backup create/restore tool :( > I would like to have it 100% bulletproof > > What is the size of your backup? > Do you have anything suspicious in the logs? > > > But no problem there, I should clean up the installation anyway ;-). > > My server is not a VM but bare metall. So I have to live with the > interference of other services. > > As you suggested, I will try kurento without docker and see how it goes. > > > So you have re-installed om+kms+coturn at your server? (I would update om > only ...) > Or set up new server? > > > > Thanks for you kind help > Thomas > > > Am 28.03.2023 11:27, schrieb Maxim Solodovnik: > > Hello Thomas, > > On Tue, 28 Mar 2023 at 15:41, Thomas Scholzen > wrote: > > > Hi Maxim, > > I just migrated from OM 6.00 to 7.00. After the upgrade did not work (too > much stuff in the backup) > > > I believe you can use command line admin in such > casehttps://openmeetings.apache.org/CommandLineAdmin.html > > I went for a fresh installation. I installed OM 7.0.0, kurento via docker and > coturn. However, I get "Media server connection for user XXX is failed, will > try to re-connect" every 2 to 15 seconds, depending on the client and > location. When the internet is routed via VPN to the server that runs OM, > there are no problems. OS Ubuntu 20.04 > > > I would say you have installed too much ... > Is it fresh new VM? > Can you run OM7 at the VM/server you already have for OM6? > > I've just have checked the changes > And I would say your migration should be flawless (no real changes i
Re: Media server connection is failed, will try to re-connect
Hi Maxim, I installed build 235 as you suggested but can still not get any video to other clients. No error messages though. Any ideas? Best regards Thomas Am 29.03.23 um 05:59 schrieb Maxim Solodovnik: https://issues.apache.org/jira/browse/OPENMEETINGS-2763 My bad :( 7.0.0 don't use TURN server config set up in OM and uses freeice all the time :((( This is fixed, I can suggest to set up build 235+ from here: https://ci-builds.apache.org/job/OpenMeetings/job/openmeetings/ (no import/export will be required, just config changes) Or wait for release of 7.1.0 (hopefully will be released in couple of weeks) build 235 is installed at https://demo-openmeetings.apache.org/openmeetings/ and works as expected sorry for inconvenience :( On Wed, 29 Mar 2023 at 03:11, Thomas Scholzen wrote: Hi Maxim, I switched now to a direct kurento installation and get less error messages. However, I can not get media transmission from other users. I tried different versions of server.xml without success. Finally, I went back to the version which was working under 6.0.0 (although I am not sure if I mixed it up; see attachment). You can connect to my server under:https://openmeetings.buche17.de/ Username: maxim Password: $olomax666 I tried the backup restore again (command line) on the current system and this time it worked ! Thanks again for your help Thomas Am 28.03.23 um 17:09 schrieb Maxim Solodovnik: According HTTPD config: everything looks great Locations like `` was required by Flash version and can now be dropped Such config require `$OM_HOME/conf/server.xml` modification, but I'm sure you did it You can send me private email, and I'll try to check if your server works for me On Tue, 28 Mar 2023 at 22:01, Maxim Solodovnik wrote: On Tue, 28 Mar 2023 at 21:32, Thomas Scholzen wrote: Hi Maxim, the size of the backup was ~ 4 GB. When the upgrade failed, Was there anything suspicious in the logs? I reinstalled OM 7.0.0. When having problems, I also reinstalled coturn & docker (plus km). When all failed I asked you ;-). The (re) installation was done on the same server on which OM 6.0.0 was running before. can you check ifhttps://demo-openmeetings.apache.org/openmeetings works for you? My coturn config looks like follows: fingerprint lt-cred-mech use-auth-secret static-auth-secret=*** realm=demo-openmeetings.apache.org stale-nonce=0 proc-user=nobody proc-group=nogroup OM config ## Kurento ## kurento.ws.url=ws://127.0.0.1:/kurento kurento.turn.url=PUBLIC_IP:3478 kurento.turn.user=demo-user kurento.turn.secret=*** kurento.turn.mode=rest Please ensure "PUBLIC_IP:3478" is available to the world (connections happens via UDP by default) Kind regards Thomas Am 28.03.2023 15:52, schrieb Maxim Solodovnik: from mobile (sorry for typos ;) On Tue, Mar 28, 2023, 20:33 Thomas Scholzen wrote: Hi Maxim, thanks for the fast response. I used the command line for migration, and it did not work (restoreing backup just hangs forever). Sounds like the error of backup create/restore tool :( I would like to have it 100% bulletproof What is the size of your backup? Do you have anything suspicious in the logs? But no problem there, I should clean up the installation anyway ;-). My server is not a VM but bare metall. So I have to live with the interference of other services. As you suggested, I will try kurento without docker and see how it goes. So you have re-installed om+kms+coturn at your server? (I would update om only ...) Or set up new server? Thanks for you kind help Thomas Am 28.03.2023 11:27, schrieb Maxim Solodovnik: Hello Thomas, On Tue, 28 Mar 2023 at 15:41, Thomas Scholzen wrote: Hi Maxim, I just migrated from OM 6.00 to 7.00. After the upgrade did not work (too much stuff in the backup) I believe you can use command line admin in such case https://openmeetings.apache.org/CommandLineAdmin.html I went for a fresh installation. I installed OM 7.0.0, kurento via docker and coturn. However, I get "Media server connection for user XXX is failed, will try to re-connect" every 2 to 15 seconds, depending on the client and location. When the internet is routed via VPN to the server that runs OM, there are no problems. OS Ubuntu 20.04 I would say you have installed too much ... Is it fresh new VM? Can you run OM7 at the VM/server you already have for OM6? I've just have checked the changes And I would say your migration should be flawless (no real changes in KMS/Coturn integration) Maybe you can try to run OM7 nearby OM6? - different port OR - stop one -> start another? So I suspect an issue with the turnserver. With OM 6.0.0 this setup went fine, so there is probably some kind of misconfiguration. This can be both TURN server issues and network misconfiguration at new VM/server "$ docker logs kms" gives me: "KurentoWebRtcEndpointImpl WebRtcEndpointImpl.cpp:609:WebRtcEn
