Matrix RTC & Element Call Not Working

[SunnyBro1056]

Playbook Configuration:

My vars.yml file looks like this:

# --------  MATRIX SERVER FOR EXAMPLE.COM --------
#
#
matrix_homeserver_implementation: synapse


# -------- Networking --------
matrix_domain: example.com
matrix_homeserver_generic_secret_key: 'REDACTED'
matrix_playbook_reverse_proxy_type: playbook-managed-traefik
devture_systemd_docker_base_ipv6_enabled: true
matrix_static_files_container_labels_base_domain_enabled: true

# -------- Matrix Clients --------
matrix_client_element_enabled: true
matrix_client_element_default_theme: 'dark'
matrix_client_element_themes_enabled: true
matrix_client_element_default_country_code: "US"

cinny_enabled: true

# -------- Matrix Authentication Service (MAS) --------
matrix_authentication_service_enabled: true
matrix_authentication_service_config_secrets_encryption: 'REDACTED'


# -------- Voice Calls --------
matrix_element_call_enabled: true
matrix_synapse_allow_guest_access: false
livekit_server_config_logging_level: "debug"

# -------- Bridges To Other Platforms --------
matrix_appservice_double_puppet_enabled: true


matrix_mautrix_discord_enabled: true
matrix_mautrix_discord_configuration_extension_yaml:
  bridge:
    permissions:
      '@sunny:{{ example.com }}': admin

matrix_mautrix_meta_instagram_enabled: true  
matrix_mautrix_meta_instagram_configuration_extension_yaml:
  bridge:
    permissions:
      '@sunny:{{ example.com }}': admin
      
# -------- Administration Tools --------
matrix_element_admin_enabled: true
postgres_connection_password: 'REDACTED'

Matrix Server:

• OS: [Debian 12]
• Architecture [amd64]

Problem description:

I have enabled Element Call in my configuration, however, it still fails to work. Calls will default to legacy and I am not able to use the new voice rooms. I have completely let the playbook manage traefik, and serve the base domain. All other services in the playbook work perfectly.

I can confirm that I have opened the required ports. I have opened 7881/tcp, 7882/udp, 3479/udp, and 5350/tcp. I have also tried running the playbook with both matrix_rtc_enabled and matrix_element_call_enabled each enabled separately. Both attempts lead to the same result of Element Call not functioning.

Going to call.element.example.com also does nothing. I can confirm that I have correctly used the CNAME address in my DNS settings, the same way I have done for my other services such as Element and Cinny.

Additional context
I am hosting this server from a NAT. I am also using the playbook from the same machine I am hosting from. I have also added matrix.example.com and example.com to my /etc/hosts/ file under 127.0.0.1 because of my router not supporting NAT hairpin/loopback.

I have also gotten the output from journalctl -fu matrix-livekit-server. I have redacted my public IPv4.

