[jitsi-users] Distributed Jitsi installation


#1

Hi,
I did Jitsi installation successfully on one Linux box, and everything works fine. My objective is to make distributed installation so that Jitsi Meet is on separate machine than Videobridge. Do you have any tips or links to documents how to do it.

I appreciate any feedback.

Regards
Ismo


#2

Hi,

There is no document about it.
So here are some quick steps to produce one that we call it shard,
this is one jicofo + nginx and multiple jvbs.

apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config
jitsi-meet-prosody

After answering the questions and filling stuff will produce the first
part of the deployment, where prosody lives. Now you need to go to the
prosody config and configure multiple components with different names
for the jvb.

And now on the separate machines, you just need to apt-get install
jitsi-videobridge, and answer questions and configure every jvb
machine with a different component name you configured in prosody, and
the ip address of the prosody machine.
To use a custom component name, different from default
'jitsi-videobridge', you need an extra option in
/etc/jitsi/videobridge/config
JVB_OPTS="--subdomain=jvb2"
This will register the jvb as component with name jvb2.yourdomain.

Regards
damencho

···

On Wed, Jan 10, 2018 at 11:20 AM, Ismo Heikkonen <ismo.heikkonen@accantosystems.com> wrote:

Hi,

I did Jitsi installation successfully on one Linux box, and everything works
fine. My objective is to make distributed installation so that Jitsi Meet is
on separate machine than Videobridge. Do you have any tips or links to
documents how to do it.

I appreciate any feedback.

Regards

Ismo

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#3

Thanks a lot Damian,
I have been struggling with this issue today and I am sure that your quick steps will help me forward.

Regards
Ismo

···

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian Minkov
Sent: 11 January 2018 16:55
To: Jitsi Users <users@jitsi.org>
Subject: Re: [jitsi-users] Distributed Jitsi installation

Hi,

There is no document about it.
So here are some quick steps to produce one that we call it shard, this is one jicofo + nginx and multiple jvbs.

apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config jitsi-meet-prosody

After answering the questions and filling stuff will produce the first part of the deployment, where prosody lives. Now you need to go to the prosody config and configure multiple components with different names for the jvb.

And now on the separate machines, you just need to apt-get install jitsi-videobridge, and answer questions and configure every jvb machine with a different component name you configured in prosody, and the ip address of the prosody machine.
To use a custom component name, different from default 'jitsi-videobridge', you need an extra option in /etc/jitsi/videobridge/config JVB_OPTS="--subdomain=jvb2"
This will register the jvb as component with name jvb2.yourdomain.

Regards
damencho

On Wed, Jan 10, 2018 at 11:20 AM, Ismo Heikkonen <ismo.heikkonen@accantosystems.com> wrote:

Hi,

I did Jitsi installation successfully on one Linux box, and everything
works fine. My objective is to make distributed installation so that
Jitsi Meet is on separate machine than Videobridge. Do you have any
tips or links to documents how to do it.

I appreciate any feedback.

Regards

Ismo

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#4

Also a quick note about prosody configuration:

you need to modify the component_interface:

IE:
component_interface = {"10.1.0.9", "127.0.0.1"}

since usually prosody and jvb are on the same machine so it uses the local address, while if jvb are on separate machines then prosody need to listen to the public/private subnet address (in this case the IP is 10.1.0.9)

Since I’ve spent a lot of time debugging this, seems to be useful to share it!

···

Da: Ismo Heikkonen
Inviato: giovedì 11 gennaio 2018 17:31
A: Jitsi Users
Oggetto: Re: [jitsi-users] Distributed Jitsi installation

Thanks a lot Damian,
I have been struggling with this issue today and I am sure that your quick steps will help me forward.

Regards
Ismo

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian Minkov
Sent: 11 January 2018 16:55
To: Jitsi Users <users@jitsi.org>
Subject: Re: [jitsi-users] Distributed Jitsi installation

Hi,

There is no document about it.
So here are some quick steps to produce one that we call it shard, this is one jicofo + nginx and multiple jvbs.

apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config jitsi-meet-prosody

After answering the questions and filling stuff will produce the first part of the deployment, where prosody lives. Now you need to go to the prosody config and configure multiple components with different names for the jvb.

And now on the separate machines, you just need to apt-get install jitsi-videobridge, and answer questions and configure every jvb machine with a different component name you configured in prosody, and the ip address of the prosody machine.
To use a custom component name, different from default 'jitsi-videobridge', you need an extra option in /etc/jitsi/videobridge/config JVB_OPTS="--subdomain=jvb2"
This will register the jvb as component with name jvb2.yourdomain.

Regards
damencho

On Wed, Jan 10, 2018 at 11:20 AM, Ismo Heikkonen <ismo.heikkonen@accantosystems.com> wrote:

Hi,

I did Jitsi installation successfully on one Linux box, and everything
works fine. My objective is to make distributed installation so that
Jitsi Meet is on separate machine than Videobridge. Do you have any
tips or links to documents how to do it.

I appreciate any feedback.

Regards

Ismo

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users
_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#5

Thanks for your help. I was able to connect remote jvb to the server, where jitsi meet installation is running, but my jitsi meet isn’t able to use the remote jvb.

I made the following kind of installation: full install on one machine and just jvb on the other machine. I can see on the prosody logs that the remote jvb is connected. When I shutdown the local jvb, the conference service does’t work anymore although the remote jvb is still connected. Shall I uninstall the full installation and install just apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config jitsi-meet-prosody one by one?

Regards
Ismo

···

From: users [mailto:users-bounces@jitsi.org] On Behalf Of Andrea Magatti
Sent: 11 January 2018 18:38
To: Jitsi Users <users@jitsi.org>
Subject: [jitsi-users] R: Distributed Jitsi installation

Also a quick note about prosody configuration:

you need to modify the component_interface:

IE:
component_interface = {"10.1.0.9", "127.0.0.1"}

since usually prosody and jvb are on the same machine so it uses the local address, while if jvb are on separate machines then prosody need to listen to the public/private subnet address (in this case the IP is 10.1.0.9)

Since I’ve spent a lot of time debugging this, seems to be useful to share it!

Da: Ismo Heikkonen<mailto:ismo.heikkonen@accantosystems.com>
Inviato: giovedì 11 gennaio 2018 17:31
A: Jitsi Users<mailto:users@jitsi.org>
Oggetto: Re: [jitsi-users] Distributed Jitsi installation

Thanks a lot Damian,
I have been struggling with this issue today and I am sure that your quick steps will help me forward.

Regards
Ismo

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian Minkov
Sent: 11 January 2018 16:55
To: Jitsi Users <users@jitsi.org<mailto:users@jitsi.org>>
Subject: Re: [jitsi-users] Distributed Jitsi installation

Hi,

There is no document about it.
So here are some quick steps to produce one that we call it shard, this is one jicofo + nginx and multiple jvbs.

apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config jitsi-meet-prosody

After answering the questions and filling stuff will produce the first part of the deployment, where prosody lives. Now you need to go to the prosody config and configure multiple components with different names for the jvb.

And now on the separate machines, you just need to apt-get install jitsi-videobridge, and answer questions and configure every jvb machine with a different component name you configured in prosody, and the ip address of the prosody machine.
To use a custom component name, different from default 'jitsi-videobridge', you need an extra option in /etc/jitsi/videobridge/config JVB_OPTS="--subdomain=jvb2"
This will register the jvb as component with name jvb2.yourdomain.

Regards
damencho

On Wed, Jan 10, 2018 at 11:20 AM, Ismo Heikkonen <ismo.heikkonen@accantosystems.com<mailto:ismo.heikkonen@accantosystems.com>> wrote:

Hi,

I did Jitsi installation successfully on one Linux box, and everything
works fine. My objective is to make distributed installation so that
Jitsi Meet is on separate machine than Videobridge. Do you have any
tips or links to documents how to do it.

I appreciate any feedback.

Regards

Ismo

_______________________________________________
users mailing list
users@jitsi.org<mailto:users@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org<mailto:users@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users
_______________________________________________
users mailing list
users@jitsi.org<mailto:users@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#6

Hi,

This should work. There is some time between jicofo checks for jvbs
... there are some tweaks to speed this up if needed. Can you test the
following:
- stop jicofo
- stop the two jvbs
- start the jvb that is on the remote machine
- start jicofo
- test it
What are the symptoms when you say it doesn't work, you get the
console log that there are no jvbs available and you see the reload
screen?

Regards
damencho

···

On Fri, Jan 12, 2018 at 1:53 PM, Ismo Heikkonen <ismo.heikkonen@accantosystems.com> wrote:

Thanks for your help. I was able to connect remote jvb to the server, where
jitsi meet installation is running, but my jitsi meet isn’t able to use the
remote jvb.

I made the following kind of installation: full install on one machine and
just jvb on the other machine. I can see on the prosody logs that the remote
jvb is connected. When I shutdown the local jvb, the conference service
does’t work anymore although the remote jvb is still connected. Shall I
uninstall the full installation and install just apt-get install nginx
jicofo jitsi-meet-web jitsi-meet-web-config jitsi-meet-prosody one by one?

Regards

Ismo

From: users [mailto:users-bounces@jitsi.org] On Behalf Of Andrea Magatti
Sent: 11 January 2018 18:38
To: Jitsi Users <users@jitsi.org>
Subject: [jitsi-users] R: Distributed Jitsi installation

Also a quick note about prosody configuration:

you need to modify the component_interface:

IE:

component_interface = {"10.1.0.9", "127.0.0.1"}

since usually prosody and jvb are on the same machine so it uses the local
address, while if jvb are on separate machines then prosody need to listen
to the public/private subnet address (in this case the IP is 10.1.0.9)

Since I’ve spent a lot of time debugging this, seems to be useful to share
it!

Da: Ismo Heikkonen
Inviato: giovedì 11 gennaio 2018 17:31
A: Jitsi Users
Oggetto: Re: [jitsi-users] Distributed Jitsi installation

Thanks a lot Damian,

I have been struggling with this issue today and I am sure that your quick
steps will help me forward.

Regards

Ismo

-----Original Message-----

From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian Minkov

Sent: 11 January 2018 16:55

To: Jitsi Users <users@jitsi.org>

Subject: Re: [jitsi-users] Distributed Jitsi installation

Hi,

There is no document about it.

So here are some quick steps to produce one that we call it shard, this is
one jicofo + nginx and multiple jvbs.

apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config
jitsi-meet-prosody

After answering the questions and filling stuff will produce the first part
of the deployment, where prosody lives. Now you need to go to the prosody
config and configure multiple components with different names for the jvb.

And now on the separate machines, you just need to apt-get install
jitsi-videobridge, and answer questions and configure every jvb machine with
a different component name you configured in prosody, and the ip address of
the prosody machine.

To use a custom component name, different from default 'jitsi-videobridge',
you need an extra option in /etc/jitsi/videobridge/config
JVB_OPTS="--subdomain=jvb2"

This will register the jvb as component with name jvb2.yourdomain.

Regards

damencho

On Wed, Jan 10, 2018 at 11:20 AM, Ismo Heikkonen > <ismo.heikkonen@accantosystems.com> wrote:

Hi,

I did Jitsi installation successfully on one Linux box, and everything

works fine. My objective is to make distributed installation so that

Jitsi Meet is on separate machine than Videobridge. Do you have any

tips or links to documents how to do it.

I appreciate any feedback.

Regards

Ismo

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#7

Hi,
When I wrote that it doesn't,I tried to access the conference service, and I got :
This site can’t be reached error on browser. When local jvb was running, conference service worked, but when I shut down the local jvb, after short time the conference service was shut down as well.

I followed your instructions and the same: This site can’t be reached error.

Here are some lines from the prosody log:
Jan 12 22:31:25 jcp1773460 info Incoming Jabber component connection
Jan 12 22:31:25 jvb1.accanto.com:component info External component successfully authenticated

Jvb1.accanto.com is the remote jvb.

When I start the local jvb, the conference service starts to work almost immediately,

Regards
Ismo

···

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian Minkov
Sent: 12 January 2018 22:07
To: Jitsi Users <users@jitsi.org>
Subject: Re: [jitsi-users] R: Distributed Jitsi installation

Hi,

This should work. There is some time between jicofo checks for jvbs ... there are some tweaks to speed this up if needed. Can you test the
following:
- stop jicofo
- stop the two jvbs
- start the jvb that is on the remote machine
- start jicofo
- test it
What are the symptoms when you say it doesn't work, you get the console log that there are no jvbs available and you see the reload screen?

Regards
damencho

On Fri, Jan 12, 2018 at 1:53 PM, Ismo Heikkonen <ismo.heikkonen@accantosystems.com> wrote:

Thanks for your help. I was able to connect remote jvb to the server,
where jitsi meet installation is running, but my jitsi meet isn’t
able to use the remote jvb.

I made the following kind of installation: full install on one machine
and just jvb on the other machine. I can see on the prosody logs that
the remote jvb is connected. When I shutdown the local jvb, the
conference service does’t work anymore although the remote jvb is
still connected. Shall I uninstall the full installation and install
just apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config jitsi-meet-prosody one by one?

Regards

Ismo

From: users [mailto:users-bounces@jitsi.org] On Behalf Of Andrea
Magatti
Sent: 11 January 2018 18:38
To: Jitsi Users <users@jitsi.org>
Subject: [jitsi-users] R: Distributed Jitsi installation

Also a quick note about prosody configuration:

you need to modify the component_interface:

IE:

component_interface = {"10.1.0.9", "127.0.0.1"}

since usually prosody and jvb are on the same machine so it uses the
local address, while if jvb are on separate machines then prosody need
to listen to the public/private subnet address (in this case the IP is
10.1.0.9)

Since I’ve spent a lot of time debugging this, seems to be useful to
share it!

Da: Ismo Heikkonen
Inviato: giovedì 11 gennaio 2018 17:31
A: Jitsi Users
Oggetto: Re: [jitsi-users] Distributed Jitsi installation

Thanks a lot Damian,

I have been struggling with this issue today and I am sure that your
quick steps will help me forward.

Regards

Ismo

-----Original Message-----

From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian
Minkov

Sent: 11 January 2018 16:55

To: Jitsi Users <users@jitsi.org>

Subject: Re: [jitsi-users] Distributed Jitsi installation

Hi,

There is no document about it.

So here are some quick steps to produce one that we call it shard,
this is one jicofo + nginx and multiple jvbs.

apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config
jitsi-meet-prosody

After answering the questions and filling stuff will produce the first
part of the deployment, where prosody lives. Now you need to go to the
prosody config and configure multiple components with different names for the jvb.

And now on the separate machines, you just need to apt-get install
jitsi-videobridge, and answer questions and configure every jvb
machine with a different component name you configured in prosody, and
the ip address of the prosody machine.

To use a custom component name, different from default
'jitsi-videobridge', you need an extra option in
/etc/jitsi/videobridge/config JVB_OPTS="--subdomain=jvb2"

This will register the jvb as component with name jvb2.yourdomain.

Regards

damencho

On Wed, Jan 10, 2018 at 11:20 AM, Ismo Heikkonen > <ismo.heikkonen@accantosystems.com> wrote:

Hi,

I did Jitsi installation successfully on one Linux box, and
everything

works fine. My objective is to make distributed installation so that

Jitsi Meet is on separate machine than Videobridge. Do you have any

tips or links to documents how to do it.

I appreciate any feedback.

Regards

Ismo

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#8

Wait, this means you are not using nginx or apache, but you are
serving the jitsi-meet client using the jetty that is embedded in the
jvb. In deployments where jvb is on a different machine, you need a
web server to serve the content. There is no easy way to move from
jetty to nginx deployment, other than configuring it by hand or
purging everything and install from scratch (here there are risks that
some left config can make problems on the new install).
On a clean deployment you will do
apt-get install nginx jitsi-meet.
In my initial email I wrote that, the first package to install is nginx.

Regards
damencho

···

On Fri, Jan 12, 2018 at 2:53 PM, Ismo Heikkonen <ismo.heikkonen@accantosystems.com> wrote:

Hi,
When I wrote that it doesn't,I tried to access the conference service, and I got :
This site can’t be reached error on browser. When local jvb was running, conference service worked, but when I shut down the local jvb, after short time the conference service was shut down as well.

I followed your instructions and the same: This site can’t be reached error.

Here are some lines from the prosody log:
Jan 12 22:31:25 jcp1773460 info Incoming Jabber component connection
Jan 12 22:31:25 jvb1.accanto.com:component info External component successfully authenticated

Jvb1.accanto.com is the remote jvb.

When I start the local jvb, the conference service starts to work almost immediately,

Regards
Ismo

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian Minkov
Sent: 12 January 2018 22:07
To: Jitsi Users <users@jitsi.org>
Subject: Re: [jitsi-users] R: Distributed Jitsi installation

Hi,

This should work. There is some time between jicofo checks for jvbs ... there are some tweaks to speed this up if needed. Can you test the
following:
- stop jicofo
- stop the two jvbs
- start the jvb that is on the remote machine
- start jicofo
- test it
What are the symptoms when you say it doesn't work, you get the console log that there are no jvbs available and you see the reload screen?

Regards
damencho

On Fri, Jan 12, 2018 at 1:53 PM, Ismo Heikkonen <ismo.heikkonen@accantosystems.com> wrote:

Thanks for your help. I was able to connect remote jvb to the server,
where jitsi meet installation is running, but my jitsi meet isn’t
able to use the remote jvb.

I made the following kind of installation: full install on one machine
and just jvb on the other machine. I can see on the prosody logs that
the remote jvb is connected. When I shutdown the local jvb, the
conference service does’t work anymore although the remote jvb is
still connected. Shall I uninstall the full installation and install
just apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config jitsi-meet-prosody one by one?

Regards

Ismo

From: users [mailto:users-bounces@jitsi.org] On Behalf Of Andrea
Magatti
Sent: 11 January 2018 18:38
To: Jitsi Users <users@jitsi.org>
Subject: [jitsi-users] R: Distributed Jitsi installation

Also a quick note about prosody configuration:

you need to modify the component_interface:

IE:

component_interface = {"10.1.0.9", "127.0.0.1"}

since usually prosody and jvb are on the same machine so it uses the
local address, while if jvb are on separate machines then prosody need
to listen to the public/private subnet address (in this case the IP is
10.1.0.9)

Since I’ve spent a lot of time debugging this, seems to be useful to
share it!

Da: Ismo Heikkonen
Inviato: giovedì 11 gennaio 2018 17:31
A: Jitsi Users
Oggetto: Re: [jitsi-users] Distributed Jitsi installation

Thanks a lot Damian,

I have been struggling with this issue today and I am sure that your
quick steps will help me forward.

Regards

Ismo

-----Original Message-----

From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian
Minkov

Sent: 11 January 2018 16:55

To: Jitsi Users <users@jitsi.org>

Subject: Re: [jitsi-users] Distributed Jitsi installation

Hi,

There is no document about it.

So here are some quick steps to produce one that we call it shard,
this is one jicofo + nginx and multiple jvbs.

apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config
jitsi-meet-prosody

After answering the questions and filling stuff will produce the first
part of the deployment, where prosody lives. Now you need to go to the
prosody config and configure multiple components with different names for the jvb.

And now on the separate machines, you just need to apt-get install
jitsi-videobridge, and answer questions and configure every jvb
machine with a different component name you configured in prosody, and
the ip address of the prosody machine.

To use a custom component name, different from default
'jitsi-videobridge', you need an extra option in
/etc/jitsi/videobridge/config JVB_OPTS="--subdomain=jvb2"

This will register the jvb as component with name jvb2.yourdomain.

Regards

damencho

On Wed, Jan 10, 2018 at 11:20 AM, Ismo Heikkonen >> <ismo.heikkonen@accantosystems.com> wrote:

Hi,

I did Jitsi installation successfully on one Linux box, and
everything

works fine. My objective is to make distributed installation so that

Jitsi Meet is on separate machine than Videobridge. Do you have any

tips or links to documents how to do it.

I appreciate any feedback.

Regards

Ismo

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users
_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#9

I’ve got a question too

There is a way so put nginx on a different machine than jicofo and prosody?
Tested in many way, but could not solve this

thanks

···

Da: Damian Minkov
Inviato: venerdì 12 gennaio 2018 22:25
A: Jitsi Users
Oggetto: Re: [jitsi-users] R: Distributed Jitsi installation

Wait, this means you are not using nginx or apache, but you are
serving the jitsi-meet client using the jetty that is embedded in the
jvb. In deployments where jvb is on a different machine, you need a
web server to serve the content. There is no easy way to move from
jetty to nginx deployment, other than configuring it by hand or
purging everything and install from scratch (here there are risks that
some left config can make problems on the new install).
On a clean deployment you will do
apt-get install nginx jitsi-meet.
In my initial email I wrote that, the first package to install is nginx.

Regards
damencho

On Fri, Jan 12, 2018 at 2:53 PM, Ismo Heikkonen <ismo.heikkonen@accantosystems.com> wrote:

Hi,
When I wrote that it doesn't,I tried to access the conference service, and I got :
This site can’t be reached error on browser. When local jvb was running, conference service worked, but when I shut down the local jvb, after short time the conference service was shut down as well.

I followed your instructions and the same: This site can’t be reached error.

Here are some lines from the prosody log:
Jan 12 22:31:25 jcp1773460 info Incoming Jabber component connection
Jan 12 22:31:25 jvb1.accanto.com:component info External component successfully authenticated

Jvb1.accanto.com is the remote jvb.

When I start the local jvb, the conference service starts to work almost immediately,

Regards
Ismo

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian Minkov
Sent: 12 January 2018 22:07
To: Jitsi Users <users@jitsi.org>
Subject: Re: [jitsi-users] R: Distributed Jitsi installation

Hi,

This should work. There is some time between jicofo checks for jvbs ... there are some tweaks to speed this up if needed. Can you test the
following:
- stop jicofo
- stop the two jvbs
- start the jvb that is on the remote machine
- start jicofo
- test it
What are the symptoms when you say it doesn't work, you get the console log that there are no jvbs available and you see the reload screen?

Regards
damencho

On Fri, Jan 12, 2018 at 1:53 PM, Ismo Heikkonen <ismo.heikkonen@accantosystems.com> wrote:

Thanks for your help. I was able to connect remote jvb to the server,
where jitsi meet installation is running, but my jitsi meet isn’t
able to use the remote jvb.

I made the following kind of installation: full install on one machine
and just jvb on the other machine. I can see on the prosody logs that
the remote jvb is connected. When I shutdown the local jvb, the
conference service does’t work anymore although the remote jvb is
still connected. Shall I uninstall the full installation and install
just apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config jitsi-meet-prosody one by one?

Regards

Ismo

From: users [mailto:users-bounces@jitsi.org] On Behalf Of Andrea
Magatti
Sent: 11 January 2018 18:38
To: Jitsi Users <users@jitsi.org>
Subject: [jitsi-users] R: Distributed Jitsi installation

Also a quick note about prosody configuration:

you need to modify the component_interface:

IE:

component_interface = {"10.1.0.9", "127.0.0.1"}

since usually prosody and jvb are on the same machine so it uses the
local address, while if jvb are on separate machines then prosody need
to listen to the public/private subnet address (in this case the IP is
10.1.0.9)

Since I’ve spent a lot of time debugging this, seems to be useful to
share it!

Da: Ismo Heikkonen
Inviato: giovedì 11 gennaio 2018 17:31
A: Jitsi Users
Oggetto: Re: [jitsi-users] Distributed Jitsi installation

Thanks a lot Damian,

I have been struggling with this issue today and I am sure that your
quick steps will help me forward.

Regards

Ismo

-----Original Message-----

From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian
Minkov

Sent: 11 January 2018 16:55

To: Jitsi Users <users@jitsi.org>

Subject: Re: [jitsi-users] Distributed Jitsi installation

Hi,

There is no document about it.

So here are some quick steps to produce one that we call it shard,
this is one jicofo + nginx and multiple jvbs.

apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config
jitsi-meet-prosody

After answering the questions and filling stuff will produce the first
part of the deployment, where prosody lives. Now you need to go to the
prosody config and configure multiple components with different names for the jvb.

And now on the separate machines, you just need to apt-get install
jitsi-videobridge, and answer questions and configure every jvb
machine with a different component name you configured in prosody, and
the ip address of the prosody machine.

To use a custom component name, different from default
'jitsi-videobridge', you need an extra option in
/etc/jitsi/videobridge/config JVB_OPTS="--subdomain=jvb2"

This will register the jvb as component with name jvb2.yourdomain.

Regards

damencho

On Wed, Jan 10, 2018 at 11:20 AM, Ismo Heikkonen >> <ismo.heikkonen@accantosystems.com> wrote:

Hi,

I did Jitsi installation successfully on one Linux box, and
everything

works fine. My objective is to make distributed installation so that

Jitsi Meet is on separate machine than Videobridge. Do you have any

tips or links to documents how to do it.

I appreciate any feedback.

Regards

Ismo

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users
_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#10

Hi,
Thanks for everybody for help. I don't see any errors in the remote machine's jvb logs anymore, so I conclude that it works fine:
JVB 2018-01-15 17:34:51.102 FINE: [57] org.jitsi.videobridge.xmpp.ComponentImpl.log() RECV: <iq id="b4kTo-33" type="result" to="jvb1.accanto.com" from="accanto.com"/>
JVB 2018-01-15 17:35:01.103 FINE: [25] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component 'JitsiVideobridge') Processing IQ (packetId b4kTo-35): <iq id="b4kTo-35" type="result" to="jvb1.accanto.com" from="accanto.com"/>

I have also jvb running on the local machine with jitsi meet installation.

But however, there is one issue, I don't understand: when I stop both videobridges, the conference seems to work fine still. I can even start new conferences without any videobridges. I checked from the log files that the videobridges were not up and running.

Regards
Ismo


#11

Sure, as long as you route bosh requests (/http-bind) to prosody

Boris

···

On Sat, Jan 13, 2018 at 10:48 AM Andrea Magatti <andrea.magatti@gmail.com> wrote:

I’ve got a question too

There is a way so put nginx on a different machine than jicofo and prosody?

Tested in many way, but could not solve this

thanks

*Da: *Damian Minkov <damencho@jitsi.org>
*Inviato: *venerdì 12 gennaio 2018 22:25
*A: *Jitsi Users <users@jitsi.org>
*Oggetto: *Re: [jitsi-users] R: Distributed Jitsi installation

Wait, this means you are not using nginx or apache, but you are

serving the jitsi-meet client using the jetty that is embedded in the

jvb. In deployments where jvb is on a different machine, you need a

web server to serve the content. There is no easy way to move from

jetty to nginx deployment, other than configuring it by hand or

purging everything and install from scratch (here there are risks that

some left config can make problems on the new install).

On a clean deployment you will do

apt-get install nginx jitsi-meet.

In my initial email I wrote that, the first package to install is nginx.

Regards

damencho

On Fri, Jan 12, 2018 at 2:53 PM, Ismo Heikkonen > > <ismo.heikkonen@accantosystems.com> wrote:

> Hi,

> When I wrote that it doesn't,I tried to access the conference service,
and I got :

> This site can’t be reached error on browser. When local jvb was running,
conference service worked, but when I shut down the local jvb, after short
time the conference service was shut down as well.

>

> I followed your instructions and the same: This site can’t be reached
error.

>

> Here are some lines from the prosody log:

> Jan 12 22:31:25 jcp1773460 info Incoming Jabber component
connection

> Jan 12 22:31:25 jvb1.accanto.com:component info External
component successfully authenticated

>

> Jvb1.accanto.com is the remote jvb.

>

> When I start the local jvb, the conference service starts to work almost
immediately,

>

> Regards

> Ismo

>

>

> -----Original Message-----

> From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian Minkov

> Sent: 12 January 2018 22:07

> To: Jitsi Users <users@jitsi.org>

> Subject: Re: [jitsi-users] R: Distributed Jitsi installation

>

> Hi,

>

> This should work. There is some time between jicofo checks for jvbs ...
there are some tweaks to speed this up if needed. Can you test the

> following:

> - stop jicofo

> - stop the two jvbs

> - start the jvb that is on the remote machine

> - start jicofo

> - test it

> What are the symptoms when you say it doesn't work, you get the console
log that there are no jvbs available and you see the reload screen?

>

> Regards

> damencho

>

>

> On Fri, Jan 12, 2018 at 1:53 PM, Ismo Heikkonen < > ismo.heikkonen@accantosystems.com> wrote:

>> Thanks for your help. I was able to connect remote jvb to the server,

>> where jitsi meet installation is running, but my jitsi meet isn’t

>> able to use the remote jvb.

>>

>>

>>

>> I made the following kind of installation: full install on one machine

>> and just jvb on the other machine. I can see on the prosody logs that

>> the remote jvb is connected. When I shutdown the local jvb, the

>> conference service does’t work anymore although the remote jvb is

>> still connected. Shall I uninstall the full installation and install

>> just apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config
jitsi-meet-prosody one by one?

>>

>>

>>

>> Regards

>>

>> Ismo

>>

>>

>>

>>

>>

>> From: users [mailto:users-bounces@jitsi.org] On Behalf Of Andrea

>> Magatti

>> Sent: 11 January 2018 18:38

>> To: Jitsi Users <users@jitsi.org>

>> Subject: [jitsi-users] R: Distributed Jitsi installation

>>

>>

>>

>> Also a quick note about prosody configuration:

>>

>>

>>

>> you need to modify the component_interface:

>>

>>

>>

>> IE:

>>

>> component_interface = {"10.1.0.9", "127.0.0.1"}

>>

>>

>>

>> since usually prosody and jvb are on the same machine so it uses the

>> local address, while if jvb are on separate machines then prosody need

>> to listen to the public/private subnet address (in this case the IP is

>> 10.1.0.9)

>>

>>

>>

>> Since I’ve spent a lot of time debugging this, seems to be useful to

>> share it!

>>

>>

>>

>>

>>

>>

>>

>> Da: Ismo Heikkonen

>> Inviato: giovedì 11 gennaio 2018 17:31

>> A: Jitsi Users

>> Oggetto: Re: [jitsi-users] Distributed Jitsi installation

>>

>>

>>

>> Thanks a lot Damian,

>>

>> I have been struggling with this issue today and I am sure that your

>> quick steps will help me forward.

>>

>>

>>

>> Regards

>>

>> Ismo

>>

>>

>>

>> -----Original Message-----

>>

>> From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian

>> Minkov

>>

>> Sent: 11 January 2018 16:55

>>

>> To: Jitsi Users <users@jitsi.org>

>>

>> Subject: Re: [jitsi-users] Distributed Jitsi installation

>>

>>

>>

>> Hi,

>>

>>

>>

>> There is no document about it.

>>

>> So here are some quick steps to produce one that we call it shard,

>> this is one jicofo + nginx and multiple jvbs.

>>

>>

>>

>> apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config

>> jitsi-meet-prosody

>>

>>

>>

>> After answering the questions and filling stuff will produce the first

>> part of the deployment, where prosody lives. Now you need to go to the

>> prosody config and configure multiple components with different names
for the jvb.

>>

>>

>>

>> And now on the separate machines, you just need to apt-get install

>> jitsi-videobridge, and answer questions and configure every jvb

>> machine with a different component name you configured in prosody, and

>> the ip address of the prosody machine.

>>

>> To use a custom component name, different from default

>> 'jitsi-videobridge', you need an extra option in

>> /etc/jitsi/videobridge/config JVB_OPTS="--subdomain=jvb2"

>>

>> This will register the jvb as component with name jvb2.yourdomain.

>>

>>

>>

>> Regards

>>

>> damencho

>>

>>

>>

>>

>>

>>

>>

>> On Wed, Jan 10, 2018 at 11:20 AM, Ismo Heikkonen > > >> <ismo.heikkonen@accantosystems.com> wrote:

>>

>>> Hi,

>>

>>>

>>

>>> I did Jitsi installation successfully on one Linux box, and

>>> everything

>>

>>> works fine. My objective is to make distributed installation so that

>>

>>> Jitsi Meet is on separate machine than Videobridge. Do you have any

>>

>>> tips or links to documents how to do it.

>>

>>>

>>

>>>

>>

>>>

>>

>>> I appreciate any feedback.

>>

>>>

>>

>>>

>>

>>>

>>

>>> Regards

>>

>>>

>>

>>> Ismo

>>

>>>

>>

>>>

>>

>>>

>>

>>>

>>

>>> _______________________________________________

>>

>>> users mailing list

>>

>>> users@jitsi.org

>>

>>> Unsubscribe instructions and other list options:

>>

>>> http://lists.jitsi.org/mailman/listinfo/users

>>

>>

>>

>> _______________________________________________

>>

>> users mailing list

>>

>> users@jitsi.org

>>

>> Unsubscribe instructions and other list options:

>>

>> http://lists.jitsi.org/mailman/listinfo/users

>>

>> _______________________________________________

>>

>> users mailing list

>>

>> users@jitsi.org

>>

>> Unsubscribe instructions and other list options:

>>

>> http://lists.jitsi.org/mailman/listinfo/users

>>

>>

>>

>>

>> _______________________________________________

>> users mailing list

>> users@jitsi.org

>> Unsubscribe instructions and other list options:

>> http://lists.jitsi.org/mailman/listinfo/users

>

> _______________________________________________

> users mailing list

> users@jitsi.org

> Unsubscribe instructions and other list options:

> http://lists.jitsi.org/mailman/listinfo/users

> _______________________________________________

> users mailing list

> users@jitsi.org

> Unsubscribe instructions and other list options:

> http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#12

You are testing with a conference of two participants who connect by
default using p2p. Turn off p2p or test with 3 tabs(3 participants).

Regards
damencho

···

On Jan 15, 2018 09:49, "Ismo Heikkonen" <ismo.heikkonen@accantosystems.com> wrote:

Hi,
Thanks for everybody for help. I don't see any errors in the remote
machine's jvb logs anymore, so I conclude that it works fine:
JVB 2018-01-15 17:34:51.102 FINE: [57] org.jitsi.videobridge.xmpp.ComponentImpl.log()
RECV: <iq id="b4kTo-33" type="result" to="jvb1.accanto.com" from="
accanto.com"/>
JVB 2018-01-15 17:35:01.103 FINE: [25] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ()
(serving component 'JitsiVideobridge') Processing IQ (packetId b4kTo-35):
<iq id="b4kTo-35" type="result" to="jvb1.accanto.com" from="accanto.com"/>

I have also jvb running on the local machine with jitsi meet installation.

But however, there is one issue, I don't understand: when I stop both
videobridges, the conference seems to work fine still. I can even start new
conferences without any videobridges. I checked from the log files that the
videobridges were not up and running.

Regards
Ismo

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#13

Thanks a lot !
Ismo

···

From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian Minkov
Sent: 15 January 2018 22:08
To: Jitsi Users <users@jitsi.org>
Subject: Re: [jitsi-users] R: Distributed Jitsi installation

You are testing with a conference of two participants who connect by default using p2p. Turn off p2p or test with 3 tabs(3 participants).

Regards
damencho

On Jan 15, 2018 09:49, "Ismo Heikkonen" <ismo.heikkonen@accantosystems.com<mailto:ismo.heikkonen@accantosystems.com>> wrote:
Hi,
Thanks for everybody for help. I don't see any errors in the remote machine's jvb logs anymore, so I conclude that it works fine:
JVB 2018-01-15 17:34:51.102 FINE: [57] org.jitsi.videobridge.xmpp.ComponentImpl.log() RECV: <iq id="b4kTo-33" type="result" to="jvb1.accanto.com<http://jvb1.accanto.com>" from="accanto.com<http://accanto.com>"/>
JVB 2018-01-15 17:35:01.103 FINE: [25] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component 'JitsiVideobridge') Processing IQ (packetId b4kTo-35): <iq id="b4kTo-35" type="result" to="jvb1.accanto.com<http://jvb1.accanto.com>" from="accanto.com<http://accanto.com>"/>

I have also jvb running on the local machine with jitsi meet installation.

But however, there is one issue, I don't understand: when I stop both videobridges, the conference seems to work fine still. I can even start new conferences without any videobridges. I checked from the log files that the videobridges were not up and running.

Regards
Ismo

_______________________________________________
users mailing list
users@jitsi.org<mailto:users@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#14

Thanks,

already done that.
My concern is about name resolution

Is it possible to have a FQDN like www.example.com and a jabber domain with different name (ex: jabber.example.com)?

Andrea

···

Da: Boris Grozev
Inviato: sabato 13 gennaio 2018 21:05
A: Jitsi Users
Oggetto: Re: [jitsi-users] R: R: Distributed Jitsi installation

Sure, as long as you route bosh requests (/http-bind) to prosody

Boris

On Sat, Jan 13, 2018 at 10:48 AM Andrea Magatti <andrea.magatti@gmail.com> wrote:
I’ve got a question too

There is a way so put nginx on a different machine than jicofo and prosody?
Tested in many way, but could not solve this

thanks

Da: Damian Minkov
Inviato: venerdì 12 gennaio 2018 22:25
A: Jitsi Users
Oggetto: Re: [jitsi-users] R: Distributed Jitsi installation

Wait, this means you are not using nginx or apache, but you are
serving the jitsi-meet client using the jetty that is embedded in the
jvb. In deployments where jvb is on a different machine, you need a
web server to serve the content. There is no easy way to move from
jetty to nginx deployment, other than configuring it by hand or
purging everything and install from scratch (here there are risks that
some left config can make problems on the new install).
On a clean deployment you will do
apt-get install nginx jitsi-meet.
In my initial email I wrote that, the first package to install is nginx.

Regards
damencho

On Fri, Jan 12, 2018 at 2:53 PM, Ismo Heikkonen <ismo.heikkonen@accantosystems.com> wrote:

Hi,
When I wrote that it doesn't,I tried to access the conference service, and I got :
This site can’t be reached error on browser. When local jvb was running, conference service worked, but when I shut down the local jvb, after short time the conference service was shut down as well.

I followed your instructions and the same: This site can’t be reached error.

Here are some lines from the prosody log:
Jan 12 22:31:25 jcp1773460 info Incoming Jabber component connection
Jan 12 22:31:25 jvb1.accanto.com:component info External component successfully authenticated

Jvb1.accanto.com is the remote jvb.

When I start the local jvb, the conference service starts to work almost immediately,

Regards
Ismo

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian Minkov
Sent: 12 January 2018 22:07
To: Jitsi Users <users@jitsi.org>
Subject: Re: [jitsi-users] R: Distributed Jitsi installation

Hi,

This should work. There is some time between jicofo checks for jvbs ... there are some tweaks to speed this up if needed. Can you test the
following:
- stop jicofo
- stop the two jvbs
- start the jvb that is on the remote machine
- start jicofo
- test it
What are the symptoms when you say it doesn't work, you get the console log that there are no jvbs available and you see the reload screen?

Regards
damencho

On Fri, Jan 12, 2018 at 1:53 PM, Ismo Heikkonen <ismo.heikkonen@accantosystems.com> wrote:

Thanks for your help. I was able to connect remote jvb to the server,
where jitsi meet installation is running, but my jitsi meet isn’t
able to use the remote jvb.

I made the following kind of installation: full install on one machine
and just jvb on the other machine. I can see on the prosody logs that
the remote jvb is connected. When I shutdown the local jvb, the
conference service does’t work anymore although the remote jvb is
still connected. Shall I uninstall the full installation and install
just apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config jitsi-meet-prosody one by one?

Regards

Ismo

From: users [mailto:users-bounces@jitsi.org] On Behalf Of Andrea
Magatti
Sent: 11 January 2018 18:38
To: Jitsi Users <users@jitsi.org>
Subject: [jitsi-users] R: Distributed Jitsi installation

Also a quick note about prosody configuration:

you need to modify the component_interface:

IE:

component_interface = {"10.1.0.9", "127.0.0.1"}

since usually prosody and jvb are on the same machine so it uses the
local address, while if jvb are on separate machines then prosody need
to listen to the public/private subnet address (in this case the IP is
10.1.0.9)

Since I’ve spent a lot of time debugging this, seems to be useful to
share it!

Da: Ismo Heikkonen
Inviato: giovedì 11 gennaio 2018 17:31
A: Jitsi Users
Oggetto: Re: [jitsi-users] Distributed Jitsi installation

Thanks a lot Damian,

I have been struggling with this issue today and I am sure that your
quick steps will help me forward.

Regards

Ismo

-----Original Message-----

From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian
Minkov

Sent: 11 January 2018 16:55

To: Jitsi Users <users@jitsi.org>

Subject: Re: [jitsi-users] Distributed Jitsi installation

Hi,

There is no document about it.

So here are some quick steps to produce one that we call it shard,
this is one jicofo + nginx and multiple jvbs.

apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config
jitsi-meet-prosody

After answering the questions and filling stuff will produce the first
part of the deployment, where prosody lives. Now you need to go to the
prosody config and configure multiple components with different names for the jvb.

And now on the separate machines, you just need to apt-get install
jitsi-videobridge, and answer questions and configure every jvb
machine with a different component name you configured in prosody, and
the ip address of the prosody machine.

To use a custom component name, different from default
'jitsi-videobridge', you need an extra option in
/etc/jitsi/videobridge/config JVB_OPTS="--subdomain=jvb2"

This will register the jvb as component with name jvb2.yourdomain.

Regards

damencho

On Wed, Jan 10, 2018 at 11:20 AM, Ismo Heikkonen >> <ismo.heikkonen@accantosystems.com> wrote:

Hi,

I did Jitsi installation successfully on one Linux box, and
everything

works fine. My objective is to make distributed installation so that

Jitsi Meet is on separate machine than Videobridge. Do you have any

tips or links to documents how to do it.

I appreciate any feedback.

Regards

Ismo

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users
_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#15

Yes, all the xmmp domains are virtual for jitsi meet. If you just make sure
the bosh proxy sets a domain you can have different http domains and xmpp
domains.
Its just prosody looks for which host is the bosh request, but this can be
forced in the nginx config.

Regards
damencho

···

On Jan 14, 2018 01:56, "Andrea Magatti" <andrea.magatti@gmail.com> wrote:

Thanks,

already done that.

My concern is about name resolution

Is it possible to have a FQDN like www.example.com and a jabber domain
with different name (ex: jabber.example.com)?

Andrea

*Da: *Boris Grozev <boris@sip-communicator.org>
*Inviato: *sabato 13 gennaio 2018 21:05
*A: *Jitsi Users <users@jitsi.org>
*Oggetto: *Re: [jitsi-users] R: R: Distributed Jitsi installation

Sure, as long as you route bosh requests (/http-bind) to prosody

Boris

On Sat, Jan 13, 2018 at 10:48 AM Andrea Magatti <andrea.magatti@gmail.com> > wrote:

I’ve got a question too

There is a way so put nginx on a different machine than jicofo and prosody?

Tested in many way, but could not solve this

thanks

*Da: *Damian Minkov <damencho@jitsi.org>
*Inviato: *venerdì 12 gennaio 2018 22:25
*A: *Jitsi Users <users@jitsi.org>
*Oggetto: *Re: [jitsi-users] R: Distributed Jitsi installation

Wait, this means you are not using nginx or apache, but you are

serving the jitsi-meet client using the jetty that is embedded in the

jvb. In deployments where jvb is on a different machine, you need a

web server to serve the content. There is no easy way to move from

jetty to nginx deployment, other than configuring it by hand or

purging everything and install from scratch (here there are risks that

some left config can make problems on the new install).

On a clean deployment you will do

apt-get install nginx jitsi-meet.

In my initial email I wrote that, the first package to install is nginx.

Regards

damencho

On Fri, Jan 12, 2018 at 2:53 PM, Ismo Heikkonen > > <ismo.heikkonen@accantosystems.com> wrote:

> Hi,

> When I wrote that it doesn't,I tried to access the conference service,
and I got :

> This site can’t be reached error on browser. When local jvb was running,
conference service worked, but when I shut down the local jvb, after short
time the conference service was shut down as well.

>

> I followed your instructions and the same: This site can’t be reached
error.

>

> Here are some lines from the prosody log:

> Jan 12 22:31:25 jcp1773460 info Incoming Jabber component
connection

> Jan 12 22:31:25 jvb1.accanto.com:component info External
component successfully authenticated

>

> Jvb1.accanto.com is the remote jvb.

>

> When I start the local jvb, the conference service starts to work almost
immediately,

>

> Regards

> Ismo

>

>

> -----Original Message-----

> From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian Minkov

> Sent: 12 January 2018 22:07

> To: Jitsi Users <users@jitsi.org>

> Subject: Re: [jitsi-users] R: Distributed Jitsi installation

>

> Hi,

>

> This should work. There is some time between jicofo checks for jvbs ...
there are some tweaks to speed this up if needed. Can you test the

> following:

> - stop jicofo

> - stop the two jvbs

> - start the jvb that is on the remote machine

> - start jicofo

> - test it

> What are the symptoms when you say it doesn't work, you get the console
log that there are no jvbs available and you see the reload screen?

>

> Regards

> damencho

>

>

> On Fri, Jan 12, 2018 at 1:53 PM, Ismo Heikkonen <ismo.heikkonen@ > accantosystems.com> wrote:

>> Thanks for your help. I was able to connect remote jvb to the server,

>> where jitsi meet installation is running, but my jitsi meet isn’t

>> able to use the remote jvb.

>>

>>

>>

>> I made the following kind of installation: full install on one machine

>> and just jvb on the other machine. I can see on the prosody logs that

>> the remote jvb is connected. When I shutdown the local jvb, the

>> conference service does’t work anymore although the remote jvb is

>> still connected. Shall I uninstall the full installation and install

>> just apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config
jitsi-meet-prosody one by one?

>>

>>

>>

>> Regards

>>

>> Ismo

>>

>>

>>

>>

>>

>> From: users [mailto:users-bounces@jitsi.org] On Behalf Of Andrea

>> Magatti

>> Sent: 11 January 2018 18:38

>> To: Jitsi Users <users@jitsi.org>

>> Subject: [jitsi-users] R: Distributed Jitsi installation

>>

>>

>>

>> Also a quick note about prosody configuration:

>>

>>

>>

>> you need to modify the component_interface:

>>

>>

>>

>> IE:

>>

>> component_interface = {"10.1.0.9", "127.0.0.1"}

>>

>>

>>

>> since usually prosody and jvb are on the same machine so it uses the

>> local address, while if jvb are on separate machines then prosody need

>> to listen to the public/private subnet address (in this case the IP is

>> 10.1.0.9)

>>

>>

>>

>> Since I’ve spent a lot of time debugging this, seems to be useful to

>> share it!

>>

>>

>>

>>

>>

>>

>>

>> Da: Ismo Heikkonen

>> Inviato: giovedì 11 gennaio 2018 17:31

>> A: Jitsi Users

>> Oggetto: Re: [jitsi-users] Distributed Jitsi installation

>>

>>

>>

>> Thanks a lot Damian,

>>

>> I have been struggling with this issue today and I am sure that your

>> quick steps will help me forward.

>>

>>

>>

>> Regards

>>

>> Ismo

>>

>>

>>

>> -----Original Message-----

>>

>> From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian

>> Minkov

>>

>> Sent: 11 January 2018 16:55

>>

>> To: Jitsi Users <users@jitsi.org>

>>

>> Subject: Re: [jitsi-users] Distributed Jitsi installation

>>

>>

>>

>> Hi,

>>

>>

>>

>> There is no document about it.

>>

>> So here are some quick steps to produce one that we call it shard,

>> this is one jicofo + nginx and multiple jvbs.

>>

>>

>>

>> apt-get install nginx jicofo jitsi-meet-web jitsi-meet-web-config

>> jitsi-meet-prosody

>>

>>

>>

>> After answering the questions and filling stuff will produce the first

>> part of the deployment, where prosody lives. Now you need to go to the

>> prosody config and configure multiple components with different names
for the jvb.

>>

>>

>>

>> And now on the separate machines, you just need to apt-get install

>> jitsi-videobridge, and answer questions and configure every jvb

>> machine with a different component name you configured in prosody, and

>> the ip address of the prosody machine.

>>

>> To use a custom component name, different from default

>> 'jitsi-videobridge', you need an extra option in

>> /etc/jitsi/videobridge/config JVB_OPTS="--subdomain=jvb2"

>>

>> This will register the jvb as component with name jvb2.yourdomain.

>>

>>

>>

>> Regards

>>

>> damencho

>>

>>

>>

>>

>>

>>

>>

>> On Wed, Jan 10, 2018 at 11:20 AM, Ismo Heikkonen > > >> <ismo.heikkonen@accantosystems.com> wrote:

>>

>>> Hi,

>>

>>>

>>

>>> I did Jitsi installation successfully on one Linux box, and

>>> everything

>>

>>> works fine. My objective is to make distributed installation so that

>>

>>> Jitsi Meet is on separate machine than Videobridge. Do you have any

>>

>>> tips or links to documents how to do it.

>>

>>>

>>

>>>

>>

>>>

>>

>>> I appreciate any feedback.

>>

>>>

>>

>>>

>>

>>>

>>

>>> Regards

>>

>>>

>>

>>> Ismo

>>

>>>

>>

>>>

>>

>>>

>>

>>>

>>

>>> _______________________________________________

>>

>>> users mailing list

>>

>>> users@jitsi.org

>>

>>> Unsubscribe instructions and other list options:

>>

>>> http://lists.jitsi.org/mailman/listinfo/users

>>

>>

>>

>> _______________________________________________

>>

>> users mailing list

>>

>> users@jitsi.org

>>

>> Unsubscribe instructions and other list options:

>>

>> http://lists.jitsi.org/mailman/listinfo/users

>>

>> _______________________________________________

>>

>> users mailing list

>>

>> users@jitsi.org

>>

>> Unsubscribe instructions and other list options:

>>

>> http://lists.jitsi.org/mailman/listinfo/users

>>

>>

>>

>>

>> _______________________________________________

>> users mailing list

>> users@jitsi.org

>> Unsubscribe instructions and other list options:

>> http://lists.jitsi.org/mailman/listinfo/users

>

> _______________________________________________

> users mailing list

> users@jitsi.org

> Unsubscribe instructions and other list options:

> http://lists.jitsi.org/mailman/listinfo/users

> _______________________________________________

> users mailing list

> users@jitsi.org

> Unsubscribe instructions and other list options:

> http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users