Arch Linux User Repository

If you update from an old version, be sure you follow the new place of the config. This is now placed in /etc/webapps/jitsi-meet /etc/jicofo /etc/jitsi-videobridge

And prosody config need to be update also.

They are some examples in the doc directory.

Can you try this tutorial:

https://blog.celogeek.com/posts/linux/archlinux/2020-06-jitsi-meet-on-arch-linux/

Also, check the inspector in your browser to see the error exactly.

I, for the life of me, can not seem to get this to work. I had it working a few version ago, but now whenever another device connects to the room, the room crashes and says "unfortunately something went wrong." I clean uninstalled everything, and reinstalled, following the Arch Wiki exactly, and then I followed the Jitsi self hosting manual, still the same results.

Again, just trying to get a default setup working. I even waiting for a bin update, to see if it was just this version having problems, but no.

Logs are also not giving me helpful solutions either.

Is anyone else having this struggle getting a basic setup working?

Done

We make the nightly and the stable look alike. The config path now for jitsi-meet is /etc/webapps/jitsi-meet (more like arch path)

@C0rn3j, would you mind updating? version 1.0.4289 is available.

@quartic would you mind updating the package?

Version 1.0.4127 is available.

Hi,

This package is late We can have a latest release by checking:

curl --silent "https://api.github.com/repos/jitsi/jitsi-meet/releases/latest" | jq -r .name
1.0.4074

I have do a change to automatically take it from this take and auto update the pkgver on the fly.

Here my PKGBUILD

_pkgname=jitsi-meet
pkgname=${_pkgname}-bin
pkgver=1.0.4074
pkgrel=1
_debrel=1
pkgdesc="WebRTC JavaScript video conferences"
arch=('any')
url="https://jitsi.org/jitsi-meet/"
license=('Apache')
depends=()
optdepends=('jicofo'
            'jitsi-videobridge'
            'nginx'
            'prosody')
conflicts=(${_pkgname})
provides=(${_pkgname})
makedepends=('binutils' 'tar')
options=('!strip')
backup=('etc/jitsi/meet/config.js'
        'etc/jitsi/meet/interface_config.js'
        'etc/jitsi/meet/logging_config.js')

source=()
noextract=()
pkgver() {
  curl --silent "https://api.github.com/repos/jitsi/$_pkgname/releases/latest" | jq -r .name
}
build() {
  curl -L "https://download.jitsi.org/stable/${pkgname}-web${pkgver}-${debrel}_all.deb" -o web.deb
  curl -L "https://download.jitsi.org/stable/${_pkgname}-web-config${pkgver}-${_debrel}_all.deb" -o config.deb
  mkdir -p config
  ar p "config.deb" data.tar.xz | tar -xJvC config
  sed -i 's/jitsi-meet.example.com-config.js/config.js/g' config/usr/share/jitsi-meet-web-config/jitsi-meet.example{,-apache}
}
package() {
  ar p "${srcdir}/web.deb" data.tar.xz | tar xJv -C "${pkgdir}"
rm -r "${pkgdir}/usr/share/doc"
install -Dm644 "${srcdir}/config/usr/share/jitsi-meet-web-config/config.js" "${pkgdir}/etc/jitsi/meet/config.js"
  mv "${pkgdir}/usr/share/jitsi-meet/interface_config.js" "${pkgdir}/etc/jitsi/meet/interface_config.js"
  mv "${pkgdir}/usr/share/jitsi-meet/logging_config.js" "${pkgdir}/etc/jitsi/meet/logging_config.js"
  ln -s '/etc/jitsi/meet/config.js' "${pkgdir}/usr/share/jitsi-meet/config.js"
  ln -s '/etc/jitsi/meet/interface_config.js' "${pkgdir}/usr/share/jitsi-meet/interface_config.js"
  ln -s '/etc/jitsi/meet/logging_config.js' "${pkgdir}/usr/share/jitsi-meet/logging_config.js"
install -Dm644 "${srcdir}/config/usr/share/jitsi-meet-web-config/jitsi-meet.example" "${pkgdir}/usr/share/doc/jitsi-meet/nginx.conf.example"
  install -Dm644 "${srcdir}/config/usr/share/jitsi-meet-web-config/jitsi-meet.example-apache" "${pkgdir}/usr/share/doc/jitsi-meet/apache.conf.example"
}
vim: set ts=2 sw=2 et:

Hope that can help

@quartic That makes sense, thank you very much!

@carlenny You are right that jicofo is required to have a working jitsi-meet system. However, it is marked as optional for this package as you could have jicofo running on another server. The same goes for jitsi-videobridge and prosody.

Is jicofo (the conference focus component) really optional? I can't get jitsi-meet working without it at the moment.