For the last ten years I have been a great fan and supporter of free and open source software, so this email is an admission of defeat for me.
Is there a script or set of instructions that will completely remove jitsi-meet and all associated files, so that it can be reinstalled without errors? I have been trying to create an acceptable working installation for about a month without success. It seems to be impossible to restore the system to it’s previous state so that a new installation can be completed.
I have a clean Ubuntu 18.04 LTS server that has only Midnight Commander and netdata installed.
On the first installation it all seemed to work. I then ran into an nginx problem because I made an error typing in the host name. After trying unsuccessfully to fix it, I decided to uninstall and reinstall. As root I did the following:
I stopped all jitsi. jocofo and prosody processes using systemctl and checking with htop.
I ran the apt-get purge … line from the quick install guide in github.
Reinstalling did not work, so I repeated from 1) to 2) and then continued:
Uninstalled nginx, LetsEncrypt and Certbot.
Found and deleted every jitsi, Jocofo, Prosody, nginx, LetsEncrypt and Certbot folder and file that I could find.
On reinstalling the following errors occurred:
… Setting up jitsi-videobridge2 (2.1-183-gdbddd169-1) …
useradd: warning: the home directory already exists.
Not copying any file from skel directory into it.
Applying /etc/sysctl.conf …
Created symlink /etc/systemd/system/multi-user.target.wants/jitsi-videobridge2.service → /lib/systemd/system/jitsi-videobridge2.service.
Selecting previously unselected package jitsi-meet.
(Reading database … 80102 files and directories currently installed.)
Preparing to unpack …/jitsi-meet_2.0.4468-1_all.deb …
Unpacking jitsi-meet (2.0.4468-1) …
Setting up jitsi-meet-web-config (1.0.4025-1) …
Can’t load /root/.rnd into RNG
140630885654976:error:2406F079:random number generator:RAND_load_file:Cannot open file:…/crypto/rand/randfile.c:88:Filename=/root/.rnd
Generating a RSA private key
writing new private key to ‘/etc/jitsi/meet/jitsi.meetu3adacorum.org.key’
cp: cannot create regular file ‘/etc/nginx/sites-available/jitsi.meetu3adacorum.org.conf’: No such file or directory
dpkg: error processing package jitsi-meet-web-config (–configure):
installed jitsi-meet-web-config package post-installation script subprocess returned error exit status 1
E: Sub-process /usr/bin/dpkg returned an error code (1)
I would really appreciate some guidance other than run systemctl status prosody.service and journalctl -xe.
I hate to say it but unless jitsi-meet can be installed and removed and installed again with standard scripts it must have and will contnue to attract and lose users without knowing it. It hurts to say it but Zoom looks increasingly attractive.
Apart from certbot (not installed with apt in the default Jitsi Debian package) deleting files and directories manually when the package uninstallation has not specifically warned about them is always the symptom of a mistake, probably of the user, but sometimes of the packager.
That’s probably the root cause of your problem.
The best way of uninstall a system like Jitsi (a very fast moving system where the packaging is done by people having other priorities, and is probably not tested as thoroughly as is usually done by Debian packagers) is to go through the installed packages in the apt logs and to carefully remove them. I have done this myself one time, and it worked. Deleting directories by hand is often a sign that you missed something.
In my notes I have this point that default install brings packages named ca-certificates-java and java-common openjdk-8-jre-headless and these are not removed automatically by only removing a few Jitsi packages while it’s necessary that ca-certificates at least is purged for the install to work again a second time.
The only bad trouble I had is that one time I had to do
Thanks. Just ran it after doing the other things. Result is below. I should be able to start again.
webadmin@jitsi:/$ sudo apt-get purge jigasi jitsi-meet jitsi-meet-web-config jitsi-meet-prosody jitsi-meet-turnserver jitsi-meet-web jicofo jitsi-videobridge jitsi-videobridge2 prosody nginx
Reading package lists… Done
Building dependency tree
Reading state information… Done
Package ‘nginx’ is not installed, so not removed
Package ‘jicofo’ is not installed, so not removed
Package ‘jigasi’ is not installed, so not removed
Package ‘jitsi-meet-prosody’ is not installed, so not removed
Package ‘jitsi-meet-turnserver’ is not installed, so not removed
Package ‘jitsi-meet-web-config’ is not installed, so not removed
Package ‘jitsi-meet-web’ is not installed, so not removed
Package ‘jitsi-meet’ is not installed, so not removed
Package ‘jitsi-videobridge2’ is not installed, so not removed
Package ‘jitsi-videobridge’ is not installed, so not removed
The following packages will be REMOVED
0 to upgrade, 0 to newly install, 1 to remove and 0 not to upgrade.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database … 78335 files and directories currently installed.)
Purging configuration files for prosody (0.10.0-1build1) …
groupdel: group ‘prosody’ does not exist
Processing triggers for systemd (237-3ubuntu10.39) …
Processing triggers for ureadahead (0.100.0-21) …
I can’t explain better than Windsurfer my whish to go further while blocked from recurring and changing issues (while new jitsi-meet releases are coming with new … little issues). But I’m a step from give up, frustrated by the amount of time vasted demonstrating my lacks without being able to demontrate the high value of this Application.
I’m working on Ubuntu 18.4 (desktop) minimal install.
Couple of weeks ago Jitsi-meet was quite OK, but after an upgrade … now I’m 100 steps back.
I’m exacly at the position posted by Windsurfer at the beginning.
Also after the suggested steps in this post.
made some check w/ “dpkg” … clean.
sudo apt-get install -y nginx
sudo apt install certbot (alread in)
… postponed the certificates install (thinking to try w/ Let’s encrypt)
sudo apt-get install jitsi-meet
re-made the procedure 3 times, adding more remove/purge …
a) not asked for the hostname
b) ERROR … exacltly the same as at the beginning of this post.
I’ve the same feeling of Windsurfer (at the beginning of this post) and mant many more dev not appearing here.
I’ve made more the the possible to see and making to see a working instance of jitsi-meet, but i’ve not neen able to have a STABLE install coming directly from the procedure illustrated in the “Quick-install” guide.
Don’t let me stay back with FaceTime, Teams, Zoom, HouseParty etc …
Pls, do you have any suggestion … to get a stable installation ?
sudo apt purge nginx nginx-common nginx-full nginx-core (got an error so repeated this way)
sudo apt remove nginx nginx-common nginx-full nginx-core
sudo apt purge nginx nginx-common nginx-full nginx-core
sudo rm -r /var/www (there was some stuff in there)
sudo dpkg -l nginx*
sudo apt-get install -y nginx
sudo systemctl status nginx.service (is it on ? NO)
sudo systemctl restart nginx.service (restart)
(I had to add these dir to avoid error during jitsi-meet install)
sudo ls -lap /etc/nginx
sudo mkdir /etc/nginx/sites-available
sudo mkdir /etc/nginx/sites-enabled
sudo mkdir /etc/nginx/modules-enabled
ADD some stuff. without these jitsi-meet install actually could fail.
sudo nano /etc/nginx/nginx.conf
(added references to the “conf” files created during j-m install on the above mentioned folders)
Addedd at the end of the file: