RocketChat / Rocket.Chat.Electron

Official OSX, Windows, and Linux Desktop Clients for Rocket.Chat
https://rocket.chat/
MIT License
1.6k stars 706 forks source link

Version 3.1.0 - Jitsi window does not open correctly using a own hosted Jitsi server #1919

Closed sandreddu closed 3 years ago

sandreddu commented 3 years ago

Unfortunately have to open an identical issue to the

1841

since I cannot reopen the old one. I'm really sorry to keep bugging you and insisting on this feature to work reliably, but as you can understand, in times of pandemic lockdown and smart working / home working situation, the video call feature is a number one priority in our company.

My Setup

Description

For all the screenshots please see the previous issue #1841 . Unfortunately, even with the latest update, the problem is not solved.

We host our own Jitsi meet server and Rocketchat server is set up to always open in new window. It works fine until release 2.17.11. Our Jitsi server is set up to use client certificate authentication Current Behavior

If I start a video call (in channel or 1-to-1), I'm asked to select a client certificate. It's selected. Then, the new window opens, but remains blank. If I close it and click on Click to Join again, it still opens a blank window.

If I close it again and select Click to Join for a THIRD time, it opens the Jitsi meeting window as expected, but the rocketchat client window becomes blank and the only way to return to the regular window after the video call is ended is to reload the client (Ctrl+R)

Expected Behavior

I select the client certificate, the jitsi window opens and the video call starts and end, and once ended we return to work on Rocket.Chat.

ankar84 commented 3 years ago

Yeap, https://github.com/RocketChat/Rocket.Chat.Electron/pull/1902 didn't fix that issue. image image @tassoevan please take a look.

tassoevan commented 3 years ago

Does it happen when a client certificate is needed?

ankar84 commented 3 years ago

Does it happen when a client certificate is needed?

No, in my case JWT token authentication is turned on in our Jitsi server

sandreddu commented 3 years ago

Thank you for the quick reply @tassoevan , I cannot test at the moment without client certificate authentication, but judging from the comments on the previous issue, it seems to happen regardless, when using an hosted server. As a test, with client certificate authentication on the browser it works ok.

tassoevan commented 3 years ago

Some new evidence suggest the blank window happens due to a crash in the Chromium process which renders the server view and can be unrelated to Jitsi. I'm still investigating.

ankar84 commented 3 years ago

