We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker-jitsi-meet/docker-compose.yml
Line 433 in 02499f8
When I open port 8080, it shows an error: Video Quality Impaired - The bridge Channel has been disconnect
console:
WebSocket connection to 'wss://xx.rts-test.com/colibri-ws/jvb/xxxxxxxxx/xxxxxxx?pwd=xxxxxxxxxxxx' failed: _initWebSocket @ BridgeChannel.js:92 t @ BridgeChannel.js:123Understand this errorAI JingleSessionPC.js:1955 2024-12-31T06:40:06.837Z [modules/xmpp/JingleSessionPC.js] JingleSessionPC[session=JVB,initiator=false,sid=xxxxxxx] addRemoteStream - OK BridgeChannel.js:395 2024-12-31T06:40:06.838Z [modules/RTC/BridgeChannel.js] <e.onclose>: Channel closed: 1006
Opening port 9090 doesn't cause this issue.
'127.0.0.1:${JVB_COLIBRI_PORT:-9090}:9090'
I used Nginx for reverse proxy
location ~ ^/colibri-ws/jvb/(.*) { proxy_pass http://127.0.0.1:9090/colibri-ws/jvb/$1$is_args$args; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; tcp_nodelay on; }
The text was updated successfully, but these errors were encountered:
I'm not sure how this is supposed to work. The JVB container has 9090 hard-coded and doesn't use $JVB_COLIBRI_PORT.
Sorry, something went wrong.
Looks like a bogus export.
The web container proxies to port 9090:
docker-jitsi-meet/web/rootfs/defaults/meet.conf
Line 2 in 3ba77e1
Since it does so using the internal container network it doesn't need port 9090 to be declared.
I'll adjust it.
No branches or pull requests
docker-jitsi-meet/docker-compose.yml
Line 433 in 02499f8
When I open port 8080, it shows an error: Video Quality Impaired - The bridge Channel has been disconnect
console:
Opening port 9090 doesn't cause this issue.
I used Nginx for reverse proxy
The text was updated successfully, but these errors were encountered: