Failed to register rtcd client

Troubleshooting
1

Summary
Calls plugin not starting and log gives error “failed to register rtcd client”

Steps to reproduce
Deploy mattermost with mattermost-enterprice-edition-2.6.62.tgz
mattermost version: 10.1.0
Calls plugin: 1.1.0
deploy external rtcd service from container: v0.18.0

configure calls plugin:

rtcdserviceurl: “http://ip_removed:8443”

no other configurations for calls plugin.

Also tested with:
rtcd v0.17.0 and v0.15.0
mattermost: 9.11.1

Expected behavior
Calls plugin registers to rtcd service and users calls are directed to rtcd service

Observed behavior
Connection between mattermost and RTCD is ok, but when starting mattermost it get errors to server log. UDP and TCP 8443 is tested with curl and netcat that message goes trough

Error messages from mattermost logs
This plugin failed to start. failed to create rtcd manager: failed to register rtcd client: http request failed: Post “http://ip_removed:8443/register”: read tcp 10.42.8.138:40318->ip_removed:8443: read: connection reset by peer

Error message from RTCD log
warn [2024-10-18 08:53:07.559 Z] Buffer too small for first packet from ip_removed:58311: short buffer caller=“rtc/logger.go:78” origin=“ice/v2.(*TCPMuxDefault).handleConn github.com/pion/ice/v2@v2.3.25/tcp_mux.go:202”

Same error in rtcd if running with curl http://ip_removed:8443/register

2

It seems that registration is not done to port 8443 but 8045. So it looks like calls plugin is not supporting self registration at all, if using external rtcd. Or it requires some port forwarding in rtcd to forward 8443/tcp to 8045/tcp.

3

Hi @mikaheikkinen! It sounds like you’ve done some thorough troubleshooting already. Based on the error messages, it might be worth double-checking your RTCD service configuration and ensuring that the correct ports are open and forwarded as needed. You can find more information about configuring the Calls plugin and troubleshooting in the Mattermost Calls documentation. If the issue persists, consider opening a support ticket for more in-depth assistance. Hope this helps!

4

hi,

does RTCD/Calls plugin use 8443/tcp for somenting? If i forward 8443/tcp → 8045/tcp so that registration works, do I get other problems?

-Mika

5

IIRC rtcd will fall back to TCP if UDP isn’t available, but there’s a performance hit.

1 Like