JWT/iFrame Authentication Troubles

Something like this:

No… a completely different issue, at least according to the logs. The symptoms described in the OP are the same, but it appears that the problem is different.

My logs show no errors at the times that I’ve been having these issues, so I’m stumped.

Check the dev console as I described ^

Okay, will do. I’ve been working on other parts of my application while I’ve been waiting for responses and all that, so I’ve yet again rolled it back to an old version for the time being. I’ll try again after dinner.

To be clear, after I run the install command for jitsi-meet-token, it should work out of the box, right? Is there any config I need to set up for it to work in the prosody settings?

@damencho I appear to have gotten it working - somehow. I did this by copying over my config files from before I installed jitsi-meet-token to my local machine, installing jitsi-meet-token, then overwriting the updated config files with my old ones. I then manually changed the settings as I needed to. I will ask here if I run into any further issues. You and @emrah have been a lot of help, and I really appreciate it.

image

YEEESSSSSSSS!!!

We know your domain now.

You can check jitok to create tokens

Does it really matter? As long as I don’t expect someone to try to DDoS my servers or brute force my credentials, there’s not much harm.

I have a pretty same issue on Ubuntu 18.04 with JWT token authentication after update to Jitsi-Meet 2.0.5765
Previously all worked perfect.
No errors in logs.
Only on client console

Logger.js:154 2021-04-20T11:48:05.855Z [conference.js] <ne._onConferenceFailed>: CONFERENCE FAILED: conference.authenticationRequired

I did try method from here but no luck.

I installed lua5.2 and luarocks 5.2

# luarocks-5.2 list
Installed rocks:
----------------
basexx
   0.4.1-1 (installed) - /usr/local/lib/luarocks/rocks-5.2
lbase64
   20120807-3 (installed) - /usr/local/lib/luarocks/rocks-5.2
lua-cjson
   2.1.0-1 (installed) - /usr/local/lib/luarocks/rocks-5.2
luajwtjitsi
   2.0-0 (installed) - /usr/local/lib/luarocks/rocks-5.2
luaossl
   20200709-0 (installed) - /usr/local/lib/luarocks/rocks-5.2

# luarocks-5.2
LuaRocks 2.4.1, a module deployment system for Lua

skipped help info

CONFIGURATION
        Lua version: 5.2
        Configuration files:
                System: /usr/local/etc/luarocks/config-5.2.lua (ok)
                User  : /root/.luarocks/config-5.2.lua (not found)

        Rocks trees in use:
                /root/.luarocks ("user")
                /usr/local ("system")

# apt search jitsi | grep installed

jicofo/stable,now 1.0-740-1 all [installed]
jitsi-meet-prosody/stable,now 1.0.4900-1 all [installed]
jitsi-meet-tokens/stable,now 1.0.4900-1 all [installed]
jitsi-meet-web/stable,now 1.0.4900-1 all [installed]
jitsi-meet-web-config/stable,now 1.0.4900-1 all [installed]
jitsi-videobridge2/stable,now 2.1-478-gc6da57bd-1 all [installed]

# apt show jitsi-meet-tokens
Package: jitsi-meet-tokens
Version: 1.0.4900-1
Priority: extra
Section: net
Source: jitsi-meet-web
Maintainer: Jitsi Team <dev@jitsi.org>
Installed-Size: 20.5 kB
Depends: debconf (>= 0.5) | debconf-2.0, prosody-trunk (>= 1nightly747) | prosody-0.11 | prosody (>= 0.11.2), libssl1.0-dev | libssl-dev, luarocks, jitsi-meet-prosody, git
Homepage: https://jitsi.org/meet
Download-Size: 4,380 B
APT-Sources: https://download.jitsi.org stable/ Packages
Description: Prosody token authentication plugin for Jitsi Meet

Do you see any errors in Prosody?

No, /var/log/prosody/prosody.err file is clean after prosody restart.
Here is a prosody.log file right after restart and create room with JWT token

You seem to be using a Prosody nightly. Any chance you can test with Prosody 0.11? There might be some incompatibility we are not aware of at the moment.

I’d love to test it with prosody 0.11, but I don’t know how to install it (that current version).
Here is my dpkg -l 'prosody*' command output

# dpkg -l 'prosody*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                                      Version                           Architecture                      Description
+++-=========================================================-=================================-=================================-========================================================================================================================
rc  prosody                                                   0.10.0-1build1                    amd64                             Lightweight Jabber/XMPP server
un  prosody-0.11                                              <none>                            <none>                            (no description available)
un  prosody-modules                                           <none>                            <none>                            (no description available)
ii  prosody-trunk                                             1nightly1427-1~bionic             amd64                             Lightweight Jabber/XMPP server
un  prosody-xmpp-server

# prosodyctl about
Prosody trunk nightly build 1427 (2021-04-16, df4bd3af4099)

# Prosody directories
Data directory:     /var/lib/prosody
Config directory:   /etc/prosody
Source directory:   /usr/lib/prosody
Plugin directories:
  /var/lib/prosody/custom_plugins
  /usr/share/jitsi-meet/prosody-plugins/
  /usr/lib/prosody/modules/


# Operating system
Linux 4.15.0-142-generic

# Lua environment
Lua version:                    Lua 5.2

Lua module search paths:
  /usr/local/share/lua/5.2/prosody/?.lua
  /usr/local/share/lua/5.2/?.lua
  /usr/local/share/lua/5.2/prosody/?/init.lua
  /usr/local/share/lua/5.2/?/init.lua
  /usr/local/lib/lua/5.2/prosody/?.lua
  /usr/local/lib/lua/5.2/?.lua
  /usr/local/lib/lua/5.2/prosody/?/init.lua
  /usr/local/lib/lua/5.2/?/init.lua
  /usr/share/lua/5.2/prosody/?.lua
  /usr/share/lua/5.2/?.lua
  /usr/share/lua/5.2/prosody/?/init.lua
  /usr/share/lua/5.2/?/init.lua
  ./prosody/?.lua
  ./?.lua
  /root/.luarocks/share/lua/5.2/?.lua
  /root/.luarocks/share/lua/5.2/?/init.lua
  /var/lib/prosody/custom_plugins/share/lua/5.2/?.lua
  /var/lib/prosody/custom_plugins/share/lua/5.2/?/init.lua

Lua C module search paths:
  /usr/local/lib/lua/5.2/prosody/?.so
  /usr/local/lib/lua/5.2/?.so
  /usr/lib/x86_64-linux-gnu/lua/5.2/prosody/?.so
  /usr/lib/x86_64-linux-gnu/lua/5.2/?.so
  /usr/lib/lua/5.2/prosody/?.so
  /usr/lib/lua/5.2/?.so
  /usr/local/lib/lua/5.2/loadall.so
  ./prosody/?.so
  ./?.so
  /root/.luarocks/lib/lua/5.2/?.so

LuaRocks:               Installed (2.4.1)

# Network

Backend: epoll

# Lua module versions
LuaExpat:       1.3.0
LuaFileSystem:  1.6.3
LuaSec:         0.6
LuaSocket:      3.0-rc1

# library versions

I don’t remember I installed some nightly versions of prosody, all installs was via quick install doc or manual install doc files.

# apt-cache show prosody
Package: prosody
Version: 0.11.8-1~bionic1
Architecture: amd64
Maintainer: Matthew James Wild <mwild1@gmail.com>
Installed-Size: 1553
Depends: adduser, procps, lsb-base, lua5.2, lua-expat, lua-filesystem, lua-socket, openssl, ssl-cert, libc6 (>= 2.17), libidn11 (>= 1.13), libssl1.1 (>= 1.1.0)
Recommends: lua-sec (>= 0.5), ca-certificates
Suggests: lua-event, lua-dbi-mysql, lua-dbi-postgresql, lua-dbi-sqlite3
Conflicts: prosody, prosody-modules (<< 0.0~hg20170719.cd828b1cb5b9+dfsg-2), prosody-xmpp-server
Replaces: prosody, prosody-xmpp-server
Provides: prosody, prosody-xmpp-server, xmpp-server
Multi-Arch: foreign
Homepage: https://prosody.im/
Priority: optional
Section: net
Filename: pool/main/p/prosody/prosody_0.11.8-1~bionic1_amd64.deb
Size: 290592
SHA256: 5036b29a9ccef6c4413c0c4016fb88057e24ac4cf00caee6a20ca2ad0b026f1a
SHA1: 1c922237b48360adbd7d9fa0528247636755e659
MD5sum: 7053bc264afda26a43a02122a1467fbf
Description: Lightweight Jabber/XMPP server
 Prosody IM is a simple-to-use XMPP server. It is designed to be easy to
 extend via plugins, and light on resources.
Description-md5: e311eacea694f5a28f7fa157b396e6aa

Package: prosody
Architecture: amd64
Version: 0.10.0-1build1
Multi-Arch: foreign
Priority: extra
Section: universe/net
Origin: Ubuntu
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Matthew James Wild <mwild1@gmail.com>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 1287
Provides: xmpp-server
Depends: adduser, lsb-base, lua-expat (>= 1.2.0), lua-filesystem (>= 1.4.2-3~), lua5.1, lua5.1-bitop, lua5.1-expat, lua5.1-filesystem, lua5.1-sec, lua5.1-socket, ssl-cert, libc6 (>= 2.14), libidn11 (>= 1.13), libssl1.1 (>= 1.1.0)
Recommends: lua5.1-event
Suggests: lua-dbi-mysql, lua-dbi-postgresql, lua-dbi-sqlite3, lua-zlib
Conflicts: prosody-modules (<< 0.0~hg20170719.cd828b1cb5b9+dfsg-1)
Filename: pool/universe/p/prosody/prosody_0.10.0-1build1_amd64.deb
Size: 244040
MD5sum: d8ec16b4392833d592c11a8a9b30919b
SHA1: ed6bf66e036f5677d5a9ff4f819f081ea9bc3b9d
SHA256: 2b5bdc2dc3eab884f983e4b6e294c2bf520f13350ff96dfc1679c5ff7bdcfad9
Homepage: http://www.prosody.im/
Description-en: Lightweight Jabber/XMPP server
 Prosody is a modern XMPP communication server. It aims to be
 easy to set up and configure, and efficient with system resources.
 Additionally, for developers it aims to be easy to extend and
 give a flexible system on which to rapidly develop added
 functionality, or prototype new protocols.
Description-md5: 12d4cb414b879c7a9ec6762a4708b10c


# apt upgrade jitsi-meet-prosody
Reading package lists... Done
Building dependency tree
Reading state information... Done
jitsi-meet-prosody is already the newest version (1.0.4900-1).
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@s-rc-jitsi-prp-01:~# apt upgrade prosody
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 prosody : Conflicts: prosody
           Conflicts: prosody-xmpp-server
 prosody-trunk : Conflicts: prosody
                 Conflicts: prosody-xmpp-server
                 Recommends: lua-unbound but it is not installable
E: Broken packages

I deleted prosody-trunk package (somehow both prosody and prosody-trunk was installed on system) and now looks like I have only Prosody 0.11.8

# apt remove prosody-trunk
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  lua-bitop
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
  prosody
Suggested packages:
  lua-dbi-mysql lua-dbi-postgresql lua-dbi-sqlite3
The following packages will be REMOVED:
  prosody-trunk
The following NEW packages will be installed:
  prosody
