Remove .well-known transport discovery - #4153
Merged
Merged
Conversation
…ove_well_known_fallback
robintown
marked this pull request as ready for review
August 10, 2026 13:16
robintown
changed the base branch from
valere/widget_rtc_transport_action
to
livekit
August 11, 2026 10:02
robintown
approved these changes
Aug 11, 2026
robintown
enabled auto-merge
August 11, 2026 10:07
w1erley
added a commit
to eledrone/eledrone-call
that referenced
this pull request
Aug 12, 2026
Transport discovery used to be three steps - the MSC4143 transports endpoint, then .well-known, then app config. Upstream removed the middle one (element-hq#4153), and that middle one is the only one eledrone had: Dendrite answers 404 for the endpoint, and the SFU is advertised in .well-known. With the fallback gone there is nowhere left to find a transport, so no call connects at all. This is why calls broke the moment the app started embedding a widget built from this fork rather than the released 0.22.0 package - the release still has the .well-known step. The URL is the one .well-known already advertises. Remove this once the homeserver implements the transports endpoint, which is where upstream is going. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
w1erley
added a commit
to eledrone/eledrone-web
that referenced
this pull request
Aug 12, 2026
Calls stopped connecting the moment the app started embedding a widget built from our own fork rather than the released 0.22.0 package. Element Call finds its SFU by trying, in order: the MSC4143 transports endpoint, .well-known, then its own config. Upstream removed the .well-known step (element-hq/element-call#4153), and that step was the only one that worked here - Dendrite answers 404 for the transports endpoint, and the SFU is advertised in .well-known. So the fork's build had nowhere left to look while 0.22.0 still did. eledrone-call now puts livekit_service_url in the widget's own config.json, which is the surviving step. This picks that build up. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Blocked because depends on: #4135
Breaking for widget host that don't support MSC4515
Content
Motivation and context
Screenshots / GIFs
Tests
Checklist