[jitsi-dev] Problem with Token Mode


#1

Hi All,

I have installed jitsi on Ubuntu 16.04 and configured the token mode as
described here
<https://github.com/jitsi/lib-jitsi-meet/blob/master/doc/tokens.md>. But
when I try to login with a token I cannot login to the conference and
getting following in prosody.log

warn No available SASL mechanisms, verify that the configured

authentication module is working

info BOSH client disconnected

What could be the possible reason ?

package details

- Jitsi meet : 1.0.2098-1
- prosody-trunk : 1nightly786-1~xenial

···

--
*Buddhika Jayawardhana*
Undergraduate | Department of Computer Science & Engineering
University of Moratuwa
*buddhika.anushka@gmail.com <buddhika.12@cse.mrt.ac.lk>* | LinkedIn
<http://lk.linkedin.com/in/buddhikajay/>


#2

Hi,

There are two ways to debug this:

First enable prosody debug log and check.
Search for saslauth, there should be more hints there about the error:
......saslauth debug sasl reply: <failure
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-allowed/><text>Invalid
signature</text></failure>

Secons is to open the js console and check, (I think) the second
http-bind request in Network tab, in the response you should see the
error, something like:
<body sid='7efaaed3-c806-4b7e-92e3-2e2b642b61af'
xmlns:stream='http://etherx.jabber.org/streams'
xmlns='http://jabber.org/protocol/httpbind'><failure
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-allowed/><text>Invalid
signature</text></failure></body>

From those errors, you should have more info what can be the reason.

Regards
damencho

···

On Sun, Jun 4, 2017 at 11:46 AM, Buddhika Jayawardhana <buddhika.anushka@gmail.com> wrote:

Hi All,

I have installed jitsi on Ubuntu 16.04 and configured the token mode as
described here. But when I try to login with a token I cannot login to the
conference and getting following in prosody.log

warn No available SASL mechanisms, verify that the configured
authentication module is working
info BOSH client disconnected

What could be the possible reason ?

package details

- Jitsi meet : 1.0.2098-1
- prosody-trunk : 1nightly786-1~xenial

--
Buddhika Jayawardhana
Undergraduate | Department of Computer Science & Engineering
University of Moratuwa
buddhika.anushka@gmail.com | LinkedIn

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


#3

This is what I get in prosody debug log.

Jun 05 04:51:33 socket debug server.lua: accepted new client connection
from 127.0.0.1:47396 to 5280
Jun 05 04:51:33 http.server debug Firing event: POST
meet2.buddhikajay.pro/http-bind
Jun 05 04:51:33 mod_bosh debug Handling new request table: 0x16869a0: <body
rid='2994510443' xmlns='http://jabber.org/protocol/httpbind' to='
meet2.buddhikajay.pro' xml:lang='en' wait='60' hold='1' content='text/xml;
charset=utf-8' ver='1.6' xmpp:version='1.0' xmlns:xmpp='urn:xmpp:xbosh'/>

···

----------
Jun 05 04:51:33 mod_bosh debug BOSH body open (sid: <none>)
Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 debug BOSH session
created for request from 123.231.126.87
Jun 05 04:51:33 mod_bosh info New BOSH session, assigned it sid
'3eadf41a-80b3-4522-905b-3ae55a4a3050'
Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 warn No available
SASL mechanisms, verify that the configured authentication module is working
Jun 05 04:51:33 mod_bosh debug We have an open request, so sending on that
Jun 05 04:51:33 mod_bosh debug Request destroyed: table: 0x1687440
Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 debug BOSH session
marked as inactive (for 60s)
Jun 05 04:51:33 socket debug server.lua: closed client handler and removed
socket from list
Jun 05 04:51:33 mod_bosh debug Session 3eadf41a-80b3-4522-905b-3ae55a4a3050
has 0 out of 1 requests open
Jun 05 04:51:33 mod_bosh debug and there are 0 things in the send_buffer:
Jun 05 04:51:33 socket debug server.lua: accepted new client connection
from 127.0.0.1:47398 to 5280
Jun 05 04:51:33 http.server debug Firing event: POST
meet2.buddhikajay.pro/http-bind
Jun 05 04:51:33 mod_bosh debug Handling new request table: 0x17ad990: <body
rid='2994510444' xmlns='http://jabber.org/protocol/httpbind'
sid='3eadf41a-80b3-4522-905b-3ae55a4a3050'/>
----------
Jun 05 04:51:33 mod_bosh debug BOSH body open (sid:
3eadf41a-80b3-4522-905b-3ae55a4a3050)
Jun 05 04:51:33 mod_bosh debug Session 3eadf41a-80b3-4522-905b-3ae55a4a3050
has 1 out of 1 requests open
Jun 05 04:51:33 mod_bosh debug and there are 0 things in the send_buffer:
Jun 05 04:51:33 mod_bosh debug Have nothing to say, so leaving request
unanswered for now
Jun 05 04:51:37 jcp14354f0 debug Received[component]: <iq id='1O2He-6728'
type='get' to='meet2.buddhikajay.pro' from='
jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:37 jcp157c5a0 debug Received[component]: <iq id='0fe3g-31648'
type='get' to='meet2.buddhikajay.pro' from='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:37 jcp157c5a0 debug Received[component]: <iq id='0fe3g-31649'
type='get' to='meet2.buddhikajay.pro' from='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31650'
type='get' to='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:39 jcp14354f0 debug Received[component]: <iq id='0fe3g-31650' type='result' to='focus@auth.meet2.buddhikajay.pro/focus3535386783579' from='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31651'
type='get' to='meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31652'
type='get' to='auth.meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31653'
type='get' to='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:39 jcp14354f0 debug Received[component]: <iq id='0fe3g-31653' type='result' to='focus@auth.meet2.buddhikajay.pro/focus3535386783579' from='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31654'
type='get' to='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:39 jcp157c5a0 debug Received[component]: <iq id='0fe3g-31654'
type='result' to='focus@auth.meet2.buddhikajay.pro/focus3535386783579'
from='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31655'
type='get' to='conference.meet2.buddhikajay.pro'>
Jun 05 04:51:47 jcp14354f0 debug Received[component]: <iq id='1O2He-6729'
type='get' to='meet2.buddhikajay.pro' from='
jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:47 jcp157c5a0 debug Received[component]: <iq id='0fe3g-31656'
type='get' to='meet2.buddhikajay.pro' from='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:47 jcp157c5a0 debug Received[component]: <iq id='0fe3g-31657'
type='get' to='meet2.buddhikajay.pro' from='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:49 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31658'
type='get' to='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:49 jcp14354f0 debug Received[component]: <iq id='0fe3g-31658' type='result' to='focus@auth.meet2.buddhikajay.pro/focus3535386783579' from='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:57 jcp14354f0 debug Received[component]: <iq id='1O2He-6730'
type='get' to='meet2.buddhikajay.pro' from='
jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:57 jcp157c5a0 debug Received[component]: <iq id='0fe3g-31659'
type='get' to='meet2.buddhikajay.pro' from='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:57 jcp157c5a0 debug Received[component]: <iq id='0fe3g-31660'
type='get' to='meet2.buddhikajay.pro' from='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:59 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31661'
type='get' to='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:59 jcp14354f0 debug Received[component]: <iq id='0fe3g-31661' type='result' to='focus@auth.meet2.buddhikajay.pro/focus3535386783579' from='jitsi-videobridge.meet2.buddhikajay.pro'>

and the response for second http bind request

<body sid='f4ed6d83-0357-44dc-a351-90cfd020ed47' xmlns:stream='
http://etherx.jabber.org/streams' xmlns='http://jabber.org/protocol/httpbind
'></body>

On Mon, Jun 5, 2017 at 1:30 AM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

There are two ways to debug this:

First enable prosody debug log and check.
Search for saslauth, there should be more hints there about the error:
......saslauth debug sasl reply: <failure
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-allowed/><text>Invalid
signature</text></failure>

Secons is to open the js console and check, (I think) the second
http-bind request in Network tab, in the response you should see the
error, something like:
<body sid='7efaaed3-c806-4b7e-92e3-2e2b642b61af'
xmlns:stream='http://etherx.jabber.org/streams'
xmlns='http://jabber.org/protocol/httpbind'><failure
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-allowed/><text>Invalid
signature</text></failure></body>

From those errors, you should have more info what can be the reason.

Regards
damencho

On Sun, Jun 4, 2017 at 11:46 AM, Buddhika Jayawardhana > <buddhika.anushka@gmail.com> wrote:
> Hi All,
>
> I have installed jitsi on Ubuntu 16.04 and configured the token mode as
> described here. But when I try to login with a token I cannot login to
the
> conference and getting following in prosody.log
>
>>>warn No available SASL mechanisms, verify that the configured
>>> authentication module is working
>>>info BOSH client disconnected
>
>
> What could be the possible reason ?
>
> package details
>
> - Jitsi meet : 1.0.2098-1
> - prosody-trunk : 1nightly786-1~xenial
>
> --
> Buddhika Jayawardhana
> Undergraduate | Department of Computer Science & Engineering
> University of Moratuwa
> buddhika.anushka@gmail.com | LinkedIn
>
> _______________________________________________
> 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

--
*Buddhika Jayawardhana*
Undergraduate | Department of Computer Science & Engineering
University of Moratuwa
*buddhika.anushka@gmail.com <buddhika.12@cse.mrt.ac.lk>* | LinkedIn
<http://lk.linkedin.com/in/buddhikajay/>


#4

When I tried with the token, this is what I get for http-bind request. Some
of the requests timed out.

<body xmlns:stream=‘http://etherx.jabber.org/streams’ xmpp:version=‘1.0’
xmlns:xmpp=‘urn:xmpp:xbosh’ ver=‘1.6’ inactivity=‘60’ requests=‘2’
polling=‘5’ secure=‘true’ hold=‘1’ from=‘meet2.buddhikajay.pro’
authid=‘4d0d7aaf-9fad-4741-be53-d717bba8b560’ wait=‘60’
sid=‘4d0d7aaf-9fad-4741-be53-d717bba8b560’ xmlns=’
http://jabber.org/protocol/httpbind’><stream:features
xmlns=‘jabber:client’><c ver=‘XCD4JZdD+JCFmoCUAznGXZHtGdA=’ hash=‘sha-1’
node=‘http://prosody.im’ xmlns=‘http://jabber.org/protocol/caps’/><starttls
xmlns=‘urn:ietf:params:xml:ns:xmpp-tls’/></stream:features></body>

···

On Mon, Jun 5, 2017 at 10:40 AM, Buddhika Jayawardhana < buddhika.anushka@gmail.com> wrote:

This is what I get in prosody debug log.

Jun 05 04:51:33 socket debug server.lua: accepted new client connection
from 127.0.0.1:47396 to 5280
Jun 05 04:51:33 http.server debug Firing event: POST
meet2.buddhikajay.pro/http-bind
Jun 05 04:51:33 mod_bosh debug Handling new request table: 0x16869a0:
<body rid='2994510443' xmlns='http://jabber.org/protocol/httpbind' to='
meet2.buddhikajay.pro' xml:lang='en' wait='60' hold='1'
content='text/xml; charset=utf-8' ver='1.6' xmpp:version='1.0'
xmlns:xmpp='urn:xmpp:xbosh'/>
----------
Jun 05 04:51:33 mod_bosh debug BOSH body open (sid: <none>)
Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 debug BOSH
session created for request from 123.231.126.87
Jun 05 04:51:33 mod_bosh info New BOSH session, assigned it sid
'3eadf41a-80b3-4522-905b-3ae55a4a3050'
Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 warn No
available SASL mechanisms, verify that the configured authentication module
is working
Jun 05 04:51:33 mod_bosh debug We have an open request, so sending on that
Jun 05 04:51:33 mod_bosh debug Request destroyed: table: 0x1687440
Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 debug BOSH
session marked as inactive (for 60s)
Jun 05 04:51:33 socket debug server.lua: closed client handler and
removed socket from list
Jun 05 04:51:33 mod_bosh debug Session 3eadf41a-80b3-4522-905b-3ae55a4a3050
has 0 out of 1 requests open
Jun 05 04:51:33 mod_bosh debug and there are 0 things in the send_buffer:
Jun 05 04:51:33 socket debug server.lua: accepted new client connection
from 127.0.0.1:47398 to 5280
Jun 05 04:51:33 http.server debug Firing event: POST
meet2.buddhikajay.pro/http-bind
Jun 05 04:51:33 mod_bosh debug Handling new request table: 0x17ad990:
<body rid='2994510444' xmlns='http://jabber.org/protocol/httpbind'
sid='3eadf41a-80b3-4522-905b-3ae55a4a3050'/>
----------
Jun 05 04:51:33 mod_bosh debug BOSH body open (sid:
3eadf41a-80b3-4522-905b-3ae55a4a3050)
Jun 05 04:51:33 mod_bosh debug Session 3eadf41a-80b3-4522-905b-3ae55a4a3050
has 1 out of 1 requests open
Jun 05 04:51:33 mod_bosh debug and there are 0 things in the send_buffer:
Jun 05 04:51:33 mod_bosh debug Have nothing to say, so leaving request
unanswered for now
Jun 05 04:51:37 jcp14354f0 debug Received[component]: <iq id='1O2He-6728'
type='get' to='meet2.buddhikajay.pro' from='jitsi-videobridge.meet2.
buddhikajay.pro'>
Jun 05 04:51:37 jcp157c5a0 debug Received[component]: <iq
id='0fe3g-31648' type='get' to='meet2.buddhikajay.pro' from='
focus.meet2.buddhikajay.pro'>
Jun 05 04:51:37 jcp157c5a0 debug Received[component]: <iq
id='0fe3g-31649' type='get' to='meet2.buddhikajay.pro' from='
focus.meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31650'
type='get' to='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:39 jcp14354f0 debug Received[component]: <iq
id='0fe3g-31650' type='result' to='focus@auth.meet2.buddhikajay.pro/
focus3535386783579' from='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31651'
type='get' to='meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31652'
type='get' to='auth.meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31653'
type='get' to='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:39 jcp14354f0 debug Received[component]: <iq
id='0fe3g-31653' type='result' to='focus@auth.meet2.buddhikajay.pro/
focus3535386783579' from='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31654'
type='get' to='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:39 jcp157c5a0 debug Received[component]: <iq
id='0fe3g-31654' type='result' to='focus@auth.meet2.buddhikajay.pro/
focus3535386783579' from='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31655'
type='get' to='conference.meet2.buddhikajay.pro'>
Jun 05 04:51:47 jcp14354f0 debug Received[component]: <iq id='1O2He-6729'
type='get' to='meet2.buddhikajay.pro' from='jitsi-videobridge.meet2.
buddhikajay.pro'>
Jun 05 04:51:47 jcp157c5a0 debug Received[component]: <iq
id='0fe3g-31656' type='get' to='meet2.buddhikajay.pro' from='
focus.meet2.buddhikajay.pro'>
Jun 05 04:51:47 jcp157c5a0 debug Received[component]: <iq
id='0fe3g-31657' type='get' to='meet2.buddhikajay.pro' from='
focus.meet2.buddhikajay.pro'>
Jun 05 04:51:49 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31658'
type='get' to='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:49 jcp14354f0 debug Received[component]: <iq
id='0fe3g-31658' type='result' to='focus@auth.meet2.buddhikajay.pro/
focus3535386783579' from='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:57 jcp14354f0 debug Received[component]: <iq id='1O2He-6730'
type='get' to='meet2.buddhikajay.pro' from='jitsi-videobridge.meet2.
buddhikajay.pro'>
Jun 05 04:51:57 jcp157c5a0 debug Received[component]: <iq
id='0fe3g-31659' type='get' to='meet2.buddhikajay.pro' from='
focus.meet2.buddhikajay.pro'>
Jun 05 04:51:57 jcp157c5a0 debug Received[component]: <iq
id='0fe3g-31660' type='get' to='meet2.buddhikajay.pro' from='
focus.meet2.buddhikajay.pro'>
Jun 05 04:51:59 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31661'
type='get' to='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:59 jcp14354f0 debug Received[component]: <iq
id='0fe3g-31661' type='result' to='focus@auth.meet2.buddhikajay.pro/
focus3535386783579' from='jitsi-videobridge.meet2.buddhikajay.pro'>

and the response for second http bind request

<body sid='f4ed6d83-0357-44dc-a351-90cfd020ed47' xmlns:stream='
http://etherx.jabber.org/streams' xmlns='http://jabber.org/
protocol/httpbind'></body>

On Mon, Jun 5, 2017 at 1:30 AM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

There are two ways to debug this:

First enable prosody debug log and check.
Search for saslauth, there should be more hints there about the error:
......saslauth debug sasl reply: <failure
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-allowed/><text>Invalid
signature</text></failure>

Secons is to open the js console and check, (I think) the second
http-bind request in Network tab, in the response you should see the
error, something like:
<body sid='7efaaed3-c806-4b7e-92e3-2e2b642b61af'
xmlns:stream='http://etherx.jabber.org/streams'
xmlns='http://jabber.org/protocol/httpbind'><failure
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-allowed/><text>Invalid
signature</text></failure></body>

From those errors, you should have more info what can be the reason.

Regards
damencho

On Sun, Jun 4, 2017 at 11:46 AM, Buddhika Jayawardhana >> <buddhika.anushka@gmail.com> wrote:
> Hi All,
>
> I have installed jitsi on Ubuntu 16.04 and configured the token mode as
> described here. But when I try to login with a token I cannot login to
the
> conference and getting following in prosody.log
>
>>>warn No available SASL mechanisms, verify that the configured
>>> authentication module is working
>>>info BOSH client disconnected
>
>
> What could be the possible reason ?
>
> package details
>
> - Jitsi meet : 1.0.2098-1
> - prosody-trunk : 1nightly786-1~xenial
>
> --
> Buddhika Jayawardhana
> Undergraduate | Department of Computer Science & Engineering
> University of Moratuwa
> buddhika.anushka@gmail.com | LinkedIn
>
> _______________________________________________
> 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

--
*Buddhika Jayawardhana*
Undergraduate | Department of Computer Science & Engineering
University of Moratuwa
*buddhika.anushka@gmail.com <buddhika.12@cse.mrt.ac.lk>* | LinkedIn
<http://lk.linkedin.com/in/buddhikajay/>

--
*Buddhika Jayawardhana*
Undergraduate | Department of Computer Science & Engineering
University of Moratuwa
*buddhika.anushka@gmail.com <buddhika.12@cse.mrt.ac.lk>* | LinkedIn
<http://lk.linkedin.com/in/buddhikajay/>


#5

I don't see any problem in the logs, but there is nothing about token also.
Can you check in your prosody for c2s_require_encryption, this should be false?

···

On Mon, Jun 5, 2017 at 12:45 AM, Buddhika Jayawardhana <buddhika.anushka@gmail.com> wrote:

When I tried with the token, this is what I get for http-bind request. Some
of the requests timed out.

<body xmlns:stream=‘http://etherx.jabber.org/streams’ xmpp:version=‘1.0’
xmlns:xmpp=‘urn:xmpp:xbosh’ ver=‘1.6’ inactivity=‘60’ requests=‘2’
polling=‘5’ secure=‘true’ hold=‘1’ from=‘meet2.buddhikajay.pro’
authid=‘4d0d7aaf-9fad-4741-be53-d717bba8b560’ wait=‘60’
sid=‘4d0d7aaf-9fad-4741-be53-d717bba8b560’
xmlns=‘http://jabber.org/protocol/httpbind’><stream:features
xmlns=‘jabber:client’><c ver=‘XCD4JZdD+JCFmoCUAznGXZHtGdA=’ hash=‘sha-1’
node=‘http://prosody.im’ xmlns=‘http://jabber.org/protocol/caps’/><starttls
xmlns=‘urn:ietf:params:xml:ns:xmpp-tls’/></stream:features></body>

On Mon, Jun 5, 2017 at 10:40 AM, Buddhika Jayawardhana > <buddhika.anushka@gmail.com> wrote:

This is what I get in prosody debug log.

Jun 05 04:51:33 socket debug server.lua: accepted new client connection
from 127.0.0.1:47396 to 5280
Jun 05 04:51:33 http.server debug Firing event: POST
meet2.buddhikajay.pro/http-bind
Jun 05 04:51:33 mod_bosh debug Handling new request table: 0x16869a0:
<body rid='2994510443' xmlns='http://jabber.org/protocol/httpbind'
to='meet2.buddhikajay.pro' xml:lang='en' wait='60' hold='1'
content='text/xml; charset=utf-8' ver='1.6' xmpp:version='1.0'
xmlns:xmpp='urn:xmpp:xbosh'/>
----------
Jun 05 04:51:33 mod_bosh debug BOSH body open (sid: <none>)
Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 debug BOSH
session created for request from 123.231.126.87
Jun 05 04:51:33 mod_bosh info New BOSH session, assigned it sid
'3eadf41a-80b3-4522-905b-3ae55a4a3050'
Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 warn No available
SASL mechanisms, verify that the configured authentication module is working
Jun 05 04:51:33 mod_bosh debug We have an open request, so sending on that
Jun 05 04:51:33 mod_bosh debug Request destroyed: table: 0x1687440
Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 debug BOSH
session marked as inactive (for 60s)
Jun 05 04:51:33 socket debug server.lua: closed client handler and removed
socket from list
Jun 05 04:51:33 mod_bosh debug Session
3eadf41a-80b3-4522-905b-3ae55a4a3050 has 0 out of 1 requests open
Jun 05 04:51:33 mod_bosh debug and there are 0 things in the send_buffer:
Jun 05 04:51:33 socket debug server.lua: accepted new client connection
from 127.0.0.1:47398 to 5280
Jun 05 04:51:33 http.server debug Firing event: POST
meet2.buddhikajay.pro/http-bind
Jun 05 04:51:33 mod_bosh debug Handling new request table: 0x17ad990:
<body rid='2994510444' xmlns='http://jabber.org/protocol/httpbind'
sid='3eadf41a-80b3-4522-905b-3ae55a4a3050'/>
----------
Jun 05 04:51:33 mod_bosh debug BOSH body open (sid:
3eadf41a-80b3-4522-905b-3ae55a4a3050)
Jun 05 04:51:33 mod_bosh debug Session
3eadf41a-80b3-4522-905b-3ae55a4a3050 has 1 out of 1 requests open
Jun 05 04:51:33 mod_bosh debug and there are 0 things in the send_buffer:
Jun 05 04:51:33 mod_bosh debug Have nothing to say, so leaving request
unanswered for now
Jun 05 04:51:37 jcp14354f0 debug Received[component]: <iq id='1O2He-6728'
type='get' to='meet2.buddhikajay.pro'
from='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:37 jcp157c5a0 debug Received[component]: <iq id='0fe3g-31648'
type='get' to='meet2.buddhikajay.pro' from='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:37 jcp157c5a0 debug Received[component]: <iq id='0fe3g-31649'
type='get' to='meet2.buddhikajay.pro' from='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31650'
type='get' to='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:39 jcp14354f0 debug Received[component]: <iq id='0fe3g-31650'
type='result' to='focus@auth.meet2.buddhikajay.pro/focus3535386783579'
from='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31651'
type='get' to='meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31652'
type='get' to='auth.meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31653'
type='get' to='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:39 jcp14354f0 debug Received[component]: <iq id='0fe3g-31653'
type='result' to='focus@auth.meet2.buddhikajay.pro/focus3535386783579'
from='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31654'
type='get' to='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:39 jcp157c5a0 debug Received[component]: <iq id='0fe3g-31654'
type='result' to='focus@auth.meet2.buddhikajay.pro/focus3535386783579'
from='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31655'
type='get' to='conference.meet2.buddhikajay.pro'>
Jun 05 04:51:47 jcp14354f0 debug Received[component]: <iq id='1O2He-6729'
type='get' to='meet2.buddhikajay.pro'
from='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:47 jcp157c5a0 debug Received[component]: <iq id='0fe3g-31656'
type='get' to='meet2.buddhikajay.pro' from='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:47 jcp157c5a0 debug Received[component]: <iq id='0fe3g-31657'
type='get' to='meet2.buddhikajay.pro' from='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:49 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31658'
type='get' to='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:49 jcp14354f0 debug Received[component]: <iq id='0fe3g-31658'
type='result' to='focus@auth.meet2.buddhikajay.pro/focus3535386783579'
from='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:57 jcp14354f0 debug Received[component]: <iq id='1O2He-6730'
type='get' to='meet2.buddhikajay.pro'
from='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:57 jcp157c5a0 debug Received[component]: <iq id='0fe3g-31659'
type='get' to='meet2.buddhikajay.pro' from='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:57 jcp157c5a0 debug Received[component]: <iq id='0fe3g-31660'
type='get' to='meet2.buddhikajay.pro' from='focus.meet2.buddhikajay.pro'>
Jun 05 04:51:59 c2s15e7e00 debug Received[c2s]: <iq id='0fe3g-31661'
type='get' to='jitsi-videobridge.meet2.buddhikajay.pro'>
Jun 05 04:51:59 jcp14354f0 debug Received[component]: <iq id='0fe3g-31661'
type='result' to='focus@auth.meet2.buddhikajay.pro/focus3535386783579'
from='jitsi-videobridge.meet2.buddhikajay.pro'>

and the response for second http bind request

<body sid='f4ed6d83-0357-44dc-a351-90cfd020ed47'
xmlns:stream='http://etherx.jabber.org/streams'
xmlns='http://jabber.org/protocol/httpbind'></body>

On Mon, Jun 5, 2017 at 1:30 AM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

There are two ways to debug this:

First enable prosody debug log and check.
Search for saslauth, there should be more hints there about the error:
......saslauth debug sasl reply: <failure
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-allowed/><text>Invalid
signature</text></failure>

Secons is to open the js console and check, (I think) the second
http-bind request in Network tab, in the response you should see the
error, something like:
<body sid='7efaaed3-c806-4b7e-92e3-2e2b642b61af'
xmlns:stream='http://etherx.jabber.org/streams'
xmlns='http://jabber.org/protocol/httpbind'><failure
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-allowed/><text>Invalid
signature</text></failure></body>

From those errors, you should have more info what can be the reason.

Regards
damencho

On Sun, Jun 4, 2017 at 11:46 AM, Buddhika Jayawardhana >>> <buddhika.anushka@gmail.com> wrote:
> Hi All,
>
> I have installed jitsi on Ubuntu 16.04 and configured the token mode as
> described here. But when I try to login with a token I cannot login to
> the
> conference and getting following in prosody.log
>
>>>warn No available SASL mechanisms, verify that the configured
>>> authentication module is working
>>>info BOSH client disconnected
>
>
> What could be the possible reason ?
>
> package details
>
> - Jitsi meet : 1.0.2098-1
> - prosody-trunk : 1nightly786-1~xenial
>
> --
> Buddhika Jayawardhana
> Undergraduate | Department of Computer Science & Engineering
> University of Moratuwa
> buddhika.anushka@gmail.com | LinkedIn
>
> _______________________________________________
> 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

--
Buddhika Jayawardhana
Undergraduate | Department of Computer Science & Engineering
University of Moratuwa
buddhika.anushka@gmail.com | LinkedIn

--
Buddhika Jayawardhana
Undergraduate | Department of Computer Science & Engineering
University of Moratuwa
buddhika.anushka@gmail.com | LinkedIn

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


#6

Hi Damian,
Yes it is set to false. I found this error in prosody.err

/usr/lib/prosody/core/modulemanager.lua:77: in function '?'
/usr/lib/prosody/util/events.lua:78: in function
</usr/lib/prosody/util/events.lua:74>
(tail call): ?
/usr/lib/prosody/core/hostmanager.lua:104: in function 'activate'
/usr/lib/prosody/core/hostmanager.lua:57: in function '?'
/usr/lib/prosody/util/events.lua:78: in function
</usr/lib/prosody/util/events.lua:74>
(tail call): ?
/usr/bin/prosody:352: in function 'prepare_to_start'
/usr/bin/prosody:421: in main chunk
[C]: ?

Any tip to track down the error ?

···

On Mon, Jun 5, 2017 at 7:08 PM, Damian Minkov <damencho@jitsi.org> wrote:

I don't see any problem in the logs, but there is nothing about token also.
Can you check in your prosody for c2s_require_encryption, this should be
false?