journalctl -fu matrix-livekit-server
Feb 23 16:39:06 debian-server matrix-livekit-server[2779686]: 2026-02-24T00:39:06.929Z        DEBUG        livekit        rtcconfig/ip.go:252        error reading from UDP socket        {"err": "read udp 172.24.0.4:7882: use of closed network connection"}
Feb 23 16:39:06 debian-server matrix-livekit-server[2779686]: 2026-02-24T00:39:06.929Z        WARN        livekit        rtcconfig/ip.go:278        could not validate external IP        {"ip": "PUBLIC_IPV4", "from": "172.22.0.4:7882", "error": "context canceled"}
Feb 23 16:39:06 debian-server matrix-livekit-server[2779686]: 2026-02-24T00:39:06.929Z        DEBUG        livekit        rtcconfig/ip.go:252        error reading from UDP socket        {"err": "read udp 172.22.0.4:7882: use of closed network connection"}
Feb 23 16:39:06 debian-server matrix-livekit-server[2779686]: 2026-02-24T00:39:06.960Z        INFO        livekit        rtcconfig/webrtc_config.go:284        failed to get external ip        {"local": "172.24.0.4", "err": "context canceled"}
Feb 23 16:39:06 debian-server matrix-livekit-server[2779686]: 2026-02-24T00:39:06.960Z        INFO        livekit        rtcconfig/webrtc_config.go:284        failed to get external ip        {"local": "172.22.0.4", "err": "context canceled"}
Feb 23 16:39:06 debian-server matrix-livekit-server[2779686]: 2026-02-24T00:39:06.960Z        INFO        livekit        rtcconfig/webrtc_config.go:99        no external IPs found, using node IP for NAT1To1Ips        {"ip": "PUBLIC_IPV4"}
Feb 23 16:39:06 debian-server matrix-livekit-server[2779686]: 2026-02-24T00:39:06.960Z        DEBUG        livekit        rtcconfig/rtc_unix.go:35        UDP receive buffer size        {"current": 15000000}
Feb 23 16:39:06 debian-server matrix-livekit-server[2779686]: 2026-02-24T00:39:06.961Z        INFO        livekit        service/turn.go:145        Starting TURN server        {"turn.relay_range_start": 30000, "turn.relay_range_end": 40000, "turn.portTLS": 5350, "turn.externalTLS": true, "turn.portUDP": 3479}
Feb 23 16:39:06 debian-server matrix-livekit-server[2779686]: 2026-02-24T00:39:06.964Z        INFO        livekit        service/server.go:264        starting LiveKit server        {"portHttp": 7880, "nodeID": "ND_9FqrHUwkvyXS", "nodeIP": "PUBLIC_IPV4", "version": "1.9.11", "bindAddresses": ["::"], "rtc.portTCP": 7881, "rtc.portUDP": {"Start":7882,"End":0}}
Feb 23 16:39:06 debian-server matrix-livekit-server[2779686]: 2026-02-24T00:39:06.964Z        DEBUG        livekit        service/signal.go:119        starting relay signal server        {"topic": "ND_9FqrHUwkvyXS"}

I have also tried removing my /etc/hosts entries. I restarted the entire playbook with just setup-all and ran journalctl -fu matrix-livekit-server again.

journalctl -fu matrix-livekit-server
Feb 23 17:55:16 debian-server matrix-livekit-server[2906261]: 2026-02-24T01:55:16.437Z        DEBUG        livekit        rtcconfig/ip.go:252        error reading from UDP socket        {"err": "read udp 172.22.0.2:7882: use of closed network connection"}
Feb 23 17:55:16 debian-server matrix-livekit-server[2906261]: 2026-02-24T01:55:16.438Z        WARN        livekit        rtcconfig/ip.go:278        could not validate external IP        {"ip": "PUBLIC_IPv4", "from": "172.24.0.4:7882", "error": "context canceled"}
Feb 23 17:55:16 debian-server matrix-livekit-server[2906261]: 2026-02-24T01:55:16.438Z        DEBUG        livekit        rtcconfig/ip.go:252        error reading from UDP socket        {"err": "read udp 172.24.0.4:7882: use of closed network connection"}
Feb 23 17:55:16 debian-server matrix-livekit-server[2906261]: 2026-02-24T01:55:16.481Z        INFO        livekit        rtcconfig/webrtc_config.go:284        failed to get external ip        {"local": "172.24.0.4", "err": "context canceled"}
Feb 23 17:55:16 debian-server matrix-livekit-server[2906261]: 2026-02-24T01:55:16.481Z        INFO        livekit        rtcconfig/webrtc_config.go:284        failed to get external ip        {"local": "172.22.0.2", "err": "context canceled"}
Feb 23 17:55:16 debian-server matrix-livekit-server[2906261]: 2026-02-24T01:55:16.481Z        INFO        livekit        rtcconfig/webrtc_config.go:99        no external IPs found, using node IP for NAT1To1Ips        {"ip": "PUBLIC_IPv4"}
Feb 23 17:55:16 debian-server matrix-livekit-server[2906261]: 2026-02-24T01:55:16.481Z        DEBUG        livekit        rtcconfig/rtc_unix.go:35        UDP receive buffer size        {"current": 15000000}
Feb 23 17:55:16 debian-server matrix-livekit-server[2906261]: 2026-02-24T01:55:16.482Z        INFO        livekit        service/turn.go:145        Starting TURN server        {"turn.relay_range_start": 30000, "turn.relay_range_end": 40000, "turn.portTLS": 5350, "turn.externalTLS": true, "turn.portUDP": 3479}
Feb 23 17:55:16 debian-server matrix-livekit-server[2906261]: 2026-02-24T01:55:16.482Z        INFO        livekit        service/server.go:264        starting LiveKit server        {"portHttp": 7880, "nodeID": "ND_mhVNhrzPQTLk", "nodeIP": "PUBLIC_IPv4", "version": "1.9.11", "bindAddresses": ["::"], "rtc.portTCP": 7881, "rtc.portUDP": {"Start":7882,"End":0}}
Feb 23 17:55:16 debian-server matrix-livekit-server[2906261]: 2026-02-24T01:55:16.482Z        DEBUG        livekit        service/signal.go:119        starting relay signal server        {"topic": "ND_mhVNhrzPQTLk"}

[SunnyBro1056]

After explicitly setting this in my vars.yml I seemed to have a better output:

livekit_server_config_rtc_use_external_ip: false
livekit_server_config_rtc_node_ip: PUBLIC_IPv4

This was my result:

journalctl -fu matrix-livekit-server
Feb 23 18:09:47 debian-server systemd[1]: matrix-livekit-server.service: Deactivated successfully.
Feb 23 18:09:47 debian-server systemd[1]: Stopped matrix-livekit-server.service - LiveKit Server.
Feb 23 18:09:47 debian-server systemd[1]: Starting matrix-livekit-server.service - LiveKit Server...
Feb 23 18:09:47 debian-server matrix-livekit-server[2940136]: 438ae21de94fd4fbcd8c2fd0f8a2a2c86754bd9241683083d6936e500771b98a
Feb 23 18:09:47 debian-server systemd[1]: Started matrix-livekit-server.service - LiveKit Server.
Feb 23 18:09:48 debian-server matrix-livekit-server[2940158]: 2026-02-24T02:09:48.825Z        INFO        livekit        routing/interfaces.go:180        using single-node routing
Feb 23 18:09:48 debian-server matrix-livekit-server[2940158]: 2026-02-24T02:09:48.826Z        DEBUG        livekit        rtcconfig/rtc_unix.go:35        UDP receive buffer size        {"current": 15000000}
Feb 23 18:09:48 debian-server matrix-livekit-server[2940158]: 2026-02-24T02:09:48.827Z        INFO        livekit        service/turn.go:145        Starting TURN server        {"turn.relay_range_start": 30000, "turn.relay_range_end": 40000, "turn.portTLS": 5350, "turn.externalTLS": true, "turn.portUDP": 3479}
Feb 23 18:09:48 debian-server matrix-livekit-server[2940158]: 2026-02-24T02:09:48.827Z        INFO        livekit        service/server.go:264        starting LiveKit server        {"portHttp": 7880, "nodeID": "ND_qkoQTEzTwEHp", "nodeIP": "PUBLIC_IPv4", "version": "1.9.11", "bindAddresses": ["::"], "rtc.portTCP": 7881, "rtc.portUDP": {"Start":7882,"End":0}}
Feb 23 18:09:48 debian-server matrix-livekit-server[2940158]: 2026-02-24T02:09:48.828Z        DEBUG        livekit        service/signal.go:119        starting relay signal server        {"topic": "ND_qkoQTEzTwEHp"}

Element Call still remains unsuccessful, along with the call.element.domain.com service.

I attempted to start a call through Element Call, and this is what comes through the logs from journalctl -fu matrix-livekit-jwt-service:

journalctl -fu matrix-livekit-jwt-service
Feb 23 18:22:59 debian-server matrix-livekit-jwt-service[2939969]: 2026/02/24 02:22:59 Processing legacy SFU request
Feb 23 18:23:03 debian-server matrix-livekit-jwt-service[2939969]: 2026/02/24 02:23:03 Request from 172.24.0.5:55072 at "https://element.example.com"
Feb 23 18:23:03 debian-server matrix-livekit-jwt-service[2939969]: 2026/02/24 02:23:03 Processing legacy SFU request
Feb 23 18:23:29 debian-server matrix-livekit-jwt-service[2939969]: 2026/02/24 02:23:29 Failed to look up user info: Get "matrix://example.com/_matrix/federation/v1/openid/userinfo?access_token=TOKEN_REDACTED": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Feb 23 18:23:29 debian-server matrix-livekit-jwt-service[2939969]: 2026/02/24 02:23:29 Error processing request: Failed to look up user info from homeserver

