Repository navigation
fix(jitsi): use container HTTPS port 8443 so domain binding works - #2310
Merged
Merged
Conversation
The jitsi/web container listens on 8000 (HTTP) and 8443 (HTTPS) only, but the package declared W9_HTTPS_PORT=443. The Websoft9 gateway uses W9_HTTPS_PORT as the reverse-proxy forward port when a domain is bound, so bound domains were proxied to a closed container port and the browser hit Jitsi's "Uh oh! We couldn't fully download everything we needed" fallback page while loading /libs/*.js. - Set W9_HTTPS_PORT=8443 to match the real container listener. - Correct the domain guide: PUBLIC_URL is https://<your-domain> when the app is reached through a bound domain.
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.
Problem
Binding a domain to Jitsi returned a broken page:
Uh oh! We couldn't fully download everything we needed :(/Missing https://<domain>/libs/lib-jitsi-meet.min.js?v=9442Accessing the app through its published port worked; accessing it through a bound domain did not.
Root cause
apps/jitsi/.envdeclaredW9_HTTPS_PORT=443, but thejitsi/webimage only listens on8000(HTTP) and8443(HTTPS).The Websoft9 gateway uses
W9_HTTPS_PORTas the reverse-proxy forward port when a domain is bound, so bound domains were forwarded tohttps://<app>:443— a port with no listener, and the critical/libs/*.jsrequests failed.Verification
docker run --env-file .env ghcr.io/jitsi/web:stable-11248: listeners are:8000and:8443only;https://127.0.0.1:443is refused./libs/lib-jitsi-meet.min.js?v=9442→200, 1,138,812 bytes;/,/css/all.css,/libs/app.bundle.min.js,/config.js→200.proxy_pass $forward_scheme://$server:$port$request_uriwithset $port 8443) returns200for every critical asset.W9_HTTPS_PORT=8443restored domain access.Changes
.env:W9_HTTPS_PORT=443→8443.README.md: the domain guide now statesPUBLIC_URLishttps://<your-domain>for a bound domain.CHANGELOG.md: entry for the fix.Note
For existing installations the new port only reaches the existing proxy host after a redeploy (the platform re-syncs proxy ports on redeploy) or after re-creating the domain binding; re-binding a domain alone keeps the old forward port.