I am accessing my jitsi domain via webbrowser and in the preview screen everything seems fine, but when I click "join conference" nothing happens. After a few seconds I get an error saying "your connection was terminated. A new attempt will be started in 30 seconds".

Fix
https://community.jitsi.org/t/jitsi-meet-in-docker-container-websocket-error/88703/15

I am accessing my jitsi domain via webbrowser and in the preview screen everything seems fine, but when I click "join conference" nothing happens. After a few seconds I get an error saying "your connection was terminated. A new attempt will be started in 30 seconds".

Fix
https://community.jitsi.org/t/jitsi-meet-in-docker-container-websocket-error/88703/15

4.95-r0-1 was problematic, because `/etc/exim/exim.conf` in the
container had the wrong permissions (writable by the `exim` user).

Fixed in 697f3cff7e
which is built as 4.95-r0-2

4.95-r0-1 is the first container image tag that is available as a multi-arch image
with support for linux/amd64, linux/arm64/v8 (arm64) and linux/arm/v7 (arm32),
so self-building is no longer necessary on all these platforms.

2.2.3 is the first container image tag that is available as a multi-arch image
with support for linux/amd64, linux/arm64/v8 (arm64) and linux/arm/v7 (arm32),
so self-building is no longer necessary on all these platforms.

Not tested but shouldn't break something

The OAuth credentials method seems to be the only viable way to
configure the mx-puppet-bridge now. Legacy tokens can no longer be
created, and the other methods (xoxs and xoxc tokens) come with warnings
about them being against Slack's terms of service.

(untested change, but unlikely to cause breakage)

Synapse v1.51.0 requires to be built with BuildKit since
https://github.com/matrix-org/synapse/pull/11691

The `docker_image` Ansible module does not support BuildKit
(https://github.com/ansible-collections/community.general/issues/514),
so we had to switch to a `docker build` call.

Fixes a issue with room version 1.

Merging has to wait until ARM images are built ofc.

using b33ea48

v1.50.0 was found to be buggy for people using a `webclient` listener.
This is fixed in v1.50.1.

We don't use such a listener, so we weren't affected anyway.