Jitsi-meet-prosody configuration problems #9129
Labels
wontfix
Issue won't be fixed
Comments
|
From you posting to a prosody forum and no prosody installation in your trace I think you installed prosody yourself; maybe you even installed it from source without help of any packager (because of the libevent message; this don't happen when using the Prosody PPA). |
|
@gpatel-fr Do I have to install a different package instead of |
|
well, you did not install Ubuntu prosody package, you installed from the Prosody PPA. |
|
I did not specify an PPA in order to install Prosody, just used Since I purged the previous installation, I re-installed Jitsi-Meet, and used This is the complete output of both installation and What can we grasp from the output of I'm going to remove |
|
After removing I installed again Jitsi-Meet, but still have some issues : |
|
@gpatel-fr I noticed another different issue, which might, or might not, be related to the configuration problems. I described it here: https://community.jitsi.org/t/jetty-server-activated-by-jitsi-meet-hampers-nginx-functioning/99009 |
it's baffling. I don't understand it actually.
Yet there are at least this instruction before:
if the file did not exist the trace should show something like that: and yet it does not appear. |
|
Is This is the content of that file. I do not see any |
no it's /var/lib/dpkg/info/jitsi-meet-prosody.postinst |
|
May be related to #8388. I'm also getting this on Ubuntu 20.04. |
|
Thank you @cedws . Actually I'm getting this message : |
|
It seems this problem only happens, if no preseeding is done as described in the scalable setup or if no other hostname than "localhost" is used. In the above case, the postinst script of the jitsi-meet-prosody debian package sees the localhost config of the prosody package and does not add its own config file: |
|
Thanks for pointing it out. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Ubuntu 18.04.4 Desktop I'm getting this error:
Package jitsi-meet-prosody is not configured yetThis is what I have in /etc/prosody/conf.d :
grasp.deals.cfg.lua :
VirtualHost "grasp.deals"
/etc/hosts :
I asked in the
Prosody chatand I've been rebounced back to here :Which package among the
libeventpackages has to be installed?I've installed
libevent-2.1-6,libevent-devandlibevent-core-2.1-6but still get message :libevent not foundand still getjitsi-meet-prosodyconfiguration problems :I tried also with
libevent1-devbut I get the same error messagesI've checked:
in /etc/hosts :
and whatever service used to check the hostname:
http://www.kloth.net/services/nslookup.php
https://www.ssllabs.com/ssltest/analyze.html?d=grasp.deals
I'm using a local PC with Ubuntu 18.04 to develop the app which will be deployed in a cloud server with Ubuntu 18.04 or newer version. It's not, I guess, a matter of PC or cloud-server, if the O.S., namely Ubuntu 18.04, is the same, because these guidelines: https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart are for Jitsi-Meet installation on a Debian-based GNU/Linux system.
I re-installed libevent-dev :
After purging everything, I re-installed Jitsi-Meet:
But still get the same error messages:
writing new private key to '/etc/jitsi/meet/grasp.deals.key'
-----
----------------
What I do not understand is this :
The host 'focus.grasp.deals' is not configured for this serverWhere does
focus.grasp.dealscome from? I didn't set anyfocus.grasp.dealsThe text was updated successfully, but these errors were encountered: