From 9afe5f6bed690314c1fb49ae8578d3f3ca4324bb Mon Sep 17 00:00:00 2001 From: stratself Date: Sun, 22 Feb 2026 22:18:39 +0000 Subject: [PATCH] docs: add caveat for deployment with non-federated instances --- docs/calls/livekit.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/calls/livekit.mdx b/docs/calls/livekit.mdx index 5f0f29839..c71fc9578 100644 --- a/docs/calls/livekit.mdx +++ b/docs/calls/livekit.mdx @@ -277,6 +277,10 @@ curl -X POST -d @payload.json https://livekit.example.com/get_token The JWT service will respond with a `jwt` token. Use this token to test at the [LiveKit Connection Tester](https://livekit.io/connection-test) - if everything works there, then you have set up LiveKit successfully! +## Caveats + +When deploying on servers with disabled federation (`enable_registration = false`), Livekit will fail as it can't fetch the required [OpenID endpoint](https://spec.matrix.org/v1.17/server-server-api/#get_matrixfederationv1openiduserinfo) via federation paths. You can find a workaround for this limitation [here](https://forgejo.ellis.link/continuwuation/continuwuity/issues/1440). + ## Related Documentation Guides: @@ -295,5 +299,3 @@ Source codes: - [Element Call](https://github.com/element-hq/element-call) - [lk-jwt-service](https://github.com/element-hq/lk-jwt-service) - [LiveKit server](https://github.com/livekit/livekit) - -