[jitsi-dev] Current version in AWS


#1

Hello Jitsi fellows,

I've installed the latest version in an EC2 instance in AWS and it is not working as the early version.

What I used to do was just follow this doc: https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md.

I see that a few configuration files have changed place, but I think it has nothing related to this issue.

Is there something I am missing to make this latest version work in EC2 service?

Thanks

Juliano Medeiros Coimbra, Architect
T: +55.19.3112-1200 ext. 1454
DaitanGroup | www.daitangroup.com<http://www.daitangroup.com/> | Highly Reliable Outsourcing. Value Added Services Worldwide.
Privileged and confidential. If this message has been received in error, please notify sender and delete it immediately.
Conteúdo confidencial. Se esta mensagem foi recebida por engano, favor avisar o remetente e apagá-la.


#2

Hi,

can you give more details, like OS version, what is not working. Did
you check the logs? Any info describing the problem will be useful.
Versions of prosody and nginx, java.

Regards
damencho

···

On Wed, Sep 16, 2015 at 11:34 AM, Juliano Medeiros Coimbra <jcoimbra@daitangroup.com> wrote:

Hello Jitsi fellows,

I've installed the latest version in an EC2 instance in AWS and it is not
working as the early version.

What I used to do was just follow this doc:
https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md.

I see that a few configuration files have changed place, but I think it has
nothing related to this issue.

Is there something I am missing to make this latest version work in EC2
service?

Thanks

Juliano Medeiros Coimbra, Architect
T: +55.19.3112-1200 ext. 1454
DaitanGroup | www.daitangroup.com | Highly Reliable Outsourcing. Value Added
Services Worldwide.
Privileged and confidential. If this message has been received in error,
please notify sender and delete it immediately.
Conteúdo confidencial. Se esta mensagem foi recebida por engano, favor
avisar o remetente e apagá-la.

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


#3

Hello Demencho,

Thanks for your reply. Of course I can :slight_smile:

I am using a c4.large instance with Ubuntu Server 14.04 LTS (HVM), with a magnetic disk of 8GB I also have opened its security group to the world for both TCP and UDP (don't try it at home).

I can see that Jitsi-meet can start a meeting, but when other fellow joins the conference we get a black stream, so I can see myself, but his stream is black (and vice-versa).

My suspicion is that we have no ICE at all.

Lets go to the facts:

# dpkg -l | grep jitsi
ii jitsi-meet 1.0.652-1 all WebRTC JavaScript video conferences
ii jitsi-meet-prosody 1.0.652-1 all Prosody configuration for Jitsi Meet
ii jitsi-videobridge 512-1 amd64 WebRTC compatible Selective Forwarding Unit (SFU)
root@jitsi-dev:~# dpkg -l | grep jicofo
ii jicofo 1.0-134-1 amd64 JItsi Meet COnference FOcus

# dpkg -l | grep libjs-jquery
ii libjs-jquery 2.1.1-1 all JavaScript library for dynamic web applications

I am attaching jicofo.log and jvb.log, let me know if this ok for an analysis.

Thank you!

jicofo.log (8.08 KB)

jvb_log.txt (67.9 KB)

···

________________________________________
De: dev <dev-bounces@jitsi.org> em nome de Damian Minkov <damencho@jitsi.org>
Enviado: quarta-feira, 16 de setembro de 2015 13:39
Para: Jitsi Developers
Assunto: Re: [jitsi-dev] Current version in AWS

Hi,

can you give more details, like OS version, what is not working. Did
you check the logs? Any info describing the problem will be useful.
Versions of prosody and nginx, java.

Regards
damencho

On Wed, Sep 16, 2015 at 11:34 AM, Juliano Medeiros Coimbra <jcoimbra@daitangroup.com> wrote:

Hello Jitsi fellows,

I've installed the latest version in an EC2 instance in AWS and it is not
working as the early version.

What I used to do was just follow this doc:
https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md.

I see that a few configuration files have changed place, but I think it has
nothing related to this issue.

Is there something I am missing to make this latest version work in EC2
service?

Thanks

Juliano Medeiros Coimbra, Architect
T: +55.19.3112-1200 ext. 1454
DaitanGroup | www.daitangroup.com | Highly Reliable Outsourcing. Value Added
Services Worldwide.
Privileged and confidential. If this message has been received in error,
please notify sender and delete it immediately.
Conteúdo confidencial. Se esta mensagem foi recebida por engano, favor
avisar o remetente e apagá-la.

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

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


#4

Hi,

From jvb.log:

java.lang.RuntimeException: java.net.UnknownHostException: ip-172-30-0-155: ip-172-30-0-155: Name or service not known

The hostname of the machine needs to be resolvable. Try adding for example
127.0.0.1 ip-172-30-0-155
in /etc/hosts

Regards,
Boris

···

On 16/09/15 12:21, Juliano Medeiros Coimbra wrote:

Hello Demencho,

Thanks for your reply. Of course I can :slight_smile:

I am using a c4.large instance with Ubuntu Server 14.04 LTS (HVM), with a magnetic disk of 8GB I also have opened its security group to the world for both TCP and UDP (don't try it at home).

I can see that Jitsi-meet can start a meeting, but when other fellow joins the conference we get a black stream, so I can see myself, but his stream is black (and vice-versa).

My suspicion is that we have no ICE at all.

Lets go to the facts:

# dpkg -l | grep jitsi
ii jitsi-meet 1.0.652-1 all WebRTC JavaScript video conferences
ii jitsi-meet-prosody 1.0.652-1 all Prosody configuration for Jitsi Meet
ii jitsi-videobridge 512-1 amd64 WebRTC compatible Selective Forwarding Unit (SFU)
root@jitsi-dev:~# dpkg -l | grep jicofo
ii jicofo 1.0-134-1 amd64 JItsi Meet COnference FOcus

# dpkg -l | grep libjs-jquery
ii libjs-jquery 2.1.1-1 all JavaScript library for dynamic web applications

I am attaching jicofo.log and jvb.log, let me know if this ok for an analysis.

Thank you!

________________________________________
De: dev <dev-bounces@jitsi.org> em nome de Damian Minkov <damencho@jitsi.org>
Enviado: quarta-feira, 16 de setembro de 2015 13:39
Para: Jitsi Developers
Assunto: Re: [jitsi-dev] Current version in AWS

Hi,

can you give more details, like OS version, what is not working. Did
you check the logs? Any info describing the problem will be useful.
Versions of prosody and nginx, java.

Regards
damencho

On Wed, Sep 16, 2015 at 11:34 AM, Juliano Medeiros Coimbra > <jcoimbra@daitangroup.com> wrote:

Hello Jitsi fellows,

I've installed the latest version in an EC2 instance in AWS and it is not
working as the early version.

What I used to do was just follow this doc:
https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md.

I see that a few configuration files have changed place, but I think it has
nothing related to this issue.

Is there something I am missing to make this latest version work in EC2
service?

Thanks

Juliano Medeiros Coimbra, Architect
T: +55.19.3112-1200 ext. 1454
DaitanGroup | www.daitangroup.com | Highly Reliable Outsourcing. Value Added
Services Worldwide.
Privileged and confidential. If this message has been received in error,
please notify sender and delete it immediately.
Conteúdo confidencial. Se esta mensagem foi recebida por engano, favor
avisar o remetente e apagá-la.

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

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

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


#5

Hey, one more thing:

We are trying jitsi-meet withou HTTPS, this is our nginx config:

server_names_hash_bucket_size 64;

server {
    listen 80;
    server_name 192.168.17.44;

    root /usr/share/jitsi-meet;
    index index.html index.htm;

    location /config.js {
        alias /etc/jitsi/meet/192.168.17.44-config.js;
    }

    location ~ ^/([a-zA-Z0-9=\?]+)$ {
        rewrite ^/(.*)$ / break;
    }

    location / {
        ssi on;server {
    listen 443 ssl;
    server_name 192.168.17.44;

    ssl_certificate /var/lib/prosody/<ip_here>.crt;
    ssl_certificate_key /var/lib/prosody/<ip_here>.key;

    root /usr/share/jitsi-meet;
    index index.html index.htm;

    location /config.js {
        alias /etc/jitsi/meet/<ip_here>-config.js;
    }

    location ~ ^/([a-zA-Z0-9=\?]+)$ {
        rewrite ^/(.*)$ / break;
    }

    location / {
        ssi on;
    }

    # BOSH
    location /http-bind {
        proxy_pass http://localhost:5280/http-bind;
        proxy_set_header X-Forwarded-For $remote_addr;
        proxy_set_header Host $http_host;
    }
}

    }

    # BOSH
    location /http-bind {
        proxy_pass http://localhost:5280/http-bind;
        proxy_set_header X-Forwarded-For $remote_addr;
        proxy_set_header Host $http_host;
    }

}

The odd thing is that in my QEMU local instance it is running well even with 1GB and one CPU, also in Ubuntu 14.04.

Thanks

···

________________________________________
De: dev <dev-bounces@jitsi.org> em nome de Juliano Medeiros Coimbra <jcoimbra@daitangroup.com>
Enviado: quarta-feira, 16 de setembro de 2015 14:21
Para: Jitsi Developers
Assunto: Re: [jitsi-dev] Current version in AWS

Hello Demencho,

Thanks for your reply. Of course I can :slight_smile:

I am using a c4.large instance with Ubuntu Server 14.04 LTS (HVM), with a magnetic disk of 8GB I also have opened its security group to the world for both TCP and UDP (don't try it at home).

I can see that Jitsi-meet can start a meeting, but when other fellow joins the conference we get a black stream, so I can see myself, but his stream is black (and vice-versa).

My suspicion is that we have no ICE at all.

Lets go to the facts:

# dpkg -l | grep jitsi
ii jitsi-meet 1.0.652-1 all WebRTC JavaScript video conferences
ii jitsi-meet-prosody 1.0.652-1 all Prosody configuration for Jitsi Meet
ii jitsi-videobridge 512-1 amd64 WebRTC compatible Selective Forwarding Unit (SFU)
root@jitsi-dev:~# dpkg -l | grep jicofo
ii jicofo 1.0-134-1 amd64 JItsi Meet COnference FOcus

# dpkg -l | grep libjs-jquery
ii libjs-jquery 2.1.1-1 all JavaScript library for dynamic web applications

I am attaching jicofo.log and jvb.log, let me know if this ok for an analysis.

Thank you!

________________________________________
De: dev <dev-bounces@jitsi.org> em nome de Damian Minkov <damencho@jitsi.org>
Enviado: quarta-feira, 16 de setembro de 2015 13:39
Para: Jitsi Developers
Assunto: Re: [jitsi-dev] Current version in AWS

Hi,

can you give more details, like OS version, what is not working. Did
you check the logs? Any info describing the problem will be useful.
Versions of prosody and nginx, java.

Regards
damencho

On Wed, Sep 16, 2015 at 11:34 AM, Juliano Medeiros Coimbra <jcoimbra@daitangroup.com> wrote:

Hello Jitsi fellows,

I've installed the latest version in an EC2 instance in AWS and it is not
working as the early version.

What I used to do was just follow this doc:
https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md.

I see that a few configuration files have changed place, but I think it has
nothing related to this issue.

Is there something I am missing to make this latest version work in EC2
service?

Thanks

Juliano Medeiros Coimbra, Architect
T: +55.19.3112-1200 ext. 1454
DaitanGroup | www.daitangroup.com | Highly Reliable Outsourcing. Value Added
Services Worldwide.
Privileged and confidential. If this message has been received in error,
please notify sender and delete it immediately.
Conteúdo confidencial. Se esta mensagem foi recebida por engano, favor
avisar o remetente e apagá-la.

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

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


#6

Hey Boris,

This is the resolution :smiley:

But the line is

127.0.1.1 ip-172-30-0-155

The AWS Private IP!

Thumbs up, +1, thank you!

···

________________________________________
De: dev <dev-bounces@jitsi.org> em nome de Boris Grozev <boris@jitsi.org>
Enviado: quarta-feira, 16 de setembro de 2015 14:41
Para: Jitsi Developers
Assunto: Re: [jitsi-dev] Current version in AWS

Hi,

From jvb.log:

java.lang.RuntimeException: java.net.UnknownHostException:
ip-172-30-0-155: ip-172-30-0-155: Name or service not known

The hostname of the machine needs to be resolvable. Try adding for example
127.0.0.1 ip-172-30-0-155
in /etc/hosts

Regards,
Boris

On 16/09/15 12:21, Juliano Medeiros Coimbra wrote:

Hello Demencho,

Thanks for your reply. Of course I can :slight_smile:

I am using a c4.large instance with Ubuntu Server 14.04 LTS (HVM), with a magnetic disk of 8GB I also have opened its security group to the world for both TCP and UDP (don't try it at home).

I can see that Jitsi-meet can start a meeting, but when other fellow joins the conference we get a black stream, so I can see myself, but his stream is black (and vice-versa).

My suspicion is that we have no ICE at all.

Lets go to the facts:

# dpkg -l | grep jitsi
ii jitsi-meet 1.0.652-1 all WebRTC JavaScript video conferences
ii jitsi-meet-prosody 1.0.652-1 all Prosody configuration for Jitsi Meet
ii jitsi-videobridge 512-1 amd64 WebRTC compatible Selective Forwarding Unit (SFU)
root@jitsi-dev:~# dpkg -l | grep jicofo
ii jicofo 1.0-134-1 amd64 JItsi Meet COnference FOcus

# dpkg -l | grep libjs-jquery
ii libjs-jquery 2.1.1-1 all JavaScript library for dynamic web applications

I am attaching jicofo.log and jvb.log, let me know if this ok for an analysis.

Thank you!

________________________________________
De: dev <dev-bounces@jitsi.org> em nome de Damian Minkov <damencho@jitsi.org>
Enviado: quarta-feira, 16 de setembro de 2015 13:39
Para: Jitsi Developers
Assunto: Re: [jitsi-dev] Current version in AWS

Hi,

can you give more details, like OS version, what is not working. Did
you check the logs? Any info describing the problem will be useful.
Versions of prosody and nginx, java.

Regards
damencho

On Wed, Sep 16, 2015 at 11:34 AM, Juliano Medeiros Coimbra > <jcoimbra@daitangroup.com> wrote:

Hello Jitsi fellows,

I've installed the latest version in an EC2 instance in AWS and it is not
working as the early version.

What I used to do was just follow this doc:
https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md.

I see that a few configuration files have changed place, but I think it has
nothing related to this issue.

Is there something I am missing to make this latest version work in EC2
service?

Thanks

Juliano Medeiros Coimbra, Architect
T: +55.19.3112-1200 ext. 1454
DaitanGroup | www.daitangroup.com | Highly Reliable Outsourcing. Value Added
Services Worldwide.
Privileged and confidential. If this message has been received in error,
please notify sender and delete it immediately.
Conteúdo confidencial. Se esta mensagem foi recebida por engano, favor
avisar o remetente e apagá-la.

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

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

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

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