0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 291 kB of archives.
After this operation, 816 kB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 https://packages.prosody.im/debian bionic/main amd64 prosody amd64 0.11.8-1~bionic1 [291 kB]
Fetched 291 kB in 1s (232 kB/s)
dpkg: prosody-trunk: dependency problems, but removing anyway as you requested:
 jitsi-meet-tokens depends on prosody-trunk (>= 1nightly747) | prosody-0.11 | prosody (>= 0.11.2); however:
  Package prosody-trunk is to be removed.
  Package prosody-0.11 is not installed.
  Package prosody is not installed.
  Package prosody-trunk which provides prosody is to be removed.
 jitsi-meet-prosody depends on prosody | prosody-trunk | prosody-0.11; however:
  Package prosody is not installed.
  Package prosody-trunk which provides prosody is to be removed.
  Package prosody-trunk is to be removed.
  Package prosody-0.11 is not installed.
 jitsi-meet-tokens depends on prosody-trunk (>= 1nightly747) | prosody-0.11 | prosody (>= 0.11.2); however:
  Package prosody-trunk is to be removed.
  Package prosody-0.11 is not installed.
  Package prosody is not installed.
  Package prosody-trunk which provides prosody is to be removed.
 jitsi-meet-prosody depends on prosody | prosody-trunk | prosody-0.11; however:
  Package prosody is not installed.
  Package prosody-trunk which provides prosody is to be removed.
  Package prosody-trunk is to be removed.
  Package prosody-0.11 is not installed.

(Reading database ... 117854 files and directories currently installed.)
Removing prosody-trunk (1nightly1427-1~bionic) ...
Selecting previously unselected package prosody.
(Reading database ... 117232 files and directories currently installed.)
Preparing to unpack .../prosody_0.11.8-1~bionic1_amd64.deb ...
Unpacking prosody (0.11.8-1~bionic1) ...
dpkg: warning: unable to delete old directory '/etc/prosody/conf.avail': Directory not empty
Setting up prosody (0.11.8-1~bionic1) ...
Installing new version of config file /etc/init.d/prosody ...

Configuration file '/etc/prosody/prosody.cfg.lua'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** prosody.cfg.lua (Y/I/N/O/D/Z) [default=N] ? y
Installing new version of config file /etc/prosody/prosody.cfg.lua ...
Processing triggers for libc-bin (2.27-3ubuntu1.4) ...
Processing triggers for systemd (237-3ubuntu10.46) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for ureadahead (0.100.0-21) ...
root@s-rc-jitsi-prp-01:~# apt install prosody
Reading package lists... Done
Building dependency tree
Reading state information... Done
prosody is already the newest version (0.11.8-1~bionic1).
prosody set to manually installed.
The following package was automatically installed and is no longer required:
  lua-bitop
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@s-rc-jitsi-prp-01:~# prosodyctl about
Prosody 0.11.8

# Prosody directories
Data directory:     /var/lib/prosody
Config directory:   /etc/prosody
Source directory:   /usr/lib/prosody
Plugin directories:
  /usr/lib/prosody/modules/


# Lua environment
Lua version:                    Lua 5.2

Lua module search paths:
  /usr/lib/prosody/?.lua
  /usr/local/share/lua/5.2/?.lua
  /usr/local/share/lua/5.2/?/init.lua
  /usr/local/lib/lua/5.2/?.lua
  /usr/local/lib/lua/5.2/?/init.lua
  /usr/share/lua/5.2/?.lua
  /usr/share/lua/5.2/?/init.lua
  /root/.luarocks/share/lua/5.2/?.lua
  /root/.luarocks/share/lua/5.2/?/init.lua

Lua C module search paths:
  /usr/lib/prosody/?.so
  /usr/local/lib/lua/5.2/?.so
  /usr/lib/x86_64-linux-gnu/lua/5.2/?.so
  /usr/lib/lua/5.2/?.so
  /usr/local/lib/lua/5.2/loadall.so
  /root/.luarocks/lib/lua/5.2/?.so

LuaRocks:               Installed (2.4.1)

# Network

Backend: select

# Lua module versions
lfs:            LuaFileSystem 1.6.3
libevent:       2.1.8-stable
luaevent:       0.4.6
lxp:            LuaExpat 1.3.0
socket:         LuaSocket 3.0-rc1
ssl:            0.6

Did that make any difference?

No… Same clean err log and nothing saying log and this error

Apr 21 11:28:59 startup info    Hello and welcome to Prosody version 0.11.8
Apr 21 11:28:59 startup info    Prosody is using the select backend for connection handling
Apr 21 11:28:59 internal.auth.jitsidev.bcs.ru:tls       info    Certificates loaded
Apr 21 11:28:59 portmanager     info    Activated service 's2s' on [*]:5269, [::]:5269
Apr 21 11:28:59 auth.jitsidev.bcs.ru:tls        info    Certificates loaded
Apr 21 11:28:59 portmanager     info    Activated service 'c2s' on [*]:5222, [::]:5222
Apr 21 11:28:59 portmanager     info    Activated service 'legacy_ssl' on no ports
Apr 21 11:28:59 focus.jitsidev.bcs.ru:tls       info    Certificates loaded
Apr 21 11:28:59 general info    Starting conference duration timer for conference.jitsidev.bcs.ru
Apr 21 11:28:59 conferenceduration.jitsidev.bcs.ru:conference_duration_component        info    No muc component found, will listen for it: conference.jitsidev.bcs.ru
Apr 21 11:28:59 conferenceduration.jitsidev.bcs.ru:tls  info    Certificates loaded
Apr 21 11:28:59 conferenceduration.jitsidev.bcs.ru:conference_duration_component        info    Hook to muc events on conference.jitsidev.bcs.ru
Apr 21 11:28:59 conference.jitsidev.bcs.ru:tls  info    Certificates loaded
Apr 21 11:28:59 conference.jitsidev.bcs.ru:muc_domain_mapper    info    Loading mod_muc_domain_mapper for host conference.jitsidev.bcs.ru!
Apr 21 11:28:59 conference.jitsidev.bcs.ru:muc_domain_mapper    info    Loading mod_muc_domain_mapper for host internal.auth.jitsidev.bcs.ru!
Apr 21 11:28:59 conference.jitsidev.bcs.ru:muc_domain_mapper    info    Loading mod_muc_domain_mapper for host auth.jitsidev.bcs.ru!
Apr 21 11:28:59 conference.jitsidev.bcs.ru:muc_domain_mapper    info    Loading mod_muc_domain_mapper for host focus.jitsidev.bcs.ru!
Apr 21 11:28:59 conference.jitsidev.bcs.ru:muc_domain_mapper    info    Loading mod_muc_domain_mapper for host conferenceduration.jitsidev.bcs.ru!
Apr 21 11:28:59 conference.jitsidev.bcs.ru:muc_domain_mapper    info    Loading mod_muc_domain_mapper for host jitsidev.bcs.ru!
Apr 21 11:28:59 jitsidev.bcs.ru:tls     info    Certificates loaded
Apr 21 11:28:59 portmanager     info    Activated service 'http' on [*]:5280, [::]:5280
Apr 21 11:28:59 portmanager     info    Activated service 'https' on [*]:5281, [::]:5281
Apr 21 11:29:00 guest.jitsidev.bcs.ru:auth_token        warn    WARNING - empty tokens allowed
Apr 21 11:29:00 conference.jitsidev.bcs.ru:muc_domain_mapper    info    Loading mod_muc_domain_mapper for host guest.jitsidev.bcs.ru!
Apr 21 11:29:00 guest.jitsidev.bcs.ru:tls       info    Certificates loaded
Apr 21 11:29:00 conference.jitsidev.bcs.ru:muc_domain_mapper    info    Loading mod_muc_domain_mapper for host speakerstats.jitsidev.bcs.ru!
Apr 21 11:29:00 general info    Starting speakerstats for conference.jitsidev.bcs.ru
Apr 21 11:29:00 speakerstats.jitsidev.bcs.ru:speakerstats_component     info    Hook to muc events on conference.jitsidev.bcs.ru
Apr 21 11:29:00 speakerstats.jitsidev.bcs.ru:tls        info    Certificates loaded
Apr 21 11:29:02 c2s560ca86ebac0 info    Client connected
Apr 21 11:29:02 c2s560ca86ebac0 info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Apr 21 11:29:02 c2s560ca86ebac0 info    Authenticated as jvb@auth.jitsidev.bcs.ru
Apr 21 11:29:04 c2s560ca85db120 info    Client connected
Apr 21 11:29:04 c2s560ca85db120 info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Apr 21 11:29:05 c2s560ca85db120 info    Authenticated as focus@auth.jitsidev.bcs.ru
Apr 21 11:29:08 mod_bosh        info    Client tried to use sid '6f356e29-ec52-4d7b-aa13-7da6856883bc' which we don't know about
Apr 21 11:29:08 mod_bosh        info    Client tried to use sid '6f356e29-ec52-4d7b-aa13-7da6856883bc' which we don't know about
Apr 21 11:29:29 mod_bosh        info    New BOSH session, assigned it sid '7d381cbc-9cfb-429c-b14e-a6525090b2a8'
Apr 21 11:29:29 bosh7d381cbc-9cfb-429c-b14e-a6525090b2a8        info    Authenticated as 0f17d54f-0e61-4c66-a9b2-9122b4eeb0cd@jitsidev.bcs.ru
Apr 21 11:29:32 bosh7d381cbc-9cfb-429c-b14e-a6525090b2a8        info    BOSH client disconnected: session close

But I think JWT is working partly - avatar is come from JWT

Now I get jicofo error SEVERE: Failed to connect/login: SASLError using SCRAM-SHA-1: not-authorized

Apr 21, 2021 12:09:25 PM org.jitsi.utils.logging2.LoggerImpl log
SEVERE: Failed to connect/login: SASLError using SCRAM-SHA-1: not-authorized
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
        at org.jivesoftware.smack.SASLAuthentication.authenticationFailed(SASLAuthentication.java:292)
        at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1100)
        at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:1000)
        at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:1016)
        at java.lang.Thread.run(Thread.java:748)

We did try to comply to PR Remove the "focus" external component, use client_proxy instead. (#8381) · jitsi/jitsi-meet@b6f7f8f · GitHub and now it’s lead to that error I guess

I think I fixed that with authentication = "internal_hashed" in auth.jitsi-meet.example.com section of /etc/prosody/conf.d/jitsi-meet.example.com file. And with

Component "focus.jitsi-meet.example.com" "client_proxy"
    target_address = "focus@auth.jitsi-meet.example.com"

And now I have this in jicofo log

Apr 21, 2021 12:56:44 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Starting Jicofo.
Apr 21, 2021 12:56:44 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Initialized newConfig: merge of /etc/jitsi/jicofo/jicofo.conf: 1,system properties,reference.conf @ jar:file:/usr/share/jicofo/jicofo.jar!/reference.conf: 1
Apr 21, 2021 12:56:44 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: loading config file at path /etc/jitsi/jicofo/sip-communicator.properties
Apr 21, 2021 12:56:44 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Error loading config file: java.io.FileNotFoundException: /etc/jitsi/jicofo/sip-communicator.properties (No such file or directory)
Apr 21, 2021 12:56:44 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Initialized legacyConfig: sip communicator props (no description provided)
Apr 21, 2021 12:56:44 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Reloading the Typesafe config source (previously reloaded 0 times).
Apr 21, 2021 12:56:45 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: No dedicated Service XMPP connection configured, re-using the client XMPP connection.
Apr 21, 2021 12:56:45 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Using org.jitsi.jicofo.bridge.IntraRegionBridgeSelectionStrategy
Apr 21, 2021 12:56:45 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Initialized with JID=jvbbrewery@internal.auth.jitsidev.bcs.ru
Apr 21, 2021 12:56:45 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: No Jibri detector configured.
Apr 21, 2021 12:56:45 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: No SIP Jibri detector configured.
Apr 21, 2021 12:56:45 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: No Jigasi detector configured.
Apr 21, 2021 12:56:45 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Initialized octoId=15
Apr 21, 2021 12:56:45 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Starting authentication service with config=AuthConfig[enabled=true, type=JWT, loginUrl=jitsidev.bcs.ru, logoutUrl=null, authenticationLifetime=PT24H, enableAutoLogin=true].
Apr 21, 2021 12:56:45 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Auto login disabled
Apr 21, 2021 12:56:45 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Authentication lifetime: PT1M
Apr 21, 2021 12:56:45 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Registering IQ handlers with XmppConnection.
Apr 21, 2021 12:56:45 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Starting HTTP server with config: host=null, port=8888, tlsPort=8843, isTls=false, keyStorePath=null.
Apr 21, 2021 12:56:45 PM org.eclipse.jetty.util.log.Log initialized
INFO: Logging initialized @1464ms to org.eclipse.jetty.util.log.Slf4jLog
Apr 21, 2021 12:56:45 PM org.eclipse.jetty.server.Server doStart
INFO: jetty-9.4.35.v20201120; built: 2020-11-20T21:17:03.964Z; git: bdc54f03a5e0a7e280fab27f55c3c75ee8da89fb; jvm 1.8.0_282-8u282-b08-0ubuntu1~18.04-b08
Apr 21, 2021 12:56:45 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Connected, JID= null
Apr 21, 2021 12:56:46 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Joined the room.
Apr 21, 2021 12:56:46 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Set replyTimeout=PT15S
Apr 21, 2021 12:56:46 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Added brewery instance: jvbbrewery@internal.auth.jitsidev.bcs.ru/jvb-02
Apr 21, 2021 12:56:46 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Added new videobridge: Bridge[jid=jvbbrewery@internal.auth.jitsidev.bcs.ru/jvb-02, relayId=172.18.106.170:4092, region=nsk, stress=0.00]
Apr 21, 2021 12:56:46 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Scheduled health-check task for: jvbbrewery@internal.auth.jitsidev.bcs.ru/jvb-02
Apr 21, 2021 12:56:46 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Added brewery instance: jvbbrewery@internal.auth.jitsidev.bcs.ru/019372d4-8588-4caf-af0c-51263690928f
Apr 21, 2021 12:56:46 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Added new videobridge: Bridge[jid=jvbbrewery@internal.auth.jitsidev.bcs.ru/019372d4-8588-4caf-af0c-51263690928f, relayId=172.18.106.168:4091, region=nsk, stress=0.00]
Apr 21, 2021 12:56:46 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Scheduled health-check task for: jvbbrewery@internal.auth.jitsidev.bcs.ru/019372d4-8588-4caf-af0c-51263690928f
Apr 21, 2021 12:56:46 PM org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
WARNING: A provider org.jitsi.rest.Version registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Version will be ignored.
Apr 21, 2021 12:56:46 PM org.eclipse.jetty.server.handler.ContextHandler doStart
INFO: Started o.e.j.s.ServletContextHandler@b016b4e{/,null,AVAILABLE}
Apr 21, 2021 12:56:47 PM org.eclipse.jetty.server.AbstractConnector doStart
INFO: Started ServerConnector@6bb2d00b{HTTP/1.1, (http/1.1)}{0.0.0.0:8888}
Apr 21, 2021 12:56:47 PM org.eclipse.jetty.server.Server doStart
INFO: Started @2824ms
Apr 21, 2021 12:56:47 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Removed brewery instance: jvbbrewery@internal.auth.jitsidev.bcs.ru/019372d4-8588-4caf-af0c-51263690928f
Apr 21, 2021 12:56:47 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Removing JVB: jvbbrewery@internal.auth.jitsidev.bcs.ru/019372d4-8588-4caf-af0c-51263690928f
Apr 21, 2021 12:56:47 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Stopping health-check task for: jvbbrewery@internal.auth.jitsidev.bcs.ru/019372d4-8588-4caf-af0c-51263690928f
Apr 21, 2021 12:56:54 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Added brewery instance: jvbbrewery@internal.auth.jitsidev.bcs.ru/019372d4-8588-4caf-af0c-51263690928f
Apr 21, 2021 12:56:54 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Added new videobridge: Bridge[jid=jvbbrewery@internal.auth.jitsidev.bcs.ru/019372d4-8588-4caf-af0c-51263690928f, relayId=172.18.106.168:4091, region=nsk, stress=0.00]
Apr 21, 2021 12:56:54 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Scheduled health-check task for: jvbbrewery@internal.auth.jitsidev.bcs.ru/019372d4-8588-4caf-af0c-51263690928f
Apr 21, 2021 12:56:57 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Focus request for room: rocketchatsarzherbsqpolu33kgyfnydxfwddom9jeriode4twmg4i729goh@conference.jitsidev.bcs.ru
Apr 21, 2021 12:57:02 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Focus request for room: rocketchatsarzherbsqpolu33kgyfnydxfwddom9jeriode4twmg4i729goh@conference.jitsidev.bcs.ru
Apr 21, 2021 12:57:02 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Focus request for room: rocketchatsarzherbsqpolu33kgyfnydxfwddom9jeriode4twmg4i729goh@conference.jitsidev.bcs.ru
Apr 21, 2021 12:57:07 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Focus request for room: rocketchatsarzherbsqpolu33kgyfnydxfwddom9jeriode4twmg4i729goh@conference.jitsidev.bcs.ru
Apr 21, 2021 12:57:08 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Focus request for room: rocketchatsarzherbsqpolu33kgyfnydxfwddom9jeriode4twmg4i729goh@conference.jitsidev.bcs.ru
Apr 21, 2021 12:57:08 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Focus request for room: rocketchatsarzherbsqpolu33kgyfnydxfwddom9jeriode4twmg4i729goh@conference.jitsidev.bcs.ru
Apr 21, 2021 12:57:13 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Focus request for room: rocketchatsarzherbsqpolu33kgyfnydxfwddom9jeriode4twmg4i729goh@conference.jitsidev.bcs.ru
Apr 21, 2021 12:57:14 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Focus request for room: rocketchatsarzherbsqpolu33kgyfnydxfwddom9jeriode4twmg4i729goh@conference.jitsidev.bcs.ru
Apr 21, 2021 12:57:15 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Focus request for room: rocketchatsarzherbsqpolu33kgyfnydxfwddom9jeriode4twmg4i729goh@conference.jitsidev.bcs.ru
Apr 21, 2021 12:57:19 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Focus request for room: rocketchatsarzherbsqpolu33kgyfnydxfwddom9jeriode4twmg4i729goh@conference.jitsidev.bcs.ru
Apr 21, 2021 12:57:20 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Focus request for room: rocketchatsarzherbsqpolu33kgyfnydxfwddom9jeriode4twmg4i729goh@conference.jitsidev.bcs.ru
Apr 21, 2021 12:57:21 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Focus request for room: rocketchatsarzherbsqpolu33kgyfnydxfwddom9jeriode4twmg4i729goh@conference.jitsidev.bcs.ru

And that part is when I try to start new room

Apr 21, 2021 12:57:21 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Focus request for room: rocketchatsarzherbsqpolu33kgyfnydxfwddom9jeriode4twmg4i729goh@conference.jitsidev.bcs.ru

In devtools I see this

<text xmlns ="urn:ietf:params:xml:ns:xmpp-stanzas" xml:lang="en"> not authorized user domain </text>

@saghul can be that Cannot start conferences anymore if LDAP Auth is active with latest stable 5765 · Issue #1018 · jitsi/docker-jitsi-meet · GitHub issue?

UPD: Yes! I get it to work now!
With client-proxy = "focus.jitsidev.bcs.ru" in /etc/jitsi/jicofo/jicofo.conf file

Great! Are you using Docker? If so, we released a fix for this a couple of days ago…

No. We used to use docker, but then migrated to Ubuntu packages.