Manually adding ingress rules for /.well-known/matrix/client to matrix-well-known ingress rule set seems to have fixed the issue (pending further testing). Also, the router ports for this service were incorrectly configured to 30881 and 30882 instead of 30001 and 30002.
Manually adding ingress rules for `/.well-known/matrix/client` to `matrix-well-known` ingress rule set seems to have fixed the issue (pending further testing). Also, the router ports for this service were incorrectly configured to 30881 and 30882 instead of 30001 and 30002.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
MatrixRTC server logs report the following:
Legacy calls are now supported through Coturn. This issue will remain open for MatrixRTC.
Manually adding ingress rules for
/.well-known/matrix/clienttomatrix-well-knowningress rule set seems to have fixed the issue (pending further testing). Also, the router ports for this service were incorrectly configured to 30881 and 30882 instead of 30001 and 30002.https://github.com/element-hq/ess-helm/issues/711
https://fariszr.com/matrix-rtc-setup-with-docker-caddy/
Tested last night - MatrixRTC is now working.