Skip to content

fix(jitsi): use container HTTPS port 8443 so domain binding works - #2310

Merged
zhaojing1987 merged 1 commit into
mainfrom
fix/jitsi-internal-https-port
Nov 17, 2026
Merged

zhaojing1987 merged 1 commit into
mainfrom
fix/jitsi-internal-https-port

Conversation

@zhaojing1987

Copy link
Copy Markdown
Collaborator

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=9442

Accessing the app through its published port worked; accessing it through a bound domain did not.

Root cause

apps/jitsi/.env declared W9_HTTPS_PORT=443, but the jitsi/web image only listens on 8000 (HTTP) and 8443 (HTTPS).

The Websoft9 gateway uses W9_HTTPS_PORT as the reverse-proxy forward port when a domain is bound, so bound domains were forwarded to https://<app>:443 — a port with no listener, and the critical /libs/*.js requests failed.

Verification

  • docker run --env-file .env ghcr.io/jitsi/web:stable-11248: listeners are :8000 and :8443 only; https://127.0.0.1:443 is refused.
  • Same container: /libs/lib-jitsi-meet.min.js?v=9442 → 200, 1,138,812 bytes; /, /css/all.css, /libs/app.bundle.min.js, /config.js → 200.
  • Replaying the gateway proxy template (proxy_pass $forward_scheme://$server:$port$request_uri with set $port 8443) returns 200 for every critical asset.
  • On the reported deployment, W9_HTTPS_PORT=8443 restored domain access.

Changes

  • .env: W9_HTTPS_PORT=443 → 8443.
  • README.md: the domain guide now states PUBLIC_URL is https://<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.

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.
@zhaojing1987
zhaojing1987 merged commit ebd6ab2 into main Nov 17, 2026
7 checks passed
@zhaojing1987
zhaojing1987 deleted the fix/jitsi-internal-https-port branch November 17, 2026 02:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant