Re: 2 problems with 5.0.0 M3
Hi! The installation worked perfectly, and the integration with Moodle too. I just had to remove old activities and create new ones. Thank you so much for this. I just realized that even if I change the language settings, some words are still in English. For example: Polls. What was already in Portuguese before changing the language file, remains in the same language. My changes have not updated. On the M3 this worked. > Em 22 de abr de 2020, à(s) 20:34, Maxim Solodovnik > escreveu: > > server.xml had some security enhancements > I would apply changes instead of copying ... > > M4 requires new plugin > Will be available most probably today :) > > On Thu, 23 Apr 2020 at 01:28, Ricardo Neves wrote: >> >> Hello! >> >> I upgraded from M3 to M4. >> I had to solve SSL, put the connector to Mysql and copy the server.xml from >> the previous version, but it worked well. >> I had a problem in Moodle: After the update, I get the message "Invalid >> Hash". >> What could be happening? >> >> Thank you for your help! >> >> >> Ricardo. >> >> >>> Em 22 de abr de 2020, à(s) 08:59, Maxim Solodovnik >>> escreveu: >>> >>> M4 is on it's way to Apache mirrors >>> please try one of the URLs from here: >>> https://www.apache.org/dyn/closer.lua/openmeetings/5.0.0-M4/bin/apache-openmeetings-5.0.0-M4.tar.gz >>> >>> Upgrade process is described here: >>> https://openmeetings.apache.org/Upgrade.html >>> Please backup everything before you start >>> >>> On Wed, 22 Apr 2020 at 18:18, Chamberland, Martin >>> wrote: >>>> >>>> Sorry about that, our research did not point us to M4 (and the fix). >>>> >>>> Where can we download M4 ?, and any step by step tutorial how to install >>>> M4 ? >>>> >>>> Thank's for you help Maxim ! >>>> >>>> -Message d'origine- >>>> De : Maxim Solodovnik [mailto:solomax...@gmail.com] >>>> Envoyé : 21 avril 2020 21:51 >>>> À : Openmeetings user-list >>>> Objet : Re: 2 problems with 5.0.0 M3 >>>> >>>> Hello, >>>> >>>> Demo server works as expected: https://om.alteametasoft.com:8443/next/ >>>> You can't reproduce both issues on demo >>>> Since it has M4-SNAPSHOT installed, and both are already fixed in M4 :))) >>>> >>>> On Wed, 22 Apr 2020 at 02:58, ratatouille >>>> wrote: >>>>> >>>>> "Chamberland, Martin" schrieb am 21.04.20 >>>>> um 19:34:14 Uhr: >>>>> >>>>>> You correctly understand the first problem. >>>>>> I hope developers will be able to reproduce it on demo server and fix it. >>>>>> For us here, we cannot use demo server 5.0.0 M3, they look down for now. >>>>>> >>>>>> For our second problem, let's try to explain better. >>>>>> Suppose you are in a room, and camera is ON, you have your windows >>>>>> (CAMERA) open. >>>>>> You can see your image and there is upper bar in that windows. On >>>>>> the right side of that bar, there is (see attached) 3 icons One refresh, >>>>>> One for Sound and the other is suppose to be for collapse or reduce the >>>>>> size of this windows. >>>>>> For now, that icon do NOTHING, I mean not collapsing that windows. >>>>>> COLLASPE / RESTORE >>>>> >>>>> Yes, thanks for explanation! I can confirm it does nothing. >>>>> >>>>> Andreas >>>> >>>> >>>> >>>> -- >>>> Best regards, >>>> Maxim >>> >>> >>> >>> -- >>> Best regards, >>> Maxim >> > > > -- > Best regards, > Maxim
Re: 2 problems with 5.0.0 M3
Hello! I upgraded from M3 to M4. I had to solve SSL, put the connector to Mysql and copy the server.xml from the previous version, but it worked well. I had a problem in Moodle: After the update, I get the message "Invalid Hash". What could be happening? Thank you for your help! Ricardo. > Em 22 de abr de 2020, à(s) 08:59, Maxim Solodovnik > escreveu: > > M4 is on it's way to Apache mirrors > please try one of the URLs from here: > https://www.apache.org/dyn/closer.lua/openmeetings/5.0.0-M4/bin/apache-openmeetings-5.0.0-M4.tar.gz > > Upgrade process is described here: > https://openmeetings.apache.org/Upgrade.html > Please backup everything before you start > > On Wed, 22 Apr 2020 at 18:18, Chamberland, Martin > wrote: >> >> Sorry about that, our research did not point us to M4 (and the fix). >> >> Where can we download M4 ?, and any step by step tutorial how to install M4 >> ? >> >> Thank's for you help Maxim ! >> >> -Message d'origine- >> De : Maxim Solodovnik [mailto:solomax...@gmail.com] >> Envoyé : 21 avril 2020 21:51 >> À : Openmeetings user-list >> Objet : Re: 2 problems with 5.0.0 M3 >> >> Hello, >> >> Demo server works as expected: https://om.alteametasoft.com:8443/next/ >> You can't reproduce both issues on demo >> Since it has M4-SNAPSHOT installed, and both are already fixed in M4 :))) >> >> On Wed, 22 Apr 2020 at 02:58, ratatouille wrote: >>> >>> "Chamberland, Martin" schrieb am 21.04.20 >>> um 19:34:14 Uhr: >>> You correctly understand the first problem. I hope developers will be able to reproduce it on demo server and fix it. For us here, we cannot use demo server 5.0.0 M3, they look down for now. For our second problem, let's try to explain better. Suppose you are in a room, and camera is ON, you have your windows (CAMERA) open. You can see your image and there is upper bar in that windows. On the right side of that bar, there is (see attached) 3 icons One refresh, One for Sound and the other is suppose to be for collapse or reduce the size of this windows. For now, that icon do NOTHING, I mean not collapsing that windows. COLLASPE / RESTORE >>> >>> Yes, thanks for explanation! I can confirm it does nothing. >>> >>> Andreas >> >> >> >> -- >> Best regards, >> Maxim > > > > -- > Best regards, > Maxim
Re: Openmeetings 5.0.0-M3 doesn't record
The video and audio stream is sent to the room, but the audio file is not generated, and the video file is zeroed. The quickest test is to click: Check the Configuration, and try to save. The 5-second counter is not activated. My server is VPS Hostgator, and it alone includes several rules in IPTABLES. I did not find the rule that blocks the correct recording, however, it is the problem, because when disabled, it works normally. Below are all the rules, if you want to reproduce: *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :icmpchk - [0:0] :input_custom - [0:0] :ipdrop_global - [0:0] :output_custom - [0:0] :ssh - [0:0] :tcpchk - [0:0] :udpchk - [0:0] -A INPUT ! -i lo -p tcp -j tcpchk -A INPUT ! -i lo -p udp -j udpchk -A INPUT ! -i lo -p icmp -j icmpchk -A INPUT -j ipdrop_global -A INPUT -j input_custom -A INPUT -i lo -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 22022 -j ssh -A INPUT -p icmp -m icmp --icmp-type 8 -m hashlimit --hashlimit-upto 2/sec --hashlimit-burst 10 --hashlimit-mode srcip --hashlimit-name PING_IN -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 8 -m limit --limit 5/min -j LOG --log-prefix "ICMP_DROP " --log-level 3 -A INPUT -p icmp -m icmp --icmp-type 8 -j DROP -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 3/4 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 3/3 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 3/1 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 11 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 12 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 30 -j ACCEPT -A INPUT -p icmp -m state --state ESTABLISHED -j ACCEPT -A INPUT -s 173.245.48.0/20 -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -s 103.21.244.0/22 -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -s 103.22.200.0/22 -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -s 103.31.4.0/22 -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -s 141.101.64.0/18 -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -s 108.162.192.0/18 -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -s 190.93.240.0/20 -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -s 188.114.96.0/20 -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -s 197.234.240.0/22 -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -s 198.41.128.0/17 -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -s 162.158.0.0/15 -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -s 104.16.0.0/12 -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -s 172.64.0.0/13 -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -s 131.0.72.0/22 -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -s 162.241.66.218/32 -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -s 198.1.121.202/32 -p tcp -m multiport --dports 22,80 -j ACCEPT -A INPUT -s 198.1.121.202/32 -p icmp -m icmp --icmp-type 8 -j ACCEPT -A INPUT -s 184.173.226.84/32 -p tcp -m multiport --dports 22,80 -j ACCEPT -A INPUT -s 184.173.226.84/32 -p icmp -m icmp --icmp-type 8 -j ACCEPT -A INPUT -s 184.172.224.50/32 -p tcp -m multiport --dports 22,80 -j ACCEPT -A INPUT -s 184.172.224.50/32 -p icmp -m icmp --icmp-type 8 -j ACCEPT -A INPUT -p tcp -m tcp --dport 53 -j ACCEPT -A INPUT -p tcp -m tcp --dport 21 -j ACCEPT -A INPUT -p tcp -m tcp --dport 22 -j ACCEPT -A INPUT -p tcp -m tcp --dport 25 -j ACCEPT -A INPUT -p tcp -m tcp --dport 26 -j ACCEPT -A INPUT -p udp -m udp --dport 53 -j ACCEPT -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -p tcp -m tcp --dport 110 -j ACCEPT -A INPUT -p tcp -m tcp --dport 143 -j ACCEPT -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT -A INPUT -p tcp -m tcp --dport 465 -j ACCEPT -A INPUT -p tcp -m tcp --dport 587 -j ACCEPT -A INPUT -p tcp -m tcp --dport 2082 -j ACCEPT -A INPUT -p tcp -m tcp --dport 2083 -j ACCEPT -A INPUT -p tcp -m tcp --dport 2084 -j ACCEPT -A INPUT -p tcp -m tcp --dport 2086 -j ACCEPT -A INPUT -p tcp -m tcp --dport 2087 -j ACCEPT -A INPUT -p tcp -m tcp --dport 2089 -j ACCEPT -A INPUT -p tcp -m tcp --dport -j ACCEPT -A INPUT -p tcp -m tcp --dport 2095 -j ACCEPT -A INPUT -p tcp -m tcp --dport 2096 -j ACCEPT -A INPUT -p tcp -m tcp --dport 993 -j ACCEPT -A INPUT -p tcp -m tcp --dport 995 -j ACCEPT -A INPUT -s 192.168.10.11/32 -p udp -m udp --sport 53 -j ACCEPT -A INPUT -s 192.168.10.11/32 -p tcp -m tcp --sport 53 -j ACCEPT -A INPUT -p tcp -m tcp --dport 3478 -j ACCEPT -A INPUT -p udp -m udp --dport 3478 -j ACCEPT -A INPUT -p tcp -m tcp --dport 5443 -j ACCEPT -A INPUT -p udp -m udp --dport 5443 -j ACCEPT -A INPUT -p tcp -m tcp --dport -j ACCEPT -A INPUT -p udp -m udp --dport -j ACCEPT -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -m limit --limit 1/sec -j LOG --log-prefix "LOG_INPUT: " -A INPUT -p tcp -m tcp -j REJECT --reject-with tcp-reset -A INPUT -j DROP -A INPUT -p udp -m multiport --dports 49152:65535 -j ACCEPT -A INPUT -i lo -j ACCEPT -A FORWARD -p tcp -j tcpchk -A FORWARD -p udp -j udpchk -A FORWARD -p icmp -j icmpchk -A OUTPUT ! -o lo -p tcp -j tcpchk -A OUTPUT -p udp -j udpchk -A OUTPUT -p icmp -j icmpchk -A OUTPUT -j output_custom -A OUTPUT -o lo -j ACCEPT -A OUTPUT
Re: Openmeetings 5.0.0-M3 doesn't record
Hi Maxim, Thanks for answering. I performed tests on Chrome and Firefox. And recording works if the firewall is disabled. As you said that the recording is internal to the server, then it is possible that the firewall is blocking something on the localhost. I'll check, because that must be it. I perform a quick test by going to "Check the Configuration". When it does not work (firewall active), when clicking on "Start Recording" the second counter is not activated, and a webm file with zero bytes is generated. Once again, disabling the firewall, even without restarting the application, Openmeetings performs the recording normally. Thanks again. Ricardo. > Em 18 de abr de 2020, à(s) 22:11, Maxim Solodovnik > escreveu: > > Hello Ricardo, > > such behavior is really weird > Recording is made on server so the main test should be: start your camera or > screen-sharing > Check using different browser or browser tab if your sharing\camera is visible > > Is it works as expected? > > What browser are you using? > > On Sun, 19 Apr 2020 at 02:22, Ricardo Neves <mailto:nevs.rica...@gmail.com>> wrote: > Hello, I'm using Openmeetings 5.0.0-M3 with Centos 7. Everything works fine, > but it doesn't record with the firewall active (it generates zero size webm > files). I've already released all the doors and more: > iptables -A INPUT -p tcp -m tcp --dport 3478 -j ACCEPT > iptables -A INPUT -p tcp -m tcp --dport 3479 -j ACCEPT > iptables -A INPUT -p tcp -m tcp --dport 5443 -j ACCEPT > iptables -A INPUT -p tcp -m tcp --dport -j ACCEPT > iptables -A INPUT -p udp --match multiport --dports 49152: 65535 -j ACCEPT > iptables -A INPUT -p udp -m udp --dport 3478 -j ACCEPT > iptables -A INPUT -p udp -m udp --dport 3479 -j ACCEPT > iptables -A OUTPUT -p udp --match multiport --dports 49152: 65535 -j ACCEPT > > If I disable the firewall, recording occurs normally. > Is there a rule missing from my firewall? > Thanks a lot for the help. > Ricardo. > > > -- > Best regards, > Maxim
Openmeetings 5.0.0-M3 doesn't record
Hello, I'm using Openmeetings 5.0.0-M3 with Centos 7. Everything works fine, but it doesn't record with the firewall active (it generates zero size webm files). I've already released all the doors and more: iptables -A INPUT -p tcp -m tcp --dport 3478 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 3479 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 5443 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport -j ACCEPT iptables -A INPUT -p udp --match multiport --dports 49152: 65535 -j ACCEPT iptables -A INPUT -p udp -m udp --dport 3478 -j ACCEPT iptables -A INPUT -p udp -m udp --dport 3479 -j ACCEPT iptables -A OUTPUT -p udp --match multiport --dports 49152: 65535 -j ACCEPT If I disable the firewall, recording occurs normally. Is there a rule missing from my firewall? Thanks a lot for the help. Ricardo.
