Slavi Pantaleev

Despite you enabling the Matrix RTC stack (or Element Call, which auto-enables the Matrix RTC stack), your `/.well-known/matrix/client` file **on the base domain** is outdated and doesn't include the new...

See if redirects are involved when serving the file. Check CORS headers.

How do you reproduce it? The nameserver in the `matrix-synapse` container (`cat /etc/resolv.conf`) is Docker's internal DNS (`127.0.0.11`), which does match the first entry (`'127.0.0.0/8'`) in `ip_range_blacklist`.

That go-neb problem is interesting. The same should happen if you try to message any other user (or bridge) on your homeserver, right? Yet, we don't have failure on such...

It seems like lifecycle hooks don't solve the problem for me as well. However, the solution proposed by @bradib0y does work. ----- In my environment, only the data-plane was dying,...

There have been others (see https://github.com/mother-of-all-self-hosting/mash-playbook/issues/247) reporting that 6.3.4 does not run on some CPUs (missing some instructions). Downgrading to 6.3.3 resolves the issue. KeyDB was chosen as a popular...

Some feedback on the role: - the "Project source code URL" in `defaults/main.yml` is incorrect - `defaults/main.yml` mentions "node_exporter" / "node exporter" in multiple places - if the role only...

The documentation page mentions `cadvisor_hostname`, but group vars are auto-setting `cadvisor_container_labels_metrics_hostname` directly. This is probably a bit odd. For other roles, we do it like this, because the main hostname...

Docker probably doesn't play well with nftables. Consider installing iptables-legacy instead and see if that makes things better.

I do not see this on my setup, but I'm probably running much fewer additional Nextcloud apps than you are, which means fewer PHP files in my setup. It's probably...