Server is still falling back to using https://meet.jit.si/

nextcloud / jitsi

Nextcloud Jitsi Integration

GNU Affero General Public License v3.0

28 stars 9 forks source link

Server is still falling back to using https://meet.jit.si/ #28

Closed jcalfee closed 1 year ago

jcalfee commented 1 year ago

Recently the Jitsi / Next plugin starting switching to meet.jit.si during conferences after reporting a week connection. I would like it to fail rather than use a 3rd party server. In the App's administrative setting though, it is unclear to me why this is a server but it still requires a "Server URL" .. Shouldn't it point to itself?

weeman1337 commented 1 year ago

Hello @jcalfee :wave:

Server URL in the settings is the Jitsi instance the plugin is using. If it says https://meet.jit.si/ , then it always uses meet.jit.si. It should never automatically reset the setting to meet.jti.si.

Can you confirm, that you have something different than meet.jit.si in the settings and it is still connecting that instance?

jcalfee commented 1 year ago

Hi! Thank you for looking at this. Our install has meet.jit.si (just like the screen shot above), and I do not believe I ever found documentation so I did not change it (that must have been the default).. I can certainly put in out domain in there instead, but I'm not sure that is what I should do. Does the plugin have access to what it needs on the root domain so it will work? It seams like there should be some extra path on the end or some docs and extra steps to configure it.

weeman1337 commented 1 year ago

The plugin can work with a JSON web token as described in the README

Basically the steps are

Set up your Jitsi with JSON Web Token auth
Go to the Nextcloud Jitsi config, set your Jitsi instance URL and the JSON Web Token

jcalfee commented 1 year ago

Ok, I guess I was assuming the plugin was a Jitsi server. This makes sense, although it is open source it is pretty complex so it makes more sense that I would need my own with the JSON Web Token. Ok, thank you.