Jitsi Meet on NS8

Development
1

Hi all,
has anyone ever managed to setup jitsi meet on ns8 via podman container?

2

There’s a gist by @davidep: Jitsi with Podman 2.2.1 · GitHub

I’m going to test it…

2 Likes
3

I found it but the link (http://tendie.haus/how-to-setup-a-basic-jitsi-instance-with-podman/) doesn’t work…

4

I think the link is not needed, all important info is in the gist.
I already got a working version where at least jitsiweb is reachable and a conference can be started, I hope to release a testing version asap.

5

When I tried, JVB was not working. I have some cloud machine with real DNS, if u want to share me something I can do some test. :slight_smile:

1 Like
6

Thanks @federico.ballarini for testing, hopefully you’ve got more luck…

The containers are running but I can’t start a conference because I get following error:

[error] 308#308: *2 xmpp.meet.jitsi could not be resolved (3: Host not found)

I think it’s just about setting real names according to DNS but I’m not sure…

To install:

add-module ghcr.io/mrmarkuz/jitsi:latest

To edit variables:

runagent -m jitsi1 nano ../actions/configure-module/10configure_environment_vars

To apply the changes, just click in “Save” the NS8 Jitsi app settings which writes the config and restarts the services.

It’s also possible to edit jitsi.env directly and restart the jitsi service but it will be overwritten by next “Save”.

Some service FQDNs are also used in the jitsi.service file, to edit:

systemctl --user edit --full jitsi

2 Likes
7

Same result here: also with public DNS when starts the meeting the system return an error.

1 Like
8

Thanks for testing.
I’m going to recheck…when I got something working I’ll report and update the app.

EDIT:

When providing a DNS wildcard entry for the pseudo names *.meet.jitsi on my DNS server (NethSec), I could join a conference.

There must be some difference to docker as regards DNS, I need to check. Usually the hosts file works to access other containers by name but jitsi does some DNS check. Maybe it could be disabled.
To be continued…

EDIT:

@federico.ballarini I think I got something. At least I could start a conference between PC and mobile phone and audio/video were working.
The default rootless podman network has dns disabled, therefore the internal names couldn’t be resolved and we got the error.
Now the jitsi service creates a new network (which has dns enabled by default) “meet.jitsi” using the same network alias. The containers are started using the new network and the prosody container adds its internal network alias “xmpp.meet.jitsi”.
The web container runs in the default podman network to be available to traefik.

To update:

api-cli run update-module --data '{"module_url":"ghcr.io/mrmarkuz/jitsi:1.0.0-dev.1","instances":["jitsi1"],"force":true}'

Todos:

  • Authentication
  • LDAP/AD
  • Performance settings
4 Likes
9

I’ll test it asap. Thank you :slight_smile:

1 Like
10

Hi @mrmarkuz, it seems there is a problem with the videobridge when you connect more than 2 people. (If there are only 2 people connected Jitsi uses P2P)

1 Like
11

Thanks for testing, did you test it on a cloud machine or on a server in the LAN?
I tested in the LAN and was able to have a conference between PC, laptop and mobile.

1 Like
12

On a Cloud machine

1 Like
13

I’m going to test it asap…

1 Like