-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GET_SESSION_ID_ERROR #1942
Comments
Focus is a special user used by jicofo, you need to create a different user and use that one. |
created a user tes5884 logged in and getting the same error. Did I break it by changing the password for focus? Thanks |
Yep, it is definitely a problem if you haven't updated jicofo config. |
ok, I reloaded the OS - just to clear any stray configs. Followed the link, then created a separate user using: I try to login, and get the same error |
+1, any suggestion so far? |
I never got a working response
…On Oct 3, 2017 06:33, "davidetrapani" ***@***.***> wrote:
+1, any suggestion so far?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1942 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AByqcu8pIXYsbpWb8LArqJH5rds0WDKBks5sog1dgaJpZM4PF8Hb>
.
|
Ups, sorry I missed your replay. |
I created the user someuser with in
jicofo is running with when connecting to https://my.domain.it/someRoom it asks me for username/password and I put this is
this is
browser-side the error is
|
So you have VirtualHost "guest.my.domain.it" And in your config.js you have: Is this correct? And in jicofo you must have org.jitsi.jicofo.auth.URL=XMPP:auth.my.domain.it if you have the configs above. |
I have VirtualHost "my.domain.it" then it's right |
What about config.js ? |
damencho Facing the same problem. |
@pradyumnaba any prosody errors in the logs, do you see any reason for the disconnect? |
@damencho in both the places of config c2s_require_encryption is set to false. In prosody, reason seems to be BOSH doesn't know the session Id and hence disconnecting. Below is the log trace
|
Can you send a full js console log from the browser? |
|
Are you using the focus user to connect to the room? The focus user is reserved for jicofo and must not be used by users. |
Getting the same error even with other user who has admin access in prosody
|
Seems the response of the bosh requests doesn't reach the client, at least this is what I suspect can you open https://mydomain.com/http-bind the output should be like https://meet.jit.si/http-bind |
Getting it right! |
Hum, what I would suggest is clean jicofo logs, restart jicofo. Try entering the room by not using focus user and paste the whole jicofo log and client logs, as it is hard to guess what can be the problem. |
I am using the latest stable on my Ubuntu 16.04 and I have just followed https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md to install full jitsi-meet and tried enabling authentication following https://github.com/jitsi/jicofo (Secure domain section). Will upload the complete logs after restarting services in sometime |
Browser Log: prosody.err was 0KB so didn't attach that. |
Hum, there is something strange ... You are trying to create a conference with user from guest.mydomain.com, if you have set up the server using https://github.com/jitsi/jicofo#secure-domain (the 3th point using org.jitsi.jicofo.auth.URL) you should be able to create a conference only using the main domain. |
Yes, These are my hosts in config
} |
That's strange ... I will set it up, locally and will test and will report my findings. Thanks for the patience. |
Do you have in your jicofo config: |
Hey @paweldomas actually the property is there, so something else must be wrong: |
@damencho I will make a quick test tomorrow with the latest |
Thanks, this is even from stable, before merging smack. |
A problem is identified which affects versions in stable and unstable, we are working on a fix. |
Thanks @damencho, will wait for the fix |
This is fixed in jitsi-meet build 2590, we will work on updating stable these days with those changes. |
Thanks @damencho I will test once we have the stable update |
I am using the latest stable version (ver. 1.0.2635-1) on my Debian 8, I have just followed the quick install notes to install jitsi-meet and I have tried to enable authentication but I have not succeeded. |
You have this in your jicofo config(/etc/jitsi/jicofo/sip-communicator.properties): I tested this last week and it was working as expected. |
Yes, I have. I think my config is fine, I have checked everything. |
I will test it tomorrow with stable versions and will report my findings. |
@damencho: Did you find anything ? |
Nope, I didn't have time to look at it, but this is still on my todo list and will get to it if not today, for sure after Christmas. |
I just tested it and it is working fine on my side with the latest stable release. |
Hi @damencho , JS Log:
/var/log/prosody/prosody.log
/etc/prosody/prosody.cfg.lua
/etc/jitsi/meet/jitsi.mydomain.com-config.js
/etc/jitsi/jicofo/config
/etc/jitsi/jicofo/sip-communicator.properties |
You need to create the user as user@jitsi.mydomain.com |
The auth domain is a special one used by the internal components. The instructions https://github.com/jitsi/jicofo#secure-domain are how to secure the main domain used by the deployment, jitsi.mydomain.com. |
Hey @damencho , thanks for answering so quickly. shell:
|
If it makes things easier, I really just want to create some rooms for my family without anonymous users using my server. If there's a way to create 3 pre-defined rooms and to block any additional rooms from being created, that will be great. I'll just give these rooms weird and long names and nobody will guess them. |
In Android and iOS app we have achieved it by adding another layer. No one can join room without giving access code.
On 23-Apr-2018 at 05:10:46 ttimmy 'notifications@github.com' wrote:
If it makes things easier, I really just want to create some rooms for my family without anonymous users using my server. If there's a way to create 3 pre-defined rooms and to block any additional rooms from being created, that will be great. I'll just give these rooms weird and long names and nobody will guess them.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (#1942 (comment)), or mute the thread (https://github.com/notifications/unsubscribe-auth/AkTBU43WLWlgBHl1jEgSmI8-8B8UlFs4ks5trRT9gaJpZM4PF8Hb).
|
After adding
Have you restarted prosody? @ajaydata Please do not spam threads! And your comment is not correct. Changing the mobile client is not protection, cause everybody can use the deployment using the web client. Protection is not achieved by modifying web or mobile client, but by enforcing it in the backend. |
@damencho I restarted the entire server, just to make sure. |
That is strange. internal_plain supports adding/modifying users. |
If you are using valid SSL certificates generated by an authority as let's Ecrypt, please check that your actually are using it in the prosody site configuration file: /etc/prosody/conf.d/yourhost.example.com.cfg.lua. They will be the same that you have in web server configuration. |
Hi Guys,
I followed this link, point being that I'm trying to create authenticated meets only.
After doing the above, I created a prosody user:
prosodyctl register focus auth.jitsi.mydomain.com focuspassword
On browsing to my jitsi instance, it asked me to login. I login using:
login: focus@auth.jitsi.mydomain.com
password: focuspassword
I get the following error:
Oops! Something went wrong and we couldn't connect to the conference: connection.GET_SESSION_ID_ERROR
Any ideas?
The text was updated successfully, but these errors were encountered: