Is it necessary to route videobridge connections via the JMS?

In Nginx on my jitsi signalling node (an ec2 instance) I have the below added to my ngin config:

location ~ ^/colibri-ws/default-id/(.*) {
        proxy_pass http://x.x.x.x: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;

This (as far as I can see) takes a connection on the JVB url, and uses the server-id set to the publically-accessible dns/ip of the videobridge to proxy the request to the videobridge itself, with a couple of headers set. Is this the only way to do this? If I set domain: directly to the public IP of the JVB on the JVB, and put a load balancer infront that listens on 443 and forwards to 9090 would that achieve the same goal?

You could also do that, yes.

That makes managing certs a bit more unwieldy since you need one extra for the JVB, but if that is not a problem for you, go ahead!

1 Like