search

spantaleev / matrix-docker-ansible-deploy

🐳 Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker
GNU Affero General Public License v3.0
4.9k stars 1.04k forks source link

Can’t create conference rooms on fresh Jitsi setup #1577

Open gunwald opened 2 years ago

gunwald commented 2 years ago

What does not work?

Hey everybody! I have some trouble to get Jitsi running. I set Jitsi up successfully with username and password protection. But I can’t start a meeting. I do not get a field to put password and username in on the web interface and when I create a meeting I cant enter in myself. This is where I’m stuck. Clicking on »Join meeting« does not have any effect: grafik

The logs do not show anything jitsi related but: INFO: Performed a successful health check in PT0.000016S. Sticky failure: false This is where is stuck: Can’t click »join meeting« or I can, but nothing happens…

What did I try to debug / solve the issue?

I checked the ports

According to the Jitsi community my console log indicates:

»You never connected bosh or websockets for the xmpp signalling is busted.«

So first I double checked if my ports are open, they are:

netstat -tulpen | grep 10000
udp        0      0 0.0.0.0:10000           0.0.0.0:*                           0          2055250071 12016/docker-proxy  
udp6       0      0 :::10000                :::*                                0          2055250077 12054/docker-proxy
netstat -tulpen | grep 4443
tcp        0      0 0.0.0.0:4443            0.0.0.0:*               LISTEN      0          2055251227 12097/docker-proxy  
tcp6       0      0 :::4443                 :::*                    LISTEN      0          2055250114 12107/docker-proxy

I checked http-bind

I also checked my deployment on http-bind: grafik

Looks great, I suppose.

I followed the troubleshooting guide in the docs

Of course I tried several times to delete Jitsi completely as recommended here: https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-jitsi.md#rebuilding-your-jitsi-installation To no effect.

Maybe it is related to some kind of permission issue? I have authentication activated and I do not get asked to put my username and password in at any point. I would expect a dialog popping up or something.

What else?

During one of my attempts to completely reinstall Jitsi I noticed the following error:

 systemctl stop matrix-jitsi-*
 rm -rf /matrix/jitsi
TASK [Ensure systemd reloaded after matrix-jitsi-web.service installation] ***************************************
TASK [Check existence of matrix-jitsi-web service] ***************************************************************
TASK [Ensure matrix-jitsi-web is stopped] ************************************************************************
TASK [Ensure matrix-jitsi-web.service doesn't exist] *************************************************************
skipping: [matrix.XXX.de]
  ansible_loop_var: item
  cmd: docker exec matrix-jitsi-prosody prosodyctl --config /config/prosody.cfg.lua register jitsi-moderator meet.
  end: '2022-01-25 18:35:22.965892'
  item:
 ansible-playbook -i inventory/hosts     password: XXX
    username: jitsi-XXX
  msg: non-zero return code
  rc: 1
  start: '2022-01-25 18:35:22.398803'
  stderr: ''
  stderr_lines: <omitted>
  stdout: |2-

    **************************
    Prosody was unable to find the configuration file.
    We looked for: /etc/prosody//config/prosody.cfg.lua
    A sample config file is included in the Prosody download called prosody.cfg.lua.dist
    Copy or rename it to prosody.cfg.lua and edit as necessary.
    More help on configuring Prosody can be found at https://prosody.im/doc/configure
    Good luck!
    **************************
  stdout_lines: <omitted>

PLAY RECAP *******************************************************************************************************
matrix.XXX : ok=33   changed=7    unreachable=0    failed=1    skipped=158  rescued=0    ignored=0   setup.yml --tags=setup-jitsi,start

This does not happen if I run:

ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start

instead. Or if I disable authentication in the configs. But It does not work without authentication neither.

PS

It seems that prosody has some problems starting up for some reason. systemctl status matrix-jitsi-prosody.service gives:

● matrix-jitsi-prosody.service - Matrix jitsi-prosody server
   Loaded: loaded (/etc/systemd/system/matrix-jitsi-prosody.service; enabled; vendor preset: enabled)                                                                          
   Active: active (running) since Tue 2022-01-25 18:35:21 CET; 3h 51min ago
  Process: 28282 ExecStartPre=/usr/bin/env sh -c /usr/bin/env docker kill matrix-jitsi-prosody 2>/dev/null (code=exited, status=1/FAILURE)                                     
  Process: 28291 ExecStartPre=/usr/bin/env sh -c /usr/bin/env docker rm matrix-jitsi-prosody 2>/dev/null (code=exited, status=1/FAILURE)                                       
 Main PID: 28318 (docker)
    Tasks: 9 (limit: 4915)
   Memory: 24.2M
   CGroup: /system.slice/matrix-jitsi-prosody.service
           └─28318 docker run --rm --name matrix-jitsi-prosody --log-driver=none --network=matrix --network-alias=xmpp.meet.jitsi --env-file=/matrix/jitsi/prosody/env --mount t

Jan 25 18:35:24 v22019021470482518 matrix-jitsi-prosody[28318]: avmoderation.meet.jitsi:tls                                  info        Certificates loaded                   
Jan 25 18:35:24 v22019021470482518 matrix-jitsi-prosody[28318]: avmoderation.meet.jitsi:av_moderation_component              info        Hook to muc events on muc.meet.jitsi  
Jan 25 18:35:24 v22019021470482518 matrix-jitsi-prosody[28318]: speakerstats.meet.jitsi:speakerstats_component               info        Hook to muc events on muc.meet.jitsi  
Jan 25 18:35:24 v22019021470482518 matrix-jitsi-prosody[28318]: conferenceduration.meet.jitsi:conference_duration_component  info        Hook to muc events on muc.meet.jitsi  
Jan 25 18:35:24 v22019021470482518 matrix-jitsi-prosody[28318]: meet.jitsi:muc_breakout_rooms                                info        Hook to muc events on muc.meet.jitsi  
Jan 25 18:35:24 v22019021470482518 matrix-jitsi-prosody[28318]: muc.meet.jitsi:tls                                           info        Certificates loaded                   
Jan 25 18:35:24 v22019021470482518 matrix-jitsi-prosody[28318]: meet.jitsi:muc_breakout_rooms                                info        Breakout rooms component created breako
Jan 25 18:35:24 v22019021470482518 matrix-jitsi-prosody[28318]: meet.jitsi:muc_breakout_rooms                                info        Hook to muc events on breakout.meet.jit
Jan 25 18:35:24 v22019021470482518 matrix-jitsi-prosody[28318]: breakout.meet.jitsi:tls                                      info        Certificates loaded                   
Jan 25 18:35:24 v22019021470482518 matrix-jitsi-prosody[28318]: auth.meet.jitsi:tls

Can anybody give me a hint how to debug further?

gunwald commented 2 years ago

It seems that the https://jitsi.example.com/config.js is not correct. See: https://community.jitsi.org/t/cant-create-conference-rooms-on-fresh-jitsi-setup/110512/12

ibLANtest commented 2 years ago

I have the same problem and it would be great if someone with insight could take a look at this. I am a relative beginner and basically following just the crumbs that I am able to find. Which variable do I have to configure in the ansible setup to set own jitsi.domain in /matrix/jitsi/web/config/config.js. I saw: domain: 'jitsi-meet.example.com', muc: 'conference.jitsi-meet.example.com' bosh: '//jitsi-meet.example.com/http-bind', urls: 'stun:meet-jit-si-turnrelay.jitsi.net:443'

Obviously editing /matrix/jitsi/web/config/config.js does not make sense, i guess because of docker. (Yeap, docker newbe here). So there must be a variable that should set these values by the ansible-playbook. Does this has to do with matrix_jitsi_web_custom_interface_config_extension ? If yes, how to use it?

@gunwald indicated that it might have worked before at the end of https://community.jitsi.org/t/cant-create-conference-rooms-on-fresh-jitsi-setup/110512/12. Could it be an easy fix when checking previous versions?

Thanks for all the help!

spantaleev commented 2 years ago

It seems like one of the the last few Jitsi upgrades broke Jitsi. This may either be a regression in Jitsi itself (less likely) or a problem with us upgrading. Perhaps we haven't migrated some new configuration options or something.

We can downgrade to a version that worked.

I don't use Jitsi and I can't find the time to spend maintaining this Jitsi setup up to date. This playbook has grown huge and I can't keep up with maintaining everything myself. It'd be nice if someone else can step in and untangle this Jitsi mess, so we can get back to a setup that works (preferably on an up-to-date version of Jitsi).