Load balancing in jitsi meet


#21

Do you see 103.249.237.9 if you do ifconfig?


#22

root@jitsi-virtual-machine:/etc/prosody# ifconfig
ens32 Link encap:Ethernet HWaddr 00:0c:29:23:f2:2d
inet addr:192.168.1.161 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::8d29:cbb6:d5f8:b5cc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:336632 errors:0 dropped:95 overruns:0 frame:0
TX packets:80143 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:77380403 (77.3 MB) TX bytes:12407276 (12.4 MB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:4069 errors:0 dropped:0 overruns:0 frame:0
TX packets:4069 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1059807 (1.0 MB) TX bytes:1059807 (1.0 MB)


#23

So your machine is behind NAT, I already wrote you about that. Then in component_interface you should put “192.168.1.161” and forward that port from your router to the internal machine, so the bridge that is outside that network can access it through internet.


#24

why we are use local machine address for component_interface. my public address already use in component_interface. And i done jitsi-meet installation by the public ip address(as DNS) of my machine.


#25

Cause this is how you specify to prosody which interface to listen to, instead of using localhost, so you can forward the port from your router and make it accessible from the Internet.