Voice/video calls fail to connect #2

Closed
opened 2025-05-27 02:17:23 +00:00 by eric · 4 comments
Owner

MatrixRTC server logs report the following:

ERROR   livekit service/signal.go:188   could not handle new participant
MatrixRTC server logs report the following: ``` ERROR livekit service/signal.go:188 could not handle new participant ```
Author
Owner

Legacy calls are now supported through Coturn. This issue will remain open for MatrixRTC.

Legacy calls are now supported through Coturn. This issue will remain open for MatrixRTC.
Author
Owner

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.
Author
Owner
https://github.com/element-hq/ess-helm/issues/711 https://fariszr.com/matrix-rtc-setup-with-docker-caddy/
Author
Owner

Tested last night - MatrixRTC is now working.

Tested last night - MatrixRTC is now working.
eric closed this issue 2026-06-10 12:46:48 +00:00
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DevOps/ansible-role-matrix-stack#2