Errors were encountered while processing: jitsi-meet-prosody jitsi-meet

#1

I’m trying to install jitsi using aws EC2 instance but I got this error

dpkg: error processing package jitsi-meet-prosody (–configure):
installed jitsi-meet-prosody package post-installation script subprocess returned error exit status 127
Setting up jicofo (1.0-862-1) …
Updating /etc/jitsi/jicofo/config to use jicofo.conf
Generating an empty jicofo.conf file
useradd: warning: the home directory already exists.
Not copying any file from skel directory into it.
dpkg: dependency problems prevent configuration of jitsi-meet:
jitsi-meet depends on jitsi-meet-prosody (= 1.0.5913-1); however:
Package jitsi-meet-prosody is not configured yet.

dpkg: error processing package jitsi-meet (–configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for ureadahead (0.100.0-21) …
Processing triggers for systemd (237-3ubuntu10.53) …
Errors were encountered while processing:
jitsi-meet-prosody
jitsi-meet
E: Sub-process /usr/bin/dpkg returned an error code (1)

#2

Looks like you had/attempted a previous installation. You probably want to completely uninstall (purge) and remove all Jitsi-related files before reinstalling.

sudo apt-get purge jigasi jitsi-meet jitsi-meet-web-config jitsi-meet-prosody jitsi-meet-web jicofo jitsi-videobridge2

Then search for any remnants of jitsi-* and jicofo on your server and delete.

#3

I did that but it dosen’t work
the problem is that aws using ubuntu 18.04 so I should use Prosody version 0.11+ as written here
“Ubuntu 18.04 can be used, but Prosody version must be updated to 0.11+ before installation Jitsi Meet is not compatible with Prosody 0.12 at the moment”

I have a problem in this step.

#4

Why not use Ubuntu 20.04 LTS instead, particularly since you’re just starting? 18.04 is being less and less supported.

#5

I upgraded it to 20.04 but I get the same error

#6

If you don’t want to delete your server and recreate it, you may get help here but you need to provide precise information on the steps you are taking and the error(s) you get. It’s painful but that is the only way. If you want an easy procedure, recreate your server. Saying ‘I have a problem’ and ‘I tried but it don’t work’ don’t cut it, nobody in a public forum can help you with that, it’s too unclear.
I can only give you the general advice : sudo apt -f install is supposed to clean broken installs. Search the internet for more.

#7

dpkg: error processing package jitsi-meet-prosody (–configure):
installed jitsi-meet-prosody package post-installation script subprocess returned error exit status 127
Setting up jicofo (1.0-862-1) …
Updating /etc/jitsi/jicofo/config to use jicofo.conf
Generating an empty jicofo.conf file
useradd: warning: the home directory already exists.
Not copying any file from skel directory into it.
dpkg: dependency problems prevent configuration of jitsi-meet:
jitsi-meet depends on jitsi-meet-prosody (= 1.0.5913-1); however:
Package jitsi-meet-prosody is not configured yet.

dpkg: error processing package jitsi-meet (–configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of jitsi-meet-turnserver:
jitsi-meet-turnserver depends on jitsi-meet-prosody; however:
Package jitsi-meet-prosody is not configured yet.

dpkg: error processing package jitsi-meet-turnserver (–configure):
dependency problems - leaving unconfigured
Processing triggers for ureadahead (0.100.0-21) …
No apport report written because the error message indicates its a followup error from a previous failure.
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for systemd (237-3ubuntu10.53) …
Errors were encountered while processing:
jitsi-meet-prosody
jitsi-meet
jitsi-meet-turnserver
E: Sub-process /usr/bin/dpkg returned an error code (1)

#8

did you recreate a fresh installation ? or did you actually upgrade a broken installation ?

#9

I feel like you’re not really going with the suggestions. This info shows you’re trying to install on the same instance. You have two options:

  1. Wipe all jitsi-related stuff, including configs completely from the instance
  2. Start with a fresh instance

My recommendation is #2, to save yourself a ton of headaches.

1 Like
#10

I upgraded a broken intallation.

#11

Oh well. That’s not supposed to be possible.
Here is my last ditch defense against failing scripts:

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

should return you a bunch of tracing steps that could help figure out how to fix this thing if you post them here (try to hit the upload button since reading long traces on this forum is painful). I’ll not proceed today to actually reading it though. Maybe tomorrow.

#12

I solved the last problem but now I have another problem with my domain name:

Challenge failed for domain mydomain -com
http-01 challenge for mydomain -com
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: mydomain.com
    Type: dns
    Detail: no valid A records found for mydomain.com; no valid
    AAAA records found for mydomain -com

  • Your account credentials have been saved in your Certbot
    configuration directory at /etc/letsencrypt. You should make a
    secure backup of this folder now. This configuration directory will
    also contain certificates and private keys obtained by Certbot so
    making regular backups of this folder is ideal.

#13

Do you have a DNS A record for your FQDN?