@tassoevan `version 3.1.1 issue is still here jitsi-grey1

sandreddu commented 3 years ago

@ankar84 the work on this issue seems to be planned for the milestone 3.1.2 https://github.com/RocketChat/Rocket.Chat.Electron/milestone/47

ankar84 commented 3 years ago

@ankar84 the work on this issue seems to be planned for the milestone 3.1.2 https://github.com/RocketChat/Rocket.Chat.Electron/milestone/47

Yeap, I hope that critical issue will be finally fixed, because it's a showstopper for Jitsi update.

jf-flocode commented 3 years ago

version 3.1.1 on macOS Big Sur, issue still exists. Interestingly, issue happens on a self hosted Jitsi environment even with a downgraded Jitsi server version. JWT is enabled for us

rogerjames99 commented 3 years ago

I have just tested a source build of the current master of rocketchat electron on my Ubuntu 20.04. Now instead of getting a blank grey screen I get nothing at all when I start a video call. Nothing in the logs. The is a major show stopper for our community hub.

ankar84 commented 3 years ago

@tassoevan @rogerjames99 @sandreddu @johnpugh24 @hogthrob @corrigac @danel1 @Vringe @fplante-tink @pmp02 @dasfreak @stleitner @BSerpent86 @EnCz @merlin-tc @JohnLukeP @jf-jflo @chrisi51 @MartinSchoeler

Yesterday was released new version 2.0.5390 of Jitsi server https://github.com/jitsi/jitsi-meet-release-notes/blob/master/CHANGELOG-WEB.md And it looks like RC.Electron application work fine with that version. image Can you guys check that in your deployments?

sandreddu commented 3 years ago

@ankar84 thanks for the info! after jitsi update, a first test on a linux 3.1.1 client was succesful. Looks good! But I need to test with more clients in the next days

rogerjames99 commented 3 years ago

Just tried and it and now have no conferencing in either electron or web client!

Nothing in syslog, jicofo, or jvb logs. I will investigate further. Any tips gratefully accepted..

ankar84 commented 3 years ago

Just tried and it and now have no conferencing in either electron or web client!

Nothing in syslog, jicofo, or jvb logs. I will investigate further. Any tips gratefully accepted..

Sounds strange. Try to restart Jitsi server. Try just Jitsi server (without rocket chat) In our deployment everything looks good for now

paulausz commented 3 years ago

From my side it works better with the latest version of jitsi installed, but still not good. Instead of the behavior that @ankar84 captured on 26/12/2020, now two windows with Jitsi are opening. Furthermore, when selecting the "Click to Join" option in a chat, I often receive Feedback that the call already ended.

Rocket.Chat 3.1.1 for Windows Jitsi.Meet 2.0.5390-1 Token Authentification Enabled

ankar84 commented 3 years ago

Furthermore, when selecting the "Click to Join" option in a chat, I often receive Feedback that the call already ended.

Rocket.Chat 3.1.1 for Windows Jitsi.Meet 2.0.5390-1 Token Authentification Enabled

Call already ended it's a very old bug that still not fixed.

rogerjames99 commented 3 years ago

Jitsi server is working fine. Only thing I can think of is that I have just upgraded rocket chat to 3.10.3

rogerjames99 commented 3 years ago

Rolled back to 3.10.0 no difference.

EnCz commented 3 years ago

Rolled back to 3.10.0 no difference.

Attention so client and Server bugs doesn't get mixed up: Jitsi-Button was broken in RC 3.10.0, see https://github.com/RocketChat/Rocket.Chat/issues/20002

According to the issue this was fixed in 3.10.3

sandreddu commented 3 years ago

We have a relatively old server version, I admit, but it works reliably with Windows and Linux client, therefore I think I might consider the issue solved for me, since other bugs are not relevant to the electron client. Will test a couple more days and eventually close this ticket

ankar84 commented 3 years ago

We have a relatively old server version, I admit, but it works reliably with Windows and Linux client, therefore I think I might consider the issue solved for me, since other bugs are not relevant to the electron client. Will test a couple more days and eventually close this ticket

My experience the same with RC server version 3.7.1, Jitsi server version 2.0.5390 and RC.Electron version 3.1.1 on Windows 10 - all works pretty good. So for me that issue is looks solved too.

de-johannes commented 3 years ago

For us, Snap RC Server V 3.9.3, Jitsi Version 2.0.5142-1, and RC Electron V 3.1.1, on Windows 10, the Electron-Client still turns grey, after starting a call.

sandreddu commented 3 years ago

@de-johannes try upgrading your Jitsi to 2.0.5390-1 if possible and test again

de-johannes commented 3 years ago

@sandreddu tested another server with most recent docker version and jwt-authentication. same grey screen :/

ankar84 commented 3 years ago

@sandreddu tested another server with most recent docker version and jwt-authentication. same grey screen :/

That's really strange, because I have JWT authentication enabled too and grey screen not appears anymore with Jitsi server version 2.0.5390

de-johannes commented 3 years ago

perhaps i did something wrong. i'll double check it and respond again tomorrow.

Julian-Held commented 3 years ago

Can confirm: the upgrade to jitsi 2.0.5390 fixed the problem for us.

rogerjames99 commented 3 years ago

Not working for me with 2.0.5390 and 3.10.4 Tried to roll back to to 3.7.1, 3.9.4, 3.10.1, 3.10.3 but got Exception in callback of async function: errorClass [Error]: [Can't find migration version 213] So stuck on 3.10.4 now. Unless there is a safe way of rolling back the schema nowadays.

corrigac commented 3 years ago

Appears to be working with Jitsi Server at (20.4-0ubuntu1~20.04.1, 20.4-0ubuntu1~20.04.2), jitsi-meet-turnserver:amd64 (1.0.4466-1, 1.0.4628-1), jitsi-videobridge2:amd64 (2.1-376-g9f12bfe2-1, 2.1-416-g2f43d1b4-1), jicofo:amd64 (1.0-644-1, 1.0-690-1), lsof:amd64 (4.93.2+dfsg-1, 4.93.2+dfsg-1ubuntu0.20.04.1), jitsi-meet-web:amd64 (1.0.4466-1, 1.0.4628-1), jitsi-meet:amd64 (2.0.5142-1, 2.0.5390-1), jitsi-meet-web-config:amd64 (1.0.4466-1, 1.0.4628-1), jitsi-meet-prosody:amd64 (1.0.4466-1, 1.0.4628-1) - and Rocketchat server 3.10.4 and Rocketchat Electron Client (Mac) 3.0.7

JohnLukeP commented 3 years ago

Not working with:

Rocketchat server 3.10. 0 (Docker installation)

Jitsi (installed with package manager) : jicofo/stable,now 1.0-690-1 jitsi-meet/stable,now 2.0.5390-1 jitsi-meet-prosody/stable,now 1.0.4628-1 jitsi-meet-tokens/stable,now 1.0.4628-1 jitsi-meet-turnserver/stable,now 1.0.4628-1 jitsi-meet-web/stable,now 1.0.4628-1 all jitsi-meet-web-config/stable,now 1.0.4628-1 jitsi-videobridge2/stable,now 2.1-416-g2f43d1b4-1

Rocketchat windows desktop client: tested with both 3.1.0 and 3.0.6

If I click on start call, a popup "Start video call" appears asking me "cancel or yes", if I click yes, nothing happens. Moreover, the button "click to join" doesn't appear in the chat. This both with the option "Always open in new windows" set to enabled or disabled.

EnCz commented 3 years ago

@JohnLukeP As i wrote earlier in this issue: https://github.com/RocketChat/Rocket.Chat.Electron/issues/1919#issuecomment-759652092

Attention so client and Server bugs doesn't get mixed up: Jitsi-Button was broken in RC 3.10.0, see RocketChat/Rocket.Chat#20002

According to the issue this was fixed in 3.10.3

rogerjames99 commented 3 years ago

Rolled back to 3.7.1. Still getting the failed to access camera error. Thinking about doing a controlled roll forward to 3.10.5 and checking the behaviour at each stage.

This is with: Jitsi 2.0.5390-3 rocketchat.electron 3.2.0-snapshot edge JWT Auth disabled (Is this significant? I have never had it turned on before).

de-johannes commented 3 years ago

It is working now for me.

RC Server 3.9.4 RC Electron 3.1.1 Jitsi (Docker) 2.5390-1

No authentication

ankar84 commented 3 years ago

Still getting the failed to access camera error.

We are talking about different problem. Please make another issue and describe your problem in detail there.

rogerjames99 commented 3 years ago

@ankar84 Ok, thanks.

sandreddu commented 3 years ago

Rolled back to 3.7.1. Still getting the failed to access camera error. Thinking about doing a controlled roll forward to 3.10.5 and checking the behaviour at each stage.

This is with: Jitsi 2.0.5390-3 rocketchat.electron 3.2.0-snapshot edge JWT Auth disabled (Is this significant? I have never had it turned on before).

Failed camera error is a permission error on the local OS. It's still an open bug for the OS X dmg installer version as far as I know, but unfortunately totally unrelated to this issue. I'm closing this issue now. Thanks to everybody who commented and tested.

bahmanjafari commented 3 years ago

i'

Rolled back to 3.10.0 no difference.

Attention so client and Server bugs doesn't get mixed up: Jitsi-Button was broken in RC 3.10.0, see RocketChat/Rocket.Chat#20002

According to the issue this was fixed in 3.10.3

I upgrade to 3.10.5 but after I click on start call, a popup "Start video call" appears asking me "cancel or yes", if I click yes, nothing happens and still issue hare

SDAdham commented 3 years ago

Hello, I have the same issue on 3.2.3:

image image Can anyone please help?