How to configure Jitsi-meet to enter the same room through different IP addresses

When I entered the same room via two different IP addresses of meet.jit.si, meet.jit.si worked very well, which was great.
Can you guide me through this configuration?

I did not find a complete configuration guide in the forum.Before that, I have read many posts.By configuring JVB components or OCTO, I still can only enter the same room with one IP address.
I look forward to your reply.

Thanks in advance!
Hugh

What exactly are you trying to achieve?

Thanks for the reply, I guess I need a cluster.
My team plans to deploy jitsi in multiple places. They are deployed on different servers through cluster deployment. I have seen other people discuss such problems on other posts, but I have not been able to figure out the specific configuration.

I don’t know what you need, you tell me! :slight_smile:

What is the purpose here: support more load? have a geographical distribution so meetings happen in server closer to users? something different?

There is no single answer, so please provide as many details as possible.

Yes, that’s what we need.

Our team has deployed our own jitsi network with several servers at different places, and the servers have different IP addresses. If two uses at two different servers try to enter a same room, it’s not possible. We hope you could help us find out how to configure it in such a case so that users at different servers can enter the same room.

So you basically have standalone “islands”. You need something to make sure all useres wanting to go a given room go the right server. We have a similar setup on meet.jit.si. Basically we use Route 53 (and are now experimenting with anycast) to first route you to the nearest entry point. Then, we have HAProxy keeping track of the active conferences so a user is routed there even if it’s not its region, because otherwise it would end up in a parallel universe.

This is not a simple setup and I cannot share the actual config with you.

I’d suggest you start simpler: have a single web, jicofo and prosody entry-point and deploy multiple JVBs for handling the extra load. Then take it from there.

Also, feel free to drop by our biweekly call (jitsi.org/thecall) and ask questions.

1 Like

@saghul
Hi
I am trying to set up a HAProxy to two jitsi meeting shard. the two shards are working normally.
it is not a geo distribution. just local cluster to support more loads.

I am following the video “Scaling Jitsi Meet in the Cloud Tutorial=”

the haproxy config is:
frontend jitsi_meet_frontend
bind *:443 ssl crt /root/server.pem
mode http
option httpclose
option forwardfor
reqadd X-Forwarded-Proto:\ https
default_backend jitsi_meet

backend jitsi_meet
mode http
balance roundrobin
server meet1 meet1.jitsi.domain.com:443 check ssl verify none
server meet2 meet2.jitsi.domain.com:443 check ssl verify none

But I have encounter 2 issue:

  1. I have allowed the camera and audio. but cannot see any thing. screen is black. I am using the self signed cert for haproxy and jitsi nginx (the cert are differnet on nginx and haproxy). I see some hand shake failure in the haproxy log.
  2. I opened 2 browser to join the same meeting. but the http_bind request go to different jitisi server. so how to use it to route users to the same shard and the same jvb server ? is there any sample haproxy config file ?

one more question:
is it possible to use A Nginx replace haproxy ?

1 Like

Ok, thank you! I can understand it.

@saghul Does it mean all uses are routed to a complete jitsi-meet server through HAProxy? For example, if we resolve jitsi.example.com to 3 IP addresses; when 3 servers are normally working, all users are routed to the first IP address through HAProxy to have meetings; when the server of the first IP address is broken down, we can use the complete service on the second IP address. Is it such a working pattern?

@lixiran1 We also want to resolve it!

@saghul In order to ensure the normal operation, we resolve one domain name to different IP addresses and deploy complete jitsi-meet service on them; so when a server is broken down, such as it’s crashed or the service is stoped due to an unknown reason, one another server can keep the service going and users can use it. And if there is only one complete jitsi-meet server working, once it’s crashed, we may not be able to deal with it in time. For this reason, can you give us some suggestion or reference? Technically we can have a try.

wow. seems we have the same target.

there are very little guide and sample about it on the web.

@lixiran1 yes.

Yasen’s tutorials might be helpful here:
https://jitsi.org/tutorials/

Boris

1 Like

thanks for Help Boris.

actually I have followed that video. but cannot work.
I need a sample file of haproxy.