[unbekannt3]

Had the same a while ago, can't remember the exact details how i've come around this but you could try adding something like this to your vars.yml:

matrix_livekit_jwt_service_container_extra_arguments:
  - "--add-host=example.com:{{ matrix_synapse_container_ip | default('172.17.0.1') }}"

[thedestroyer4312]

Also having a similar issue to you, element X does not work at all for me, just get a black screen. Element call does seem to work on the web app for me though (through app.element.io as I'm not self-hosting the frontend).

Not sure what to do, wish setting this up wasn't such a hassle...

[MechaFizz]

I am also now having this issue. I had it working at one point with only 'matrix_rtc_enabled: true', but since updating and moving to new hardware, I can't seem to get the same configuration to work anymore. I've tried the above suggestions, but to no resolve. I'm really lost at this point.

[Taylory774]

element call is working, calls are coming. But mistakes bother me. I don't know what to fix or where to fix it. This configuration is only for calls:

matrix_element_call_enabled: true
matrix_element_call_hostname: call.site.com
matrix_synapse_allow_guest_access: false
livekit_server_config_logging_level: "error"

The errors themselves when loading:

TASK [custom/matrix-element-call : Fail if Element Call architecture is not supported]
TASK [galaxy/livekit_server : Fail if LiveKit Server port range configuration is invalid]
TASK [galaxy/livekit_server : Fail if LiveKit TURN relay range configuration is invalid]
TASK [galaxy/livekit_server : Fail if LiveKit Server logging level is invalid]

[thedestroyer4312]

element call is working, calls are coming. But mistakes bother me. I don't know what to fix or where to fix it. This configuration is only for calls:

matrix_element_call_enabled: true
matrix_element_call_hostname: call.site.com
matrix_synapse_allow_guest_access: false
livekit_server_config_logging_level: "error"

The errors themselves when loading:

TASK [custom/matrix-element-call : Fail if Element Call architecture is not supported]
TASK [galaxy/livekit_server : Fail if LiveKit Server port range configuration is invalid]
TASK [galaxy/livekit_server : Fail if LiveKit TURN relay range configuration is invalid]
TASK [galaxy/livekit_server : Fail if LiveKit Server logging level is invalid]

Did you open 30000-30020/udp? https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-livekit-server.md

TURN error in logs likely indicates something to do with that

[Taylory774]

element call is working, calls are coming. But mistakes bother me. I don't know what to fix or where to fix it. This configuration is only for calls:

matrix_element_call_enabled: true
matrix_element_call_hostname: call.site.com
matrix_synapse_allow_guest_access: false
livekit_server_config_logging_level: "error"

The errors themselves when loading:

TASK [custom/matrix-element-call : Fail if Element Call architecture is not supported]
TASK [galaxy/livekit_server : Fail if LiveKit Server port range configuration is invalid]
TASK [galaxy/livekit_server : Fail if LiveKit TURN relay range configuration is invalid]
TASK [galaxy/livekit_server : Fail if LiveKit Server logging level is invalid]

Did you open 30000-30020/udp? https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-livekit-server.md

TURN error in logs likely indicates something to do with that

ufw allow 7881/tcp
ufw allow 7882/udp
ufw allow 3479/udp
ufw allow 5350/tcp
ufw allow 30000:30020/udp

Keenetic router has internet ports open:

7881/tcp
30000-30020/udp

but I didn't set up this configuration, by default.:

livekit_server_config_turn_external_tls: true
livekit_server_container_labels_turn_traefik_enabled: true
livekit_server_container_labels_turn_traefik_entrypoints: "<your-livekit-turn-traffic-entrypoint>"

OS debian 13

[kovacs-andras]

Same problem here, tried clean install multiple times with/without a subdomain, etc.