After uninstalling the jitsi, when reinstalling . getting this error

Setting up ruby-hocon (1.2.5-1) …
Setting up jitsi-meet-web (1.0.4985-1) …
Setting up jitsi-meet-prosody (1.0.4985-1) …
The given hostname does not exist in the config
grep: /etc/prosody/conf.avail/meet..com.cfg.lua: No such file or directory
grep: /etc/prosody/conf.avail/meet.

.com.cfg.lua: No such file or directory
modulemanager error Unable to load module ‘roster_command’: /usr/lib/prosody/modules/mod_roster_command.lua: No such file or directory
Failed to load module ‘roster_command’: /usr/lib/prosody/modules/mod_roster_command.lua: No such file or directory
dpkg: error processing package jitsi-meet-prosody (–configure):
installed jitsi-meet-prosody package post-installation script subprocess returned error exit status 1
Setting up jicofo (1.0-747-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.4985-1); however:
Package jitsi-meet-prosody is not configured yet.

dpkg: error processing package jitsi-meet (–configure):
dependency problems - leaving unconfigured
Processing triggers for man-db (2.8.3-2ubuntu0.1) …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.39) …
Errors were encountered while processing:
jitsi-meet-prosody
jitsi-meet
E: Sub-process /usr/bin/dpkg returned an error code (1)

It might be the case that the debconf db might have retain some values skipping part of the installation process.

We wrote a tool to clean/purge previous installations without the need reset the complete OS.

Maybe this can be of help.
Cheers.