I've stumbled through getting a synapse server up and running with mas connecting to my authentik server behind nginx using docker compose.
Now I want to get element-call up and running, and I can't for the life of me figure out the .well-known file shenanigans.
As I understand it, MAS and synapse know about each other and are serving the file for me, but element-call doesn't talk the same way? If it does, I haven't figured out the incantation to get RTC added to it.
Another related question, do I need the jwt layer even though I'm using MAS, the matrix authentication service?
3 Comments
ohshit604@sh.itjust.works · 2 pts · 204d
2 months late but if you have Element Call questions still I can try to help you through it! Certainly was a PIA when I configured mine.
Tolookah@discuss.tchncs.de · 1 pts · 204d
I eventually got it, with hello from the matrix channels (so I have an account at matrix.org just for super to get my server up. They were great there, very patient
Thanks though!
Tolookah@discuss.tchncs.de · 1 pts · 275d
I figured the well-known part out myself eventually, and for the next one through here: in homeserver.yaml, adding extra_well_known_client_content: org.matrix.msc4143.rtc_foci: [{"type": "livekit", "livekit_service_url": "https://livekit.domain.com/"}]
Added it to the generated well-known/matrix/client.
Still don't know about jwt vs mas, maybe I'll figure that out today