PUBLIC_URL doesn't accept external port 443
See original GitHub issueSo it looks like colibri-ws can’t be reached when using an external nginx proxy.
[Error] WebSocket connection to 'wss://meet.blah.de/colibri-ws/172.28.0.4/5ee3129342726f27/76aae33e?pwd=4fasf5f7ksfas2dv4ksasfsf9' failed: Unexpected response code: 405
Given the issue #850 I updated my external nginx proxy with this setting:
location = /xmpp-websocket {
proxy_pass http://0.0.0.0:38000/xmpp-websocket;
proxy_http_version 1.1;
proxy_set_header Connection "upgrade";
proxy_set_header Upgrade $http_upgrade;
tcp_nodelay on;
}
I tried to do something similar for colibri but it doesn’t seem to work:
location ~ ^/colibri-ws/([a-zA-Z0-9-\.]+)/(.*) {
proxy_pass http://0.0.0.0:38000/colibri-ws/$1/$2$is_args$args;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
tcp_nodelay on;
}
A thing I noticed is that I tried adding a port to the PUBLIC_URL
as suggested in the new env file but adding the correct :443
port results in the xmpp-websocket failing in the web app.
Without a port in the PUBLIC_URL
the xmpp-websocket works and the meetings work as well but I get constant errors like this as well as bad video quality.
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (4 by maintainers)
Top Results From Across the Web
[SOLVED] Port forwarding, internal server to external port
I've tried using alias but it doesn't work. ... If you are forwarding both port 80 (HTTP) and port 443 (HTTPS), you want...
Read more >Why is Sharepiont appending port number to public URL?
I have created an extended web application, so there are two SharePoint applications running on the same server, one on port 80 and...
Read more >Setup JItsi URL and port - Install & Config
I've installed Jitsi on my Ubuntu 14.04+Apache. After installation, I can only access the Jitsi video conference from the URL of my site....
Read more >Accessing external ip from internal network does not work for ...
I port forwarded port 80 and 443 in the router so that the web server running in rpi is accessible outside. I was...
Read more >Expose localhost as a public URL and debug using ngrok
... port as a public URL through SSL which you can copy from the CLI. ... only accept a public URL and you...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have similar setup - working fine for me (but just small load on jitsi until now):
my nginx reverse-proxy part for the complete jitsi service:
But I needed some more changes to get the colibri WebSocket (triggered inside docker-compose via ENABLE_XMPP_WEBSOCKET ?) working:
inside the docker-compose.yml Adding
- JICOFO_COMPONENT_SECRET
inside the jicofo partinside .env Adding
JICOFO_COMPONENT_SECRET
with a new generated secret key (e.g.openssl rand -hex 16
as it does gen-passwords.sh)All my jitsi images inside the docker-compose pinned to
stable-5765-1
(e.g.image: jitsi/web:stable-5765-1
), running on debian-10 without “WebSocket connection to ‘wss:…’” errors.@polybos Thanks a lot, your config works perfectly, I was stuck for way too long on this! Probably should be added to the documentation in the section “Running behind a reverse proxy”