Moving to websockets

Greetings. Migration guide says this:

 # colibri (JVB) websockets for jvb1
  location ~ ^/colibri-ws/default-id/(.*) {
     proxy_pass http://127.0.0.1:9090/colibri-ws/default-id/$1$is_args$args;
     proxy_http_version 1.1;
     proxy_set_header Upgrade $http_upgrade;
     proxy_set_header Connection "upgrade";
     tcp_nodelay on;
  }

Am I right to think that I need to add a different block like that for every additional videobridge which I have in my setup? (Using the internal IP of the videobridges instead of 127.0.0.1).

Previously, I was able to use the same nginx configuration whatever extra videobridges I had, and I believe this is no longer possible. How do people deal with this? Maybe by installing a nginx server on top of each videobridge?

Thanks.

Look at latest jitsi stable release, they changed it to

# colibri (JVB) websockets
location ~ ^/colibri-ws/([a-zA-Z0-9-\.]+)/(.*) {
    proxy_pass http://$1:9090/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;
} 

Where instead of default-id each jvb identifies itself with it’s own IP address, so your use case should work.

IIRC the dash (-) should be the last or the first element in a set, otherwise it’s processed as a range, not as the dash character… Probably there is no problem in this code since the character before the dash is already an element of a range but not a good practise…

Thanks a lot! Yes, this is the way to go, but apparently this is not yet in the latest stable packages, it’s only in the docker version here: