New jvb break websocket

I search search search no solution.
I build jitsi for AWS. Everything one server he work fine
But I try do another jvb another server he work but bad resolusion and plenty plenty websocket errors for js console like so

WebSocket connection to 'wss://party.family.com/colibri-ws/default-id/68624485a9e3bc8d/4c868538?pwd=*@##**********' failed: Error during WebSocket handshake: Unexpected response code: 403

[modules/RTC/BridgeChannel.js] <WebSocket.e.onclose>:  Channel closed: 1006 

[modules/RTC/BridgeChannel.js] <l._send>:  Bridge Channel send: no opened channel.

So jvb for separate server no do websocket connexion with jitsi. I see plenty people have thees question. How I add new jvb make connect websocket with jitsi?

Check 3. in FAQ · Jitsi Meet Handbook
You need such a nginx config for every jvb. And jvb need to have different server-id in its config like this: docker-jitsi-meet/jvb.conf at master · jitsi/docker-jitsi-meet · GitHub

@damencho thank you for my respond

This are confuse me too much sorry. I suppose create like this inside nginx for every jvb?

# 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;
  }

What to do for aws autoscale then? Autoscale are make new jvb (I put script he give jvb new id) but how to put for nginx?
My friend @emrah are try to help me are show me this skript I put inside nginx. I still see same websocket problem

# colibri (JVB) websockets for additional JVBs
   location ~ ^/colibri-ws/([0-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;

What to do? I confuse too much and make me so sad

This is right if you had setup on every jvb the server-id to be its private address.

This will work only if jvb is on the same machine as nginx, so nginx forwards the connection to 127.0.0.1.

@damencho So how I put if my skript are use aws instance id for jvb nickname? This my confuxion now.

Yes this one he work for jvb on nginx server. But nothing else he work. If I make new jvb server that when websocket error are full for js konsole

@damencho I see if I put ip of jvb server for server-ip then it are work. But tell me where $WS_SERVER_ID are define so maybe I are make it point to jvb ip?

What is that?

@damencho the line you are told me from the link from jvb.conf

server-id = "{{ $WS_SERVER_ID }}"

Use the internal address of the bridge there. And make sure it is accessible from the nginx machine using this address.

@damencho you mean internal ip?

Yes

ok maybe i have many other problem because if I do curl -v to ip of new jvb he no go. I open port tcp/443 udp/10000 tcp/9090 for jvb instance but still he no go for curl. I so tire I no no what I do so wrong

Thank you he fix now. I forget open port inside firewall before is problem