yes, jvb1 is the default JMS, which is inside default docker-compose file. I have copied the docker-compose to a new folder, with the env file, changed the jvb nickname, rest everything matches with the default jvb
I SOLVED IT a minute ago, at least for know … I know about the PR. My modification is based on this PR. I got the base Octo config working, but the bridges never really talked correctly to each other. It was a simple configuration issue:
You have to use 0.0.0.0 for BIND_ADDRESS and the external IP (NOT DNS name!) of the JVB’s machine. It is working now for me!
I am using docker-compose, because I wrote a complete script framework for us internally, that a) builds Jitsi images, b) pulls my own docker-jitsi-meet repo, because I integrated the Octo PR on my own, c) sets up all necessary Jitsi variables, d) injects old Web UI, because we have custom further modifications for it and the new UI simply is not working for us, e) configures Docker swarm network, f) sets up a complete Grafana instance for the whole setup and fires it up.
Everything is based on a single config file each instance. So I set up the config for main instance, copy some files over to the next JVB machine, which have been created during startup of main instance, modifiy only some address values and the JVB counter in the config file and fire it up again. On the second machine, only JVB instance will be created and some exporters for Grafana.
Then I am up and running. I cannot use Swarm, because of the additional config steps which are necessary on the main Grafana instance to pull data from the additional JVBs - at least the way I am doing it.