element-hq / element-desktop

A glossy Matrix collaboration client for desktop.
https://element.io
GNU Affero General Public License v3.0
1.17k stars 267 forks source link

Set jitsi server in element desktop conf not working #816

Open Thatoo opened 3 years ago

Thatoo commented 3 years ago

I have Element 1.7.29 on Pop OS 20.10 I did

nano ~/.config/Element/config.json

The file was not existing. I copy paste in it the following, as explained in here https://github.com/vector-im/element-web/blob/develop/docs/jitsi.md

{
  "jitsi": {
    "preferredDomain": "jitsi.xxx.fr"
  }
}

then I restarted Element and when I click on camera call button in a room, it creates a jitsi.riot.im call and not a jitsi.xxx.fr call as expected.

robintown commented 3 years ago

Was the ~/.config/Element directory already existing? Is there a ~/.config/Riot directory you could try putting the config in?

Thatoo commented 3 years ago

~/.config/Element directory was existing and there is no ~/.config/Riot directory. There was a ~/.config/Element/electron-config.json file though but I didn't modify this one. I wonder if I should not modify that file instead of creating ~/.config/Element/config.json ...

Thatoo commented 3 years ago

By the way, I found this setting quiet complicated to set. Why not adding an option inside "Audio and Video" call settings of Element, where we set Audio output and Input and Camera...?

cajus commented 2 years ago

It's not exactly the same issue, but it seems like if I'm serving element-web locally, the config.json settings for

{
  "jitsi": {
    "preferredDomain": "jitsi.xxx.fr"
  }
}

doesn't seem to have any effect at all. It always connects to jitsi.riot.im. Is this expected?

t3chguy commented 2 years ago

doesn't seem to have any effect at all. It always connects to jitsi.riot.im. Is this expected?

How are you creating your conferences?

cajus commented 2 years ago

I'm inside of a private room and press the "call" button on top of the room chat. Then the jitsi widget loads, offering a button "Join conference". Pressing this button leads to a connection to jitsi.riot.im.

Sorry if I'm completely misunderstanding it - I'm currently in "getting started with matrix" mode ;-)

crjo commented 10 months ago

Hi there, i see that some people is able to configure a self jitsi server using Jitsi preferred domain, so is the issue still open or have i missed some configuration ?

photoninger commented 6 months ago

camelCase "preferredDomain" works for me, snake_case "preferred_domain" not. But camelCase is deprecated says https://github.com/element-hq/element-web/blob/develop/docs/config.md

t3chguy commented 6 months ago

Hmm both should work in config.json, only camel in well-known/matrix/client

image

elchako commented 5 months ago

config.json Good evening, everyone! I have the same problem. I'm launching element web in docker. The config file is attached.json from docker itself. I added it and tried to add preferred Domain and preferred_domain

It opens anyway https://meet.element.io/

Thank you for any help!

crjo commented 5 months ago

config.json Good evening, everyone! I have the same problem. I'm launching element web in docker. The config file is attached.json from docker itself. I added it and tried to add preferred Domain and preferred_domain

It opens anyway https://meet.element.io/

Thank you for any help!

Hi,

From our experience, that depends on the client you use :

And it depends how you are starting a call.

We found that in a new room if you add the Jitsi Widget and then start a call from the widget you open meet.element.io If you start a call without adding the widget, it's added automaticaly and you open the jitsi from config.json.

elchako commented 5 months ago

@crjo Thank you for the full answer!

t3chguy commented 5 months ago

Yeah if you add the widget manually then https://github.com/element-hq/element-integration-manager does not respect your config and does always use meet.element.io

mikebakke commented 3 months ago

Can someone explain what "adding a widget" means? I am just running the web-app in a docker, created the config.json which I know is accessed because the other configurations I put in are honoured. I just start a conversation with a user, press the call button and it always starts the call on default not my own jitsi instance.

Having maybe seen that 1:1 is always internal I created a call with 3 users and the result is identical.

OK - I figured out the widget part and ensured I was not - simply clicking on the call button. Regardless of what I try a call is never set up on my jitsi instance.

janonym1 commented 1 week ago

Yeah if you add the widget manually then https://github.com/element-hq/element-integration-manager does not respect your config and does always use meet.element.io

I made an issue regarding this behaviour here: https://github.com/element-hq/element-integration-manager/issues/131