Thanks a lot. This problem is solved too. Am Do., 15. Okt. 2020 um 14:48 Uhr schrieb Alvaro <zurca...@gmail.com>:
> > Ok, please follow the indicatios of Maxim in the other thread > > > > ................ > > El jue, 15-10-2020 a las 14:39 +0200, K. Kamhamea escribió: > > <!-- <policy domain="coder" rights="none" pattern="PS" /> --> > <!-- <policy domain="coder" rights="none" pattern="PDF" /> --> > > This is what these lines look like. > > And this is the content of the directory > root@Ubuntu-2004-focal-64-minimal /etc/ImageMagick-6 # dir > coder.xml mime.xml type-dejavu.xml > colors.xml policy.xml type-ghostscript.xml > delegates.xml quantization-table.xml type-urw-base35.xml > log.xml thresholds.xml type-windows.xml > magic.xml type-apple.xml type.xml > > Am Do., 15. Okt. 2020 um 14:30 Uhr schrieb Alvaro <zurca...@gmail.com>: > > Please, take a look in step 4 page 2 about: > > <policy domain="coder" rights="none" pattern="PS" /> > <policy domain="coder" rights="none" pattern="PDF" /> > > > ..................... > > El jue, 15-10-2020 a las 12:44 +0200, K. Kamhamea escribió: > > Yes I did both time. At least I think so. Maybe I messed up something > inadvertendly during my first installation. > Though your tutorial is perfect thank you :-) > K. > > Am Do., 15. Okt. 2020 um 12:30 Uhr schrieb Alvaro <zurca...@gmail.com>: > > > ...do you have followed the installation tuto called: > > Installation OpenMeetings 5.0.1 on Ubuntu 20.04 lts.pdf > <https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20OpenMeetings%205.0.1%20on%20Ubuntu%2020.04%20lts.pdf?version=1&modificationDate=1600875964000&api=v2> > > ...can find it at: > > > https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools > > > ................................ > ........................................... > > El jue, 15-10-2020 a las 12:24 +0200, K. Kamhamea escribió: > > Eventually I got version 5.0.1 running. Problem solved. I don't know what > caused the problem with the previous version > interfering though. I reinstalled the whole thing Ubuntu 20.04 and OM > 5.0.1 and now it works. As can be seen on the screenshot, the version is > true 5.0.1. There are some problems with file upload though, but I'd better > start a new thread for that. > > [image: grafik.png] > > > Am Mi., 14. Okt. 2020 um 04:09 Uhr schrieb Maxim Solodovnik < > solomax...@gmail.com>: > > well > > according to your screen-shot > > the login screen is from REAL 5.0.1, so the version seems to be correct > > > On Wed, 14 Oct 2020 at 08:40, K. Kamhamea <kamha...@googlemail.com> wrote: > > 1. I can't. I reseted the server and I'm going to install some older M4 > version that I still have a copy from. > 2. I entered the PW you sent me. That was " Q!w2e3r4t5 " > > > you can > 1) stop OM > 2) delete *.db file(s) in OM_HOME > 3) run command line/UI installer one more time > > > > My personal opinion/conclusion is that the version currently available at " > https://downloads.apache.org/openmeetings/5.0.1/bin/"; is compromised. > Sorry, I have no other explanation. > > > personal opinion is something very hard to argue with :)) > > > > Best K. > > Am Mi., 14. Okt. 2020 um 03:02 Uhr schrieb Maxim Solodovnik < > solomax...@gmail.com>: > > please enter `ui_admin` as login > and what you have entered as password ;))) > > On Wed, 14 Oct 2020 at 00:28, K. Kamhamea <kamha...@googlemail.com> wrote: > > OK. I see this login page as before. > > [image: grafik.png] > But I cannot login as usual. > > > Am Di., 13. Okt. 2020 um 19:22 Uhr schrieb Maxim Solodovnik < > solomax...@gmail.com>: > > the password prompt is buried in this logs > just enter something like Q!w2e3r4t5 and hit Enter :))) > > On Wed, 14 Oct 2020 at 00:20, K. Kamhamea <kamha...@googlemail.com> wrote: > > It doesn't stop at step 5 creating such a strange output > > DEBUG 10-13 19:14:50.827 o.a.o.u.c.CryptProvider:39 [Bean#0_Worker-9] - > get:: configKeyCryptClassName: null > DEBUG 10-13 19:15:05.827 o.a.o.u.c.CryptProvider:39 [ean#0_Worker-10] - > get:: configKeyCryptClassName: null > DEBUG 10-13 19:15:20.829 o.a.o.u.c.CryptProvider:39 [Bean#0_Worker-7] - > get:: configKeyCryptClassName: null > DEBUG 10-13 19:15:35.826 o.a.o.u.c.CryptProvider:39 [Bean#0_Worker-1] - > get:: configKeyCryptClassName: null > DEBUG 10-13 19:15:50.828 o.a.o.u.c.CryptProvider:39 [Bean#0_Worker-8] - > get:: configKeyCryptClassName: null > DEBUG 10-13 19:16:05.827 o.a.o.u.c.CryptProvider:39 [Bean#0_Worker-4] - > get:: configKeyCryptClassName: null > WARN 10-13 19:16:15.820 o.a.o.d.d.b.ConfigurationDao:139 > [Bean#0_Worker-3] - Could not find key in configurations: > number.minutes.reminder.send > DEBUG 10-13 19:16:20.826 o.a.o.u.c.CryptProvider:39 [Bean#0_Worker-5] - > get:: configKeyCryptClassName: null > DEBUG 10-13 19:16:35.827 o.a.o.u.c.CryptProvider:39 [ean#0_Worker-10] - > get:: configKeyCryptClassName: null > DEBUG 10-13 19:16:50.827 o.a.o.u.c.CryptProvider:39 [Bean#0_Worker-7] - > get:: configKeyCryptClassName: null > DEBUG 10-13 19:17:05.826 o.a.o.u.c.CryptProvider:39 [Bean#0_Worker-2] - > get:: configKeyCryptClassName: null > DEBUG 10-13 19:17:20.827 o.a.o.u.c.CryptProvider:39 [Bean#0_Worker-6] - > get:: configKeyCryptClassName: null > DEBUG 10-13 19:17:35.827 o.a.o.u.c.CryptProvider:39 [Bean#0_Worker-8] - > get:: configKeyCryptClassName: null > DEBUG 10-13 19:17:50.826 o.a.o.u.c.CryptProvider:39 [Bean#0_Worker-4] - > get:: configKeyCryptClassName: null > WARN 10-13 19:17:55.820 o.a.o.d.d.b.ConfigurationDao:139 > [Bean#0_Worker-3] - Could not find key in configurations: > number.minutes.reminder.send > DEBUG 10-13 19:18:05.827 o.a.o.u.c.CryptProvider:39 [Bean#0_Worker-5] - > get:: configKeyCryptClassName: null > > It never asked for a password though. > > Am Di., 13. Okt. 2020 um 18:44 Uhr schrieb Maxim Solodovnik < > solomax...@gmail.com>: > > OK > > try to > > 1) enter the machine > 2) stop everything that works on it: `sudo killall java` > 3) in NEW EMPTY folder `tar -xzf apache-openmeetings*` > 4) cd apache-openmeetings* > 5) `./admin.sh -i -v -user ui_admin -email someem...@gmail.com -tz > "Asia/Tehran" -group "yourgroup"` enter password > 6) `./bin/catalina.sh run` > 7) check https://your-ip:5443/openmeetings > (no other steps please) > > what is the result? > > On Tue, 13 Oct 2020 at 23:40, K. Kamhamea <kamha...@googlemail.com> wrote: > > gpg --verify apache-openmeetings-5.0.1.tar.gz.asc > apache-openmeetings-5.0.1.tar.gz > gpg: Signature made Sat 19 Sep 2020 07:18:08 AM CEST > gpg: using RSA key 15EB59354EBF43E3A6314BEBE8302FC78456901E > gpg: Good signature from "Maxim Solodovnik <solo...@apache.org>" [unknown] > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the > owner. > Primary key fingerprint: 15EB 5935 4EBF 43E3 A631 4BEB E830 2FC7 8456 901E > > Any Ideas? > > Am Di., 13. Okt. 2020 um 18:03 Uhr schrieb Thomas Scholzen < > tschol...@buche17.de>: > > Look at "about" on the login page. > > > > Am 13.10.2020 18:00, schrieb K. Kamhamea: > > > you can check the signature > I have no idea how I can do that. Where is the signature stored? > > > any chance your requests to new server are routed to some older one? > No, as I can follow the log (tail -f ./logfile) and and I see exactly my > requests there. > > Am Di., 13. Okt. 2020 um 17:54 Uhr schrieb Maxim Solodovnik < > solomax...@gmail.com>: > > you can check the signature > any chance your requests to new server are routed to some older one? > Or something cashed in the browser (I doubt it is possible ...) > > On Tue, 13 Oct 2020 at 22:51, K. Kamhamea <kamha...@googlemail.com> wrote: > > That's interesting. > I downloaded the file from > > sudo wget > https://downloads.apache.org/openmeetings/5.0.1/bin/apache-openmeetings-5.0.1.tar.gz > > as described in Alvaro's tutorial. And the file downloaded that still > resides in the folder says > > /opt # dir > apache-openmeetings-5.0.1.tar.gz > > Is exactly that. I also can rule out the possibility that some older > version resided on that server because it is a fresh new server. > > Did someone hack into that file? > > Best K > > Am Di., 13. Okt. 2020 um 17:35 Uhr schrieb Maxim Solodovnik < > solomax...@gmail.com>: > > Hello K. > > well, your screen-shots are not from 5.0.1 :( > please check the latest UI here https://om.alteametasoft.com/openmeetings/ > (it has the latest release installed) > I can't reproduce both of your issues :( > > have you customized your OM? > Any details on your installation? > > On Tue, 13 Oct 2020 at 22:29, K. Kamhamea <kamha...@googlemail.com> wrote: > > Second, when I press this button The USER and FILES tabs disappear for > ever. > > [image: grafik.png] > In M4 there was a button with arrows pointing in the opposite direction > that restored these tabs. This button has miraculously disappeared. > > Am Di., 13. Okt. 2020 um 17:25 Uhr schrieb K. Kamhamea < > kamha...@googlemail.com>: > > Thank you for this quick response. Sorry for the first problem. It is a > typo not "errors" but "arrows". I hope the picture is instructive and makes > it clear. > > [image: grafik.png] > > > Am Di., 13. Okt. 2020 um 17:18 Uhr schrieb Maxim Solodovnik < > solomax...@gmail.com>: > > Hello K > > On Tue, 13 Oct 2020 at 22:06, K. Kamhamea <kamha...@googlemail.com> wrote: > > I just installed the new version on a test server following Alvaro's > instruction (without Coturn and Letsencrypt) on Ubuntu 20.04. I had the > version M4 running before with much less issues. > > 1. First thing that annoyed me was the fact that I cannot restore the > USERS and FILES tab once removed the to the right. > > > this make no sense, please provide steps to reproduce > > > 2. The FILES tab shows folders with moving errors only. I suppose this > signals some failure. Upload is impossible too. Though I can see the file > in the folder, an exclamation mark signals some error, and I cannot drag it > on to the whiteboard. > > > same here > what is "moving errors? since upload is impossible what in the > logs/browser console? > I'm afraid no one can help you with this level of details :( > > > > I suppose the reason is some problem with permissions. I set the whole OM > folder to > chown -R nobody:nogroup ./OM-Folder > But nothing changed. > Best K. > > > > -- > Best regards, > Maxim > > > > -- > Best regards, > Maxim > > > > -- > Best regards, > Maxim > > > > -- > Best regards, > Maxim > > > >
