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