From ArchWiki
Latest comment: 19 March 2023 by Celogeek in topic authentication fails

New paths to config files?

I get the impression that the paths to many of the config files have changed? I am installing the bin suite. However since I don't fully understand and have not succeeded myself I don't want to edit directly.

E.g. I think /etc/jitsi-videobridge/jitsi-videobridge.conf -> /etc/jitsi/videobridge/config, /opt/jitsi-videobridge/ -> /usr/share/jitsi-videobridge, /etc/jicofo/jicofo.conf -> /etc/jitsi/jicofo/config -- Eothred (talk) 15:47, 19 April 2020

Paths have not changed, please read the Jitsi-meet#Installation section. But yeah, the configuration part of the article is not complete at this moment. -- SlavMetal (talk) 14:15, 19 April 2020 (UTC)Reply
In the stable packages, the videobridge configuration is still named config. Maybe only jitsi-videobridge-git has been updated. Kauron (talk) 22:07, 22 February 2021 (UTC)Reply
I maintain the packages for stable bin, nightly and nightly-bin. All of them works the same way, with more an Arch way to organize the file (/etc/jicofo, /etc/jitsi-videobridge, /etc/webapps/jitsi-meet, and docs in /usr/share/doc/jitsi-meet-*). The only remaining one was the stable one (not the bin one). I'm now the maintainer of this one too, and I would like to align this package so we can have 1 docs that works for the stable package. The nightly have new stuff and different path (-nightly), so probably just add a note for that too. I made a complete accurate blog post for the stable bin here: and here for the nightly: Can I update the path of the stable packages and also update the wiki with every information I have in my blog to properly set jitsi on arch (and add it as a source if possible)? Celogeek (talk) 23:12, 7 April 2021 (UTC)Reply

JVB2 config

Migration to Jitsi videobridge 2 (in the stable jitsi-videobridge package) has not been smooth for me. Did anyone get a working config with that? Fordprefect (talk) 09:11, 14 May 2020 (UTC)Reply

Rewrite guide to match new version of jitsi-meet (stable, stable-bin, nightly, nightly-bin, git)

I realign all jitsi-meet packages to match Arch paths, and in order to have only 1 wiki that can applied to all of them.

The configs is placed under /etc:

- /etc/jicofo
- /etc/jicofo-nightly
- /etc/jicofo-git
- /etc/jitsi-videobridge
- /etc/jitsi-videobridge-nightly
- /etc/jitsi-videobridge-git

The webapps config are placed under /etc/webapps:

- /etc/webapps/jitsi-meet
- /etc/webapps/jitsi-meet-nightly
- /etc/webapps/jitsi-meet-git

The websites are placed under /usr/share/webapps:

- /usr/share/webapps/jitsi-meet
- /usr/share/webapps/jitsi-meet-nightly
- /usr/share/webapps/jitsi-meet-git

I made already a complete and accurate guide for Arch for the package I maintained: stable-bin, nightly and nightly-bin Now I maintain them all, so I will update the wiki with all this information here.

Celogeek (talk) 14:32, 10 April 2021 (UTC)Reply

authentication fails

If I modify the authentication in /etc/prosody/conf.d/jitsi.cfg.lua to

VirtualHost "auth.JITSIFQDN"
authentication = "internal_plain"

as suggested by the wiki then jitsi-videobridge cannot authenticate. If instead I leave it at

authentication = "internal_hashed"

it works. Is this a mistake in the wiki?

Juw (talk) 17:55, 12 March 2023 (UTC)Reply

If you change the authentication method after save a password, then it's not reconize anymore, you have to set it again so it can write into the right format.

Celogeek (talk) 18:38, 14 March 2023 (UTC)Reply

Thank you for your help. I changed it to authentication = "internal_plain" and then reran the prosodyctl register … and prosodyctl mod_roster_command … and now it works, it seems it has now overwritten the user credentials to now be stored in pain authentication. I am wondering though, what is the purpose of instructing

authentication = "internal_plain"

in the guide, instead of leaving it to "internal_hashed"?

Juw (talk) 10:35, 15 March 2023 (UTC)Reply

Few years ago, the setup for password was like that. They change it and support hashing now. I need to update the wiki and blog to use this new authentication method. I will check this week end and do updates if everything works properly.

You can try setting internal_hashed instead of internal_plain in prosody and register your password again to update the files. Restart everything and check if that's ok.

Celogeek (talk) 11:25, 15 March 2023 (UTC)Reply

It works for me either way. It also works if I omit the line completely. In /etc/prosody/prosody.cfg.lua it already sets it to internal_hashed, I assume this is what is used then?

Juw (talk) 11:33, 15 March 2023 (UTC)Reply

I have update the authentication. So internal_plain should be internal_hashed, and anonymous should be jitsi-anonymous. I test it and also compare with the debian version.

Celogeek (talk) 12:06, 19 March 2023 (UTC)Reply


Is YOUR_DOMAIN supposed to be the same as JITSIFQDN?

Juw (talk) 17:54, 12 March 2023 (UTC)Reply

Yes. I've fixed the wiki.

Celogeek (talk) 18:38, 14 March 2023 (UTC)Reply