Installation in Ubuntu 18.04

dpkg: error processing package jitsi-meet (–configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates it’s a follow-up error from a previous failure.
Processing triggers for systemd (237-3ubuntu10.38) …
Processing triggers for man-db (2.8.3-2ubuntu0.1) …
Processing triggers for ufw (0.36-0ubuntu0.18.04.1) …
Processing triggers for ureadahead (0.100.0-21) …
ureadahead will be reprofiled on next reboot
Processing triggers for libc-bin (2.27-3ubuntu1) …
Errors were encountered while processing:
jitsi-meet-web-config
jitsi-meet
E: Sub-process /usr/bin/dpkg returned an error code (1)

Have you already run:

apt-add-repository universe

?

If not, run then, then run:

sudo apt-get update
sudo apt-get -f install

Hello Jitsi Community,

I’m sitting in the same boat. I’ve tried several times to get jtisi-meet on a fresh Ubuntu 18.0.4 server to work, but sadly it failed :frowning:
I’ve followed to steps described here and installed nginx first:

But everytime it failes with the following package: jitsi-meet-turnserver

Blockquote
jitsi-meet (2.0.4384-1) wird eingerichtet …
jitsi-meet-turnserver (1.0.3969-1) wird eingerichtet …
dpkg: Fehler beim Bearbeiten des Paketes jitsi-meet-turnserver (–configure):
installed jitsi-meet-turnserver package post-installation script subprocess returned error exit status 9
Trigger für systemd (237-3ubuntu10.39) werden verarbeitet …
Trigger für man-db (2.8.3-2ubuntu0.1) werden verarbeitet …
Trigger für ca-certificates (20180409) werden verarbeitet …
Updating certificates in /etc/ssl/certs…
0 added, 0 removed; done.

If I run:
apt-add-repository universe
and then:
sudo apt-get update
sudo apt-get -f install

It still failes:

Blockquote
jitsi-meet-turnserver (1.0.3969-1) wird eingerichtet …
dpkg: Fehler beim Bearbeiten des Paketes jitsi-meet-turnserver (–configure):
installed jitsi-meet-turnserver package post-installation script subprocess returned error exit status 9
Fehler traten auf beim Bearbeiten von:
jitsi-meet-turnserver
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any advise what I can do?
Thanks in advance and kind regards,
Daniel

I’d try purging jitsi-meet, then trying to install again.

If I purge the installation:
apt-get purge jigasi jitsi-meet jitsi-meet-web-config jitsi-meet-prosody jitsi-meet-turnserver jitsi-meet-web jicofo jitsi-videobridge2

And do a reinstall:

apt install -y jitsi-meet

I run into the same error. :roll_eyes:

If I try to do the installation with:
apt install --no-install-recommends jitsi-meet .

I get no error, but Jitsi won’t work. If I browse to the ip Adress I only see a default nginx webpage, but not more…
Regarding this thread others seems to struggle as well:

I’m not sure I can definitively help you, but I had the same exact situation and banged my head for several hours. I started up a standard AWS Ubuntu 18.4 instance and follow the (jitsi-meet/quick-install.md at master · jitsi/jitsi-meet · GitHub) tutorial steps. No Nginx or Java installed by default. Everything seemed to install correctly, but it the Meet UI would never be hosted through Nginx on 80 or 443. However, when I ran with this option:

443 started working and everything worked great. I see that you tried this, but did you try and access it over HTTPS?

try these steps:
1 apt-get remove --purge jitsi-meet jitsi-meet-prosody jitsi-meet-web-config jitsi-meet-web jicofo jitsi-videobridge
2 sudo apt-get update
3 sudo apt-get install -y jitsi-meet

@Free_Runner please change your server output language if you want to be helped, otherwise it’s really hard to identify what’s wrong

This happen when you didn’t uninstalled turnserver, as wrote in the guide sometimes you need to launch the purge command 2 times to make it effective on turnserver

@Lee in the guide it’s not said, but it’s a lot recommended to install apache2 or nginx, latest developments higly suggest to use nginx
The best thing you should do is: launch 2 times the purge command, install nginx, install again jitsi-meet, if something doesn’t work (you can check by doina meeting with a room with youself), check the errors log, if you see a java exception it’s turnserver that collide with nginx 443 port (in that case purge just jitsi-turnserver)

I did apt-get remove --purge jitsi-meet jitsi-meet-prosody jitsi-meet-web-config jitsi-meet-web jicofo jitsi-videobridge, followed by sudo apt-get update, followed by apt install --no-install-recommends jitsi-meet. This worked Ok except for:
Setting up jicofo (1.0-541-1) …
useradd: warning: the home directory already exists.
Not copying any file from skel directory into it.
Also, jitsi-turnserver was not installed. I noted that nginx is installed but not apache2. Perhaps that’s good as later RubensRainelli stated:
“The best thing you should do is: launch 2 times the purge command, install nginx, install again jitsi-meet, if something doesn’t work (you can check by doina meeting with a room with youself), check the errors log, if you see a java exception it’s turnserver that collide with nginx 443 port (in that case purge just jitsi-turnserver)”

I thought that this would give a standalone app in Ubuntu 18.04 but it didn’t. Am I supposed to run Jitsi Meet from within my Browser?

That’s correct. You’ve installed the server components. You then access your server via a browser.

(If you don’t need to run your own server, you can just use the hosted jitsi instance, meet.jit.si, from your browser, without needing to install anything.)

I’m slightly in disbelief that Jitsi devs can use a so user-friendly system as debian packaging and not include in a FAQ the appropriate incantation to debug package install problems.

Here it is in all its glory:

sudo debconf --frontend=readline bash -x /var/lib/dpkg/info/jitsi-meet-turnserver.postinst configure

Hope it helps - because a postinst script like the jitsi-meet-turnserver one can be somewhat complicated and can fail for several different reasons.

Thanks, but still not working :frowning:
It returns the following:

Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages were automatically installed and are no longer required:
apt-clone archdetect-deb btrfs-tools cryptsetup-bin dmraid
gir1.2-geocodeglib-1.0 gir1.2-timezonemap-1.0 gir1.2-xkl-1.0
icedtea-netx-common kpartx kpartx-boot libdbusmenu-gtk4 libdebian-installer4
libdmraid1.0.0.rc16 libfwup1 libido3-0.1-0 libllvm6.0 libllvm7 libllvm8
libtimezonemap-data libtimezonemap1 linux-oem-headers-4.15.0-1043
linux-oem-headers-4.15.0-1045 linux-oem-headers-4.15.0-1050
linux-oem-headers-4.15.0-1056 linux-oem-headers-4.15.0-1057
linux-oem-headers-4.15.0-1059 linux-oem-headers-4.15.0-1064
linux-oem-headers-4.15.0-1065 linux-oem-headers-4.15.0-1066 python3-icu
python3-pam rdate ubuntu-web-launchers
Use ‘sudo apt autoremove’ to remove them.
0 to upgrade, 0 to newly install, 0 to remove and 8 not to upgrade.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up jitsi-meet-web-config (1.0.3969-1) …
req: Use -help for summary.
dpkg: error processing package jitsi-meet-web-config (–configure):
installed jitsi-meet-web-config package post-installation script subprocess returned error exit status 1
No apport report written because the error message indicates it’s a follow-up error from a previous failure.
dpkg: dependency problems prevent configuration of jitsi-meet:
jitsi-meet depends on jitsi-meet-web-config (= 1.0.3969-1); however:
Package jitsi-meet-web-config is not configured yet.

dpkg: error processing package jitsi-meet (–configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
jitsi-meet-web-config
jitsi-meet
E: Sub-process /usr/bin/dpkg returned an error code (1)

Thanks, that helped a lot.
For some reasons we had a restrictive DNS Rule that blocked this query:

dig +short myip.opendns.com @resolver1.opendns.com

After purging and reinstalling jitsi-meet I no longer see this error with jitsi-meet-turnserver…

But it seems that I ran in another error, that nginx won’t work properly with the ssl cert.

I assume that I did a typo by entering the passphrase for the SSL Cert or the promt for entering the passphrase did never appear!

If I execute nginx-t I can enter the correct pass phrase, but where is this info stored?

root@meet:~# nginx -t
Enter PEM pass phrase:
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
root@meet:~#

Purging and reinstalling jitisi-meet doesn’t ask me for the passphrase again.

Thanks for any advice,
Daniel

well, I think the package find its nginx dependency already satisfied and so all is well with nginx and its certificate. Try to purge nginx also. When you purge a software, always look if the config directory
/etc/someapp
still exists, it’s a sure indication that there is still something installed that keeps it alive (unless the uninstall package warns you that it should delete it and it’s not empty, in this case that’s someone has created/modified files by hand and in this case it’s better to delete them by hand before reinstalling.
If you want to start again, always remove everything (look in the /var/log/apt directory to see what was installed)

With apt upgrade etc, I now get:
jitsi-meet-prosody
jitsi-meet
jitsi-meet-turnserver
E: Sub-process /usr/bin/dpkg returned an error code (1)
How do I stop this?

I uninstalled using sudo apt remove jitsi* nginx. That went Ok. I reinstalled jitsi meet but didn’t get a request for a FDQN as per github’s Quick Install Guide.
How do I change the stored FDQN (as I mistyped it on first install) or how do I remove any files it’s stored in?

Now I’m confused.
After I couldn’t find the error in any of the configuration files with nginx, I’ve decided to setup a new ubuntu Server and begin with a new jitsi-meet installation from scratch. The setup went through fine so far.
In the step where the setup asks about the SSL Cert I did choose to use my own SSL Cert.
In a further step the setup asks to put the *.crt file and the *.key file in the /etc/SSL directory what I did.

In a previous Installation I remember that the setup did ask for a passphrase to setup the SSL Cert, but that didn’t happen.

Job for nginx.service failed because the control process exited with error code.
See “systemctl status nginx.service” and “journalctl -xe” for details.
invoke-rc.d: initscript nginx, action “reload” failed.

If I execute: journalctl -xe I get the following output:

Apr 09 11:43:33 meet turnserver[7106]: 0: turn server id=2 created
Apr 09 11:43:33 meet turnserver[7106]: 0: turn server id=0 created
Apr 09 11:43:33 meet turnserver[7106]: 0: turn server id=4 created
Apr 09 11:43:33 meet turnserver[7106]: 0: turn server id=3 created
Apr 09 11:43:33 meet turnserver[7106]: 0: IO method (general relay thread): epoll (with changelist)
Apr 09 11:43:33 meet turnserver[7106]: 0: IO method (general relay thread): epoll (with changelist)
Apr 09 11:43:33 meet turnserver[7106]: 0: turn server id=1 created
Apr 09 11:43:33 meet turnserver[7106]: 0: turn server id=5 created
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. DTLS/UDP listener opened on: 127.0.0.1:443
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. DTLS/UDP listener opened on: 127.0.0.1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. DTLS/UDP listener opened on: 10.30.98.112:443
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. DTLS/UDP listener opened on: 10.30.98.112:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv6. DTLS/UDP listener opened on: ::1:443
Apr 09 11:43:33 meet kernel: sctp: Hash tables configured (bind 256/256)
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. TLS/SCTP listener opened on : 127.0.0.1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. TLS listener opened on : 127.0.0.1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv6. DTLS/UDP listener opened on: ::1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. TLS/SCTP listener opened on : 10.30.98.112:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. TLS listener opened on : 10.30.98.112:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv6. TLS/SCTP listener opened on : ::1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. TLS listener opened on : 127.0.0.1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv6. TLS listener opened on : ::1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. TLS listener opened on : 127.0.0.1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. TLS listener opened on : 10.30.98.112:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. TLS listener opened on : 10.30.98.112:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: Total General servers: 6
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. TLS listener opened on : 127.0.0.1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv6. TLS listener opened on : ::1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv6. TLS listener opened on : ::1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. TLS listener opened on : 10.30.98.112:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. TLS listener opened on : 127.0.0.1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. TLS listener opened on : 10.30.98.112:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. TLS listener opened on : 127.0.0.1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv6. TLS listener opened on : ::1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv4. TLS listener opened on : 10.30.98.112:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IO method (auth thread): epoll (with changelist)
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv6. TLS listener opened on : ::1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IPv6. TLS listener opened on : ::1:4445
Apr 09 11:43:33 meet turnserver[7106]: 0: IO method (auth thread): epoll (with changelist)
Apr 09 11:43:33 meet turnserver[7106]: 0: IO method (auth thread): epoll (with changelist)
Apr 09 11:43:33 meet turnserver[7106]: 0: IO method (admin thread): epoll (with changelist)
Apr 09 11:43:33 meet turnserver[7106]: 0: SQLite DB connection success: /var/lib/turn/turndb
Apr 09 11:43:33 meet systemd[1]: Reloading A high performance web server and a reverse proxy server.
– Subject: Unit nginx.service has begun reloading its configuration
– Defined-By: systemd
– Support: http://www.ubuntu.com/support

– Unit nginx.service has begun reloading its configuration
Apr 09 11:43:33 meet nginx[7190]: Enter PEM pass phrase:
Apr 09 11:43:33 meet nginx[7190]: nginx: [emerg] SSL_CTX_use_PrivateKey_file("/etc/ssl/meet.**********.key") failed (SSL: error:2807106B:UI routines:UI_process:processing error:while reading
Apr 09 11:43:33 meet systemd[1]: nginx.service: Control process exited, code=exited status=1
Apr 09 11:43:33 meet systemd[1]: Reload failed for A high performance web server and a reverse proxy server.
– Subject: Unit nginx.service has finished reloading its configuration
– Defined-By: systemd
– Support: http://www.ubuntu.com/support

– Unit nginx.service has finished reloading its configuration

I know the passphrase for the certificate, but why did the setup not ask for it?
Has anyone an advise what I can do to fix this error?

Thanks in advance for every help

Remove the passphrase?

I found a post elsewhere on how to do this:
sudo dpkg-reconfigure FQDN jitsi-videobridge2
(where FDQN is the new FDQN).
It worked in that it changed a number of conf files.
I did similar for all other jitsi packages. Only one that gave any messages was jitsi-meet-web-config:
root@JohnPC:/home/john# dpkg-reconfigure jitsi-meet-web-config
Can’t load /root/.rnd into RNG
140239277429184: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/FQDN.key’ (where is my FQDN)


You can now switch to a Let’s Encrypt certificate. To do so, execute:
/usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh

So I did the lets-encrypt-cert.sh:
All went well except after installing a number of packages and generating a certificate, it gave:
http-01 challenge for FQDN (where FQDN is my FQDN)
Using the webroot path /usr/share/jitsi-meet for all unmatched domains.
Waiting for verification…
Challenge failed for domain johnjitsimeet.myddns.me
http-01 challenge for FQDN (where FQDN is my FQDN)
Cleaning up challenges
Some challenges have failed.

Anybody suggest a solution?
PS Apologies for not putting the above log extracts as a “Code” block as I couldn’t figure out how to do it!

Well, I tried to install Jitsi in 18.04 (AWS) with no success, triggering the error seen in [jitsi-users] java.lang.NoClassDefFoundError: Could not initialize class org.jitsi.sctp4j.Sctp

I had to “downgrade” to 16.10 (I think that’s the version AWS offers) to make it work.