On Mon, Jun 5, 2017 at 12:45 AM, Buddhika Jayawardhana > <buddhika.anushka@gmail.com> wrote:
> When I tried with the token, this is what I get for http-bind request.
Some
> of the requests timed out.
>
> <body xmlns:stream=‘http://etherx.jabber.org/streams’ xmpp:version=‘1.0’
> xmlns:xmpp=‘urn:xmpp:xbosh’ ver=‘1.6’ inactivity=‘60’ requests=‘2’
> polling=‘5’ secure=‘true’ hold=‘1’ from=‘meet2.buddhikajay.pro’
> authid=‘4d0d7aaf-9fad-4741-be53-d717bba8b560’ wait=‘60’
> sid=‘4d0d7aaf-9fad-4741-be53-d717bba8b560’
> xmlns=‘http://jabber.org/protocol/httpbind’><stream:features
> xmlns=‘jabber:client’><c ver=‘XCD4JZdD+JCFmoCUAznGXZHtGdA=’ hash=‘sha-1’
> node=‘http://prosody.im’ xmlns=‘http://jabber.org/protocol/caps’/
><starttls
> xmlns=‘urn:ietf:params:xml:ns:xmpp-tls’/></stream:features></body>
>
> On Mon, Jun 5, 2017 at 10:40 AM, Buddhika Jayawardhana > > <buddhika.anushka@gmail.com> wrote:
>>
>> This is what I get in prosody debug log.
>>
>> Jun 05 04:51:33 socket debug server.lua: accepted new client connection
>> from 127.0.0.1:47396 to 5280
>> Jun 05 04:51:33 http.server debug Firing event: POST
>> meet2.buddhikajay.pro/http-bind
>> Jun 05 04:51:33 mod_bosh debug Handling new request table: 0x16869a0:
>> <body rid=‘2994510443’ xmlns=‘http://jabber.org/protocol/httpbind
>> to=‘meet2.buddhikajay.pro’ xml:lang=‘en’ wait=‘60’ hold=‘1’
>> content=‘text/xml; charset=utf-8’ ver=‘1.6’ xmpp:version=‘1.0’
>> xmlns:xmpp=‘urn:xmpp:xbosh’/>
>> ----------
>> Jun 05 04:51:33 mod_bosh debug BOSH body open (sid: <none>)
>> Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 debug BOSH
>> session created for request from 123.231.126.87
>> Jun 05 04:51:33 mod_bosh info New BOSH session, assigned it sid
>> ‘3eadf41a-80b3-4522-905b-3ae55a4a3050’
>> Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 warn No
available
>> SASL mechanisms, verify that the configured authentication module is
working
>> Jun 05 04:51:33 mod_bosh debug We have an open request, so sending on
that
>> Jun 05 04:51:33 mod_bosh debug Request destroyed: table: 0x1687440
>> Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 debug BOSH
>> session marked as inactive (for 60s)
>> Jun 05 04:51:33 socket debug server.lua: closed client handler and
removed
>> socket from list
>> Jun 05 04:51:33 mod_bosh debug Session
>> 3eadf41a-80b3-4522-905b-3ae55a4a3050 has 0 out of 1 requests open
>> Jun 05 04:51:33 mod_bosh debug and there are 0 things in the
send_buffer:
>> Jun 05 04:51:33 socket debug server.lua: accepted new client connection
>> from 127.0.0.1:47398 to 5280
>> Jun 05 04:51:33 http.server debug Firing event: POST
>> meet2.buddhikajay.pro/http-bind
>> Jun 05 04:51:33 mod_bosh debug Handling new request table: 0x17ad990:
>> <body rid=‘2994510444’ xmlns=‘http://jabber.org/protocol/httpbind
>> sid=‘3eadf41a-80b3-4522-905b-3ae55a4a3050’/>
>> ----------
>> Jun 05 04:51:33 mod_bosh debug BOSH body open (sid:
>> 3eadf41a-80b3-4522-905b-3ae55a4a3050)
>> Jun 05 04:51:33 mod_bosh debug Session
>> 3eadf41a-80b3-4522-905b-3ae55a4a3050 has 1 out of 1 requests open
>> Jun 05 04:51:33 mod_bosh debug and there are 0 things in the
send_buffer:
>> Jun 05 04:51:33 mod_bosh debug Have nothing to say, so leaving request
>> unanswered for now
>> Jun 05 04:51:37 jcp14354f0 debug Received[component]: <iq
id=‘1O2He-6728’
>> type=‘get’ to=‘meet2.buddhikajay.pro’
>> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:37 jcp157c5a0 debug Received[component]: <iq
id=‘0fe3g-31648’
>> type=‘get’ to=‘meet2.buddhikajay.pro’ from='focus.meet2.buddhikajay.pro
'>
>> Jun 05 04:51:37 jcp157c5a0 debug Received[component]: <iq
id=‘0fe3g-31649’
>> type=‘get’ to=‘meet2.buddhikajay.pro’ from='focus.meet2.buddhikajay.pro
'>
>> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31650’
>> type=‘get’ to=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 jcp14354f0 debug Received[component]: <iq
id=‘0fe3g-31650’
>> type=‘result’ to=‘focus@auth.meet2.buddhikajay.pro/focus3535386783579’
>> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31651’
>> type=‘get’ to=‘meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31652’
>> type=‘get’ to=‘auth.meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31653’
>> type=‘get’ to=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 jcp14354f0 debug Received[component]: <iq
id=‘0fe3g-31653’
>> type=‘result’ to=‘focus@auth.meet2.buddhikajay.pro/focus3535386783579’
>> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31654’
>> type=‘get’ to=‘focus.meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 jcp157c5a0 debug Received[component]: <iq
id=‘0fe3g-31654’
>> type=‘result’ to=‘focus@auth.meet2.buddhikajay.pro/focus3535386783579’
>> from=‘focus.meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31655’
>> type=‘get’ to=‘conference.meet2.buddhikajay.pro’>
>> Jun 05 04:51:47 jcp14354f0 debug Received[component]: <iq
id=‘1O2He-6729’
>> type=‘get’ to=‘meet2.buddhikajay.pro’
>> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:47 jcp157c5a0 debug Received[component]: <iq
id=‘0fe3g-31656’
>> type=‘get’ to=‘meet2.buddhikajay.pro’ from='focus.meet2.buddhikajay.pro
'>
>> Jun 05 04:51:47 jcp157c5a0 debug Received[component]: <iq
id=‘0fe3g-31657’
>> type=‘get’ to=‘meet2.buddhikajay.pro’ from='focus.meet2.buddhikajay.pro
'>
>> Jun 05 04:51:49 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31658’
>> type=‘get’ to=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:49 jcp14354f0 debug Received[component]: <iq
id=‘0fe3g-31658’
>> type=‘result’ to=‘focus@auth.meet2.buddhikajay.pro/focus3535386783579’
>> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:57 jcp14354f0 debug Received[component]: <iq
id=‘1O2He-6730’
>> type=‘get’ to=‘meet2.buddhikajay.pro’
>> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:57 jcp157c5a0 debug Received[component]: <iq
id=‘0fe3g-31659’
>> type=‘get’ to=‘meet2.buddhikajay.pro’ from='focus.meet2.buddhikajay.pro
'>
>> Jun 05 04:51:57 jcp157c5a0 debug Received[component]: <iq
id=‘0fe3g-31660’
>> type=‘get’ to=‘meet2.buddhikajay.pro’ from='focus.meet2.buddhikajay.pro
'>
>> Jun 05 04:51:59 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31661’
>> type=‘get’ to=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:59 jcp14354f0 debug Received[component]: <iq
id=‘0fe3g-31661’
>> type=‘result’ to=‘focus@auth.meet2.buddhikajay.pro/focus3535386783579’
>> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>>
>> and the response for second http bind request
>>
>> <body sid=‘f4ed6d83-0357-44dc-a351-90cfd020ed47’
>> xmlns:stream=‘http://etherx.jabber.org/streams
>> xmlns=‘http://jabber.org/protocol/httpbind’></body>
>>
>> On Mon, Jun 5, 2017 at 1:30 AM, Damian Minkov <damencho@jitsi.org> > wrote:
>>>
>>> Hi,
>>>
>>> There are two ways to debug this:
>>>
>>> First enable prosody debug log and check.
>>> Search for saslauth, there should be more hints there about the error:
>>> ......saslauth debug sasl reply: <failure
>>> xmlns=‘urn:ietf:params:xml:ns:xmpp-sasl’><not-allowed/><text>Invalid
>>> signature</text></failure>
>>>
>>> Secons is to open the js console and check, (I think) the second
>>> http-bind request in Network tab, in the response you should see the
>>> error, something like:
>>> <body sid=‘7efaaed3-c806-4b7e-92e3-2e2b642b61af’
>>> xmlns:stream=‘http://etherx.jabber.org/streams
>>> xmlns=‘http://jabber.org/protocol/httpbind’><failure
>>> xmlns=‘urn:ietf:params:xml:ns:xmpp-sasl’><not-allowed/><text>Invalid
>>> signature</text></failure></body>
>>>
>>> From those errors, you should have more info what can be the reason.
>>>
>>> Regards
>>> damencho
>>>
>>>
>>> On Sun, Jun 4, 2017 at 11:46 AM, Buddhika Jayawardhana > >>> <buddhika.anushka@gmail.com> wrote:
>>> > Hi All,
>>> >
>>> > I have installed jitsi on Ubuntu 16.04 and configured the token mode
as
>>> > described here. But when I try to login with a token I cannot login
to
>>> > the
>>> > conference and getting following in prosody.log
>>> >
>>> >>>warn No available SASL mechanisms, verify that the configured
>>> >>> authentication module is working
>>> >>>info BOSH client disconnected
>>> >
>>> >
>>> > What could be the possible reason ?
>>> >
>>> > package details
>>> >
>>> > - Jitsi meet : 1.0.2098-1
>>> > - prosody-trunk : 1nightly786-1~xenial
>>> >
>>> > --
>>> > Buddhika Jayawardhana
>>> > Undergraduate | Department of Computer Science & Engineering
>>> > University of Moratuwa
>>> > buddhika.anushka@gmail.com | LinkedIn
>>> >
>>> > _______________________________________________
>>> > 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
>>
>>
>>
>>
>> --
>> Buddhika Jayawardhana
>> Undergraduate | Department of Computer Science & Engineering
>> University of Moratuwa
>> buddhika.anushka@gmail.com | LinkedIn
>
>
>
>
> --
> Buddhika Jayawardhana
> Undergraduate | Department of Computer Science & Engineering
> University of Moratuwa
> buddhika.anushka@gmail.com | LinkedIn
>
> _______________________________________________
> 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

--
*Buddhika Jayawardhana*
Undergraduate | Department of Computer Science & Engineering
University of Moratuwa
*buddhika.anushka@gmail.com <buddhika.12@cse.mrt.ac.lk>* | LinkedIn
<http://lk.linkedin.com/in/buddhikajay/>


#7

Hi,

If this is the whole error stack, I haven't seen it and it is not in
our code, so I have no idea. You can check what is the code
prosody/core/modulemanager.lua on line 77 and maybe you can have an
idea what may be wrong.

Regards
damencho

···

On Tue, Jun 6, 2017 at 8:03 AM, Buddhika Jayawardhana <buddhika.anushka@gmail.com> wrote:

Hi Damian,
Yes it is set to false. I found this error in prosody.err

/usr/lib/prosody/core/modulemanager.lua:77: in function '?'
/usr/lib/prosody/util/events.lua:78: in function
</usr/lib/prosody/util/events.lua:74>
(tail call): ?
/usr/lib/prosody/core/hostmanager.lua:104: in function 'activate'
/usr/lib/prosody/core/hostmanager.lua:57: in function '?'
/usr/lib/prosody/util/events.lua:78: in function
</usr/lib/prosody/util/events.lua:74>
(tail call): ?
/usr/bin/prosody:352: in function 'prepare_to_start'
/usr/bin/prosody:421: in main chunk
[C]: ?

Any tip to track down the error ?

On Mon, Jun 5, 2017 at 7:08 PM, Damian Minkov <damencho@jitsi.org> wrote:

I don't see any problem in the logs, but there is nothing about token
also.
Can you check in your prosody for c2s_require_encryption, this should be
false?

On Mon, Jun 5, 2017 at 12:45 AM, Buddhika Jayawardhana >> <buddhika.anushka@gmail.com> wrote:
> When I tried with the token, this is what I get for http-bind request.
> Some
> of the requests timed out.
>
> <body xmlns:stream=‘http://etherx.jabber.org/streams’ xmpp:version=‘1.0’
> xmlns:xmpp=‘urn:xmpp:xbosh’ ver=‘1.6’ inactivity=‘60’ requests=‘2’
> polling=‘5’ secure=‘true’ hold=‘1’ from=‘meet2.buddhikajay.pro’
> authid=‘4d0d7aaf-9fad-4741-be53-d717bba8b560’ wait=‘60’
> sid=‘4d0d7aaf-9fad-4741-be53-d717bba8b560’
> xmlns=‘http://jabber.org/protocol/httpbind’><stream:features
> xmlns=‘jabber:client’><c ver=‘XCD4JZdD+JCFmoCUAznGXZHtGdA=’ hash=‘sha-1’
> node=‘http://prosody.im
> xmlns=‘http://jabber.org/protocol/caps’/><starttls
> xmlns=‘urn:ietf:params:xml:ns:xmpp-tls’/></stream:features></body>
>
> On Mon, Jun 5, 2017 at 10:40 AM, Buddhika Jayawardhana >> > <buddhika.anushka@gmail.com> wrote:
>>
>> This is what I get in prosody debug log.
>>
>> Jun 05 04:51:33 socket debug server.lua: accepted new client connection
>> from 127.0.0.1:47396 to 5280
>> Jun 05 04:51:33 http.server debug Firing event: POST
>> meet2.buddhikajay.pro/http-bind
>> Jun 05 04:51:33 mod_bosh debug Handling new request table: 0x16869a0:
>> <body rid=‘2994510443’ xmlns=‘http://jabber.org/protocol/httpbind
>> to=‘meet2.buddhikajay.pro’ xml:lang=‘en’ wait=‘60’ hold=‘1’
>> content=‘text/xml; charset=utf-8’ ver=‘1.6’ xmpp:version=‘1.0’
>> xmlns:xmpp=‘urn:xmpp:xbosh’/>
>> ----------
>> Jun 05 04:51:33 mod_bosh debug BOSH body open (sid: <none>)
>> Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 debug BOSH
>> session created for request from 123.231.126.87
>> Jun 05 04:51:33 mod_bosh info New BOSH session, assigned it sid
>> ‘3eadf41a-80b3-4522-905b-3ae55a4a3050’
>> Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 warn No
>> available
>> SASL mechanisms, verify that the configured authentication module is
>> working
>> Jun 05 04:51:33 mod_bosh debug We have an open request, so sending on
>> that
>> Jun 05 04:51:33 mod_bosh debug Request destroyed: table: 0x1687440
>> Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 debug BOSH
>> session marked as inactive (for 60s)
>> Jun 05 04:51:33 socket debug server.lua: closed client handler and
>> removed
>> socket from list
>> Jun 05 04:51:33 mod_bosh debug Session
>> 3eadf41a-80b3-4522-905b-3ae55a4a3050 has 0 out of 1 requests open
>> Jun 05 04:51:33 mod_bosh debug and there are 0 things in the
>> send_buffer:
>> Jun 05 04:51:33 socket debug server.lua: accepted new client connection
>> from 127.0.0.1:47398 to 5280
>> Jun 05 04:51:33 http.server debug Firing event: POST
>> meet2.buddhikajay.pro/http-bind
>> Jun 05 04:51:33 mod_bosh debug Handling new request table: 0x17ad990:
>> <body rid=‘2994510444’ xmlns=‘http://jabber.org/protocol/httpbind
>> sid=‘3eadf41a-80b3-4522-905b-3ae55a4a3050’/>
>> ----------
>> Jun 05 04:51:33 mod_bosh debug BOSH body open (sid:
>> 3eadf41a-80b3-4522-905b-3ae55a4a3050)
>> Jun 05 04:51:33 mod_bosh debug Session
>> 3eadf41a-80b3-4522-905b-3ae55a4a3050 has 1 out of 1 requests open
>> Jun 05 04:51:33 mod_bosh debug and there are 0 things in the
>> send_buffer:
>> Jun 05 04:51:33 mod_bosh debug Have nothing to say, so leaving request
>> unanswered for now
>> Jun 05 04:51:37 jcp14354f0 debug Received[component]: <iq
>> id=‘1O2He-6728’
>> type=‘get’ to=‘meet2.buddhikajay.pro’
>> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:37 jcp157c5a0 debug Received[component]: <iq
>> id=‘0fe3g-31648’
>> type=‘get’ to=‘meet2.buddhikajay.pro’
>> from=‘focus.meet2.buddhikajay.pro’>
>> Jun 05 04:51:37 jcp157c5a0 debug Received[component]: <iq
>> id=‘0fe3g-31649’
>> type=‘get’ to=‘meet2.buddhikajay.pro’
>> from=‘focus.meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31650’
>> type=‘get’ to=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 jcp14354f0 debug Received[component]: <iq
>> id=‘0fe3g-31650’
>> type=‘result’ to=‘focus@auth.meet2.buddhikajay.pro/focus3535386783579’
>> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31651’
>> type=‘get’ to=‘meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31652’
>> type=‘get’ to=‘auth.meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31653’
>> type=‘get’ to=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 jcp14354f0 debug Received[component]: <iq
>> id=‘0fe3g-31653’
>> type=‘result’ to=‘focus@auth.meet2.buddhikajay.pro/focus3535386783579’
>> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31654’
>> type=‘get’ to=‘focus.meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 jcp157c5a0 debug Received[component]: <iq
>> id=‘0fe3g-31654’
>> type=‘result’ to=‘focus@auth.meet2.buddhikajay.pro/focus3535386783579’
>> from=‘focus.meet2.buddhikajay.pro’>
>> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31655’
>> type=‘get’ to=‘conference.meet2.buddhikajay.pro’>
>> Jun 05 04:51:47 jcp14354f0 debug Received[component]: <iq
>> id=‘1O2He-6729’
>> type=‘get’ to=‘meet2.buddhikajay.pro’
>> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:47 jcp157c5a0 debug Received[component]: <iq
>> id=‘0fe3g-31656’
>> type=‘get’ to=‘meet2.buddhikajay.pro’
>> from=‘focus.meet2.buddhikajay.pro’>
>> Jun 05 04:51:47 jcp157c5a0 debug Received[component]: <iq
>> id=‘0fe3g-31657’
>> type=‘get’ to=‘meet2.buddhikajay.pro’
>> from=‘focus.meet2.buddhikajay.pro’>
>> Jun 05 04:51:49 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31658’
>> type=‘get’ to=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:49 jcp14354f0 debug Received[component]: <iq
>> id=‘0fe3g-31658’
>> type=‘result’ to=‘focus@auth.meet2.buddhikajay.pro/focus3535386783579’
>> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:57 jcp14354f0 debug Received[component]: <iq
>> id=‘1O2He-6730’
>> type=‘get’ to=‘meet2.buddhikajay.pro’
>> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:57 jcp157c5a0 debug Received[component]: <iq
>> id=‘0fe3g-31659’
>> type=‘get’ to=‘meet2.buddhikajay.pro’
>> from=‘focus.meet2.buddhikajay.pro’>
>> Jun 05 04:51:57 jcp157c5a0 debug Received[component]: <iq
>> id=‘0fe3g-31660’
>> type=‘get’ to=‘meet2.buddhikajay.pro’
>> from=‘focus.meet2.buddhikajay.pro’>
>> Jun 05 04:51:59 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31661’
>> type=‘get’ to=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> Jun 05 04:51:59 jcp14354f0 debug Received[component]: <iq
>> id=‘0fe3g-31661’
>> type=‘result’ to=‘focus@auth.meet2.buddhikajay.pro/focus3535386783579’
>> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>>
>> and the response for second http bind request
>>
>> <body sid=‘f4ed6d83-0357-44dc-a351-90cfd020ed47’
>> xmlns:stream=‘http://etherx.jabber.org/streams
>> xmlns=‘http://jabber.org/protocol/httpbind’></body>
>>
>> On Mon, Jun 5, 2017 at 1:30 AM, Damian Minkov <damencho@jitsi.org> >> >> wrote:
>>>
>>> Hi,
>>>
>>> There are two ways to debug this:
>>>
>>> First enable prosody debug log and check.
>>> Search for saslauth, there should be more hints there about the error:
>>> ......saslauth debug sasl reply: <failure
>>> xmlns=‘urn:ietf:params:xml:ns:xmpp-sasl’><not-allowed/><text>Invalid
>>> signature</text></failure>
>>>
>>> Secons is to open the js console and check, (I think) the second
>>> http-bind request in Network tab, in the response you should see the
>>> error, something like:
>>> <body sid=‘7efaaed3-c806-4b7e-92e3-2e2b642b61af’
>>> xmlns:stream=‘http://etherx.jabber.org/streams
>>> xmlns=‘http://jabber.org/protocol/httpbind’><failure
>>> xmlns=‘urn:ietf:params:xml:ns:xmpp-sasl’><not-allowed/><text>Invalid
>>> signature</text></failure></body>
>>>
>>> From those errors, you should have more info what can be the reason.
>>>
>>> Regards
>>> damencho
>>>
>>>
>>> On Sun, Jun 4, 2017 at 11:46 AM, Buddhika Jayawardhana >> >>> <buddhika.anushka@gmail.com> wrote:
>>> > Hi All,
>>> >
>>> > I have installed jitsi on Ubuntu 16.04 and configured the token mode
>>> > as
>>> > described here. But when I try to login with a token I cannot login
>>> > to
>>> > the
>>> > conference and getting following in prosody.log
>>> >
>>> >>>warn No available SASL mechanisms, verify that the configured
>>> >>> authentication module is working
>>> >>>info BOSH client disconnected
>>> >
>>> >
>>> > What could be the possible reason ?
>>> >
>>> > package details
>>> >
>>> > - Jitsi meet : 1.0.2098-1
>>> > - prosody-trunk : 1nightly786-1~xenial
>>> >
>>> > --
>>> > Buddhika Jayawardhana
>>> > Undergraduate | Department of Computer Science & Engineering
>>> > University of Moratuwa
>>> > buddhika.anushka@gmail.com | LinkedIn
>>> >
>>> > _______________________________________________
>>> > 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
>>
>>
>>
>>
>> --
>> Buddhika Jayawardhana
>> Undergraduate | Department of Computer Science & Engineering
>> University of Moratuwa
>> buddhika.anushka@gmail.com | LinkedIn
>
>
>
>
> --
> Buddhika Jayawardhana
> Undergraduate | Department of Computer Science & Engineering
> University of Moratuwa
> buddhika.anushka@gmail.com | LinkedIn
>
> _______________________________________________
> 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

--
Buddhika Jayawardhana
Undergraduate | Department of Computer Science & Engineering
University of Moratuwa
buddhika.anushka@gmail.com | LinkedIn

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


#8

Thanks Damian.

···

On Tue, Jun 6, 2017 at 7:58 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

If this is the whole error stack, I haven't seen it and it is not in
our code, so I have no idea. You can check what is the code
prosody/core/modulemanager.lua on line 77 and maybe you can have an
idea what may be wrong.

Regards
damencho

On Tue, Jun 6, 2017 at 8:03 AM, Buddhika Jayawardhana > <buddhika.anushka@gmail.com> wrote:
> Hi Damian,
> Yes it is set to false. I found this error in prosody.err
>
> /usr/lib/prosody/core/modulemanager.lua:77: in function ‘?’
> /usr/lib/prosody/util/events.lua:78: in function
> </usr/lib/prosody/util/events.lua:74>
> (tail call): ?
> /usr/lib/prosody/core/hostmanager.lua:104: in function ‘activate’
> /usr/lib/prosody/core/hostmanager.lua:57: in function ‘?’
> /usr/lib/prosody/util/events.lua:78: in function
> </usr/lib/prosody/util/events.lua:74>
> (tail call): ?
> /usr/bin/prosody:352: in function ‘prepare_to_start’
> /usr/bin/prosody:421: in main chunk
> [C]: ?
>
> Any tip to track down the error ?
>
>
> On Mon, Jun 5, 2017 at 7:08 PM, Damian Minkov <damencho@jitsi.org> > wrote:
>>
>> I don’t see any problem in the logs, but there is nothing about token
>> also.
>> Can you check in your prosody for c2s_require_encryption, this should be
>> false?
>>
>> On Mon, Jun 5, 2017 at 12:45 AM, Buddhika Jayawardhana > >> <buddhika.anushka@gmail.com> wrote:
>> > When I tried with the token, this is what I get for http-bind request.
>> > Some
>> > of the requests timed out.
>> >
>> > <body xmlns:stream=‘http://etherx.jabber.org/streams
xmpp:version=‘1.0’
>> > xmlns:xmpp=‘urn:xmpp:xbosh’ ver=‘1.6’ inactivity=‘60’ requests=‘2’
>> > polling=‘5’ secure=‘true’ hold=‘1’ from=‘meet2.buddhikajay.pro’
>> > authid=‘4d0d7aaf-9fad-4741-be53-d717bba8b560’ wait=‘60’
>> > sid=‘4d0d7aaf-9fad-4741-be53-d717bba8b560’
>> > xmlns=‘http://jabber.org/protocol/httpbind’><stream:features
>> > xmlns=‘jabber:client’><c ver=‘XCD4JZdD+JCFmoCUAznGXZHtGdA=’
hash=‘sha-1’
>> > node=‘http://prosody.im
>> > xmlns=‘http://jabber.org/protocol/caps’/><starttls
>> > xmlns=‘urn:ietf:params:xml:ns:xmpp-tls’/></stream:features></body>
>> >
>> > On Mon, Jun 5, 2017 at 10:40 AM, Buddhika Jayawardhana > >> > <buddhika.anushka@gmail.com> wrote:
>> >>
>> >> This is what I get in prosody debug log.
>> >>
>> >> Jun 05 04:51:33 socket debug server.lua: accepted new client
connection
>> >> from 127.0.0.1:47396 to 5280
>> >> Jun 05 04:51:33 http.server debug Firing event: POST
>> >> meet2.buddhikajay.pro/http-bind
>> >> Jun 05 04:51:33 mod_bosh debug Handling new request table: 0x16869a0:
>> >> <body rid=‘2994510443’ xmlns=‘http://jabber.org/protocol/httpbind
>> >> to=‘meet2.buddhikajay.pro’ xml:lang=‘en’ wait=‘60’ hold=‘1’
>> >> content=‘text/xml; charset=utf-8’ ver=‘1.6’ xmpp:version=‘1.0’
>> >> xmlns:xmpp=‘urn:xmpp:xbosh’/>
>> >> ----------
>> >> Jun 05 04:51:33 mod_bosh debug BOSH body open (sid: <none>)
>> >> Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 debug BOSH
>> >> session created for request from 123.231.126.87
>> >> Jun 05 04:51:33 mod_bosh info New BOSH session, assigned it sid
>> >> ‘3eadf41a-80b3-4522-905b-3ae55a4a3050’
>> >> Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 warn No
>> >> available
>> >> SASL mechanisms, verify that the configured authentication module is
>> >> working
>> >> Jun 05 04:51:33 mod_bosh debug We have an open request, so sending on
>> >> that
>> >> Jun 05 04:51:33 mod_bosh debug Request destroyed: table: 0x1687440
>> >> Jun 05 04:51:33 bosh3eadf41a-80b3-4522-905b-3ae55a4a3050 debug BOSH
>> >> session marked as inactive (for 60s)
>> >> Jun 05 04:51:33 socket debug server.lua: closed client handler and
>> >> removed
>> >> socket from list
>> >> Jun 05 04:51:33 mod_bosh debug Session
>> >> 3eadf41a-80b3-4522-905b-3ae55a4a3050 has 0 out of 1 requests open
>> >> Jun 05 04:51:33 mod_bosh debug and there are 0 things in the
>> >> send_buffer:
>> >> Jun 05 04:51:33 socket debug server.lua: accepted new client
connection
>> >> from 127.0.0.1:47398 to 5280
>> >> Jun 05 04:51:33 http.server debug Firing event: POST
>> >> meet2.buddhikajay.pro/http-bind
>> >> Jun 05 04:51:33 mod_bosh debug Handling new request table: 0x17ad990:
>> >> <body rid=‘2994510444’ xmlns=‘http://jabber.org/protocol/httpbind
>> >> sid=‘3eadf41a-80b3-4522-905b-3ae55a4a3050’/>
>> >> ----------
>> >> Jun 05 04:51:33 mod_bosh debug BOSH body open (sid:
>> >> 3eadf41a-80b3-4522-905b-3ae55a4a3050)
>> >> Jun 05 04:51:33 mod_bosh debug Session
>> >> 3eadf41a-80b3-4522-905b-3ae55a4a3050 has 1 out of 1 requests open
>> >> Jun 05 04:51:33 mod_bosh debug and there are 0 things in the
>> >> send_buffer:
>> >> Jun 05 04:51:33 mod_bosh debug Have nothing to say, so leaving
request
>> >> unanswered for now
>> >> Jun 05 04:51:37 jcp14354f0 debug Received[component]: <iq
>> >> id=‘1O2He-6728’
>> >> type=‘get’ to=‘meet2.buddhikajay.pro’
>> >> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:37 jcp157c5a0 debug Received[component]: <iq
>> >> id=‘0fe3g-31648’
>> >> type=‘get’ to=‘meet2.buddhikajay.pro’
>> >> from=‘focus.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:37 jcp157c5a0 debug Received[component]: <iq
>> >> id=‘0fe3g-31649’
>> >> type=‘get’ to=‘meet2.buddhikajay.pro’
>> >> from=‘focus.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31650’
>> >> type=‘get’ to=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:39 jcp14354f0 debug Received[component]: <iq
>> >> id=‘0fe3g-31650’
>> >> type=‘result’ to=‘focus@auth.meet2.buddhikajay.pro/
focus3535386783579’
>> >> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31651’
>> >> type=‘get’ to=‘meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31652’
>> >> type=‘get’ to=‘auth.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31653’
>> >> type=‘get’ to=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:39 jcp14354f0 debug Received[component]: <iq
>> >> id=‘0fe3g-31653’
>> >> type=‘result’ to=‘focus@auth.meet2.buddhikajay.pro/
focus3535386783579’
>> >> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31654’
>> >> type=‘get’ to=‘focus.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:39 jcp157c5a0 debug Received[component]: <iq
>> >> id=‘0fe3g-31654’
>> >> type=‘result’ to=‘focus@auth.meet2.buddhikajay.pro/
focus3535386783579’
>> >> from=‘focus.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:39 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31655’
>> >> type=‘get’ to=‘conference.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:47 jcp14354f0 debug Received[component]: <iq
>> >> id=‘1O2He-6729’
>> >> type=‘get’ to=‘meet2.buddhikajay.pro’
>> >> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:47 jcp157c5a0 debug Received[component]: <iq
>> >> id=‘0fe3g-31656’
>> >> type=‘get’ to=‘meet2.buddhikajay.pro’
>> >> from=‘focus.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:47 jcp157c5a0 debug Received[component]: <iq
>> >> id=‘0fe3g-31657’
>> >> type=‘get’ to=‘meet2.buddhikajay.pro’
>> >> from=‘focus.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:49 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31658’
>> >> type=‘get’ to=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:49 jcp14354f0 debug Received[component]: <iq
>> >> id=‘0fe3g-31658’
>> >> type=‘result’ to=‘focus@auth.meet2.buddhikajay.pro/
focus3535386783579’
>> >> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:57 jcp14354f0 debug Received[component]: <iq
>> >> id=‘1O2He-6730’
>> >> type=‘get’ to=‘meet2.buddhikajay.pro’
>> >> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:57 jcp157c5a0 debug Received[component]: <iq
>> >> id=‘0fe3g-31659’
>> >> type=‘get’ to=‘meet2.buddhikajay.pro’
>> >> from=‘focus.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:57 jcp157c5a0 debug Received[component]: <iq
>> >> id=‘0fe3g-31660’
>> >> type=‘get’ to=‘meet2.buddhikajay.pro’
>> >> from=‘focus.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:59 c2s15e7e00 debug Received[c2s]: <iq id=‘0fe3g-31661’
>> >> type=‘get’ to=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> >> Jun 05 04:51:59 jcp14354f0 debug Received[component]: <iq
>> >> id=‘0fe3g-31661’
>> >> type=‘result’ to=‘focus@auth.meet2.buddhikajay.pro/
focus3535386783579’
>> >> from=‘jitsi-videobridge.meet2.buddhikajay.pro’>
>> >>
>> >> and the response for second http bind request
>> >>
>> >> <body sid=‘f4ed6d83-0357-44dc-a351-90cfd020ed47’
>> >> xmlns:stream=‘http://etherx.jabber.org/streams
>> >> xmlns=‘http://jabber.org/protocol/httpbind’></body>
>> >>
>> >> On Mon, Jun 5, 2017 at 1:30 AM, Damian Minkov <damencho@jitsi.org> > >> >> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> There are two ways to debug this:
>> >>>
>> >>> First enable prosody debug log and check.
>> >>> Search for saslauth, there should be more hints there about the
error:
>> >>> ......saslauth debug sasl reply: <failure
>> >>> xmlns=‘urn:ietf:params:xml:ns:xmpp-sasl’><not-allowed/><
>Invalid
>> >>> signature</text></failure>
>> >>>
>> >>> Secons is to open the js console and check, (I think) the second
>> >>> http-bind request in Network tab, in the response you should see the
>> >>> error, something like:
>> >>> <body sid=‘7efaaed3-c806-4b7e-92e3-2e2b642b61af’
>> >>> xmlns:stream=‘http://etherx.jabber.org/streams
>> >>> xmlns=‘http://jabber.org/protocol/httpbind’><failure
>> >>> xmlns=‘urn:ietf:params:xml:ns:xmpp-sasl’><not-allowed/><
>Invalid
>> >>> signature</text></failure></body>
>> >>>
>> >>> From those errors, you should have more info what can be the reason.
>> >>>
>> >>> Regards
>> >>> damencho
>> >>>
>> >>>
>> >>> On Sun, Jun 4, 2017 at 11:46 AM, Buddhika Jayawardhana > >> >>> <buddhika.anushka@gmail.com> wrote:
>> >>> > Hi All,
>> >>> >
>> >>> > I have installed jitsi on Ubuntu 16.04 and configured the token
mode
>> >>> > as
>> >>> > described here. But when I try to login with a token I cannot
login
>> >>> > to
>> >>> > the
>> >>> > conference and getting following in prosody.log
>> >>> >
>> >>> >>>warn No available SASL mechanisms, verify that the configured
>> >>> >>> authentication module is working
>> >>> >>>info BOSH client disconnected
>> >>> >
>> >>> >
>> >>> > What could be the possible reason ?
>> >>> >
>> >>> > package details
>> >>> >
>> >>> > - Jitsi meet : 1.0.2098-1
>> >>> > - prosody-trunk : 1nightly786-1~xenial
>> >>> >
>> >>> > --
>> >>> > Buddhika Jayawardhana
>> >>> > Undergraduate | Department of Computer Science & Engineering
>> >>> > University of Moratuwa
>> >>> > buddhika.anushka@gmail.com | LinkedIn
>> >>> >
>> >>> > _______________________________________________
>> >>> > 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
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Buddhika Jayawardhana
>> >> Undergraduate | Department of Computer Science & Engineering
>> >> University of Moratuwa
>> >> buddhika.anushka@gmail.com | LinkedIn
>> >
>> >
>> >
>> >
>> > --
>> > Buddhika Jayawardhana
>> > Undergraduate | Department of Computer Science & Engineering
>> > University of Moratuwa
>> > buddhika.anushka@gmail.com | LinkedIn
>> >
>> > _______________________________________________
>> > 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
>
>
>
>
> --
> Buddhika Jayawardhana
> Undergraduate | Department of Computer Science & Engineering
> University of Moratuwa
> buddhika.anushka@gmail.com | LinkedIn
>
> _______________________________________________
> 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

--
*Buddhika Jayawardhana*
Undergraduate | Department of Computer Science & Engineering
University of Moratuwa
*buddhika.anushka@gmail.com <buddhika.12@cse.mrt.ac.lk>* | LinkedIn
<http://lk.linkedin.com/in/buddhikajay/>