Skip to content
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

Chrome: Talk kicks out member from call #13960

Open
AssiaAzzouzi opened this issue Dec 7, 2024 · 1 comment
Open

Chrome: Talk kicks out member from call #13960

AssiaAzzouzi opened this issue Dec 7, 2024 · 1 comment

Comments

@AssiaAzzouzi
Copy link

AssiaAzzouzi commented Dec 7, 2024

How to use GitHub

  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Steps to reproduce

  1. Connect to NC and open Nextcloud Talk in Chrome browser
  2. Join an ongoing call
  3. Start participating in the discussion

Expected behaviour

The user's participation in the discussion must be maintained.

Actual behaviour

The participant got kicked out from call and redirected to the login page of Nextcloud.

Talk app

Talk app version: 19

Custom Signaling server configured: yes version 2.0.0

Custom TURN server configured: yes Coturn-4.6.2

Custom STUN server configured: yes

Browser

Microphone available: yes

Camera available: yes

Operating system: Mac

Browser name: Chrome

Browser version: 131

Browser inspect element

When the user got kicked out from the call the browser logs the following:

Image

Server configuration

Operating system: Debian

Web server: Apache behind Nginx Reverse Proxy

Database: Maria

PHP version: 8.2

Nextcloud Version: 29.0.0

Signaling Server log

Nov 26 19:44:26 signaling signaling[487054]: clientsession.go:505: Session yW**************************MQ== left call ******
Nov 26 19:44:26 signaling janus[487005]: Detaching handle from JANUS VideoRoom plugin; 0x7f710001bba0 0x7f70a00199c0 0x7f710001bba0 0x7f710000fcc0
Nov 26 19:44:26 signaling janus[487005]: [janus.plugin.videoroom-0x7f70a00199c0] No WebRTC media anymore; 0x7f710001bba0 0x7f710000fcc0
Nov 26 19:44:26 signaling janus[487005]: [385973569225015] WebRTC resources freed; 0x7f710001bba0 0x7f7100006ae0
Nov 26 19:44:26 signaling janus[487005]: Detaching handle from JANUS VideoRoom plugin; 0x7f7100044a00 0x7f70a000fe10 0x7f7100044a00 0x7f71000353a0
Nov 26 19:44:26 signaling janus[487005]: [385973569225015] Handle and related resources freed; 0x7f710001bba0 0x7f7100006ae0
Nov 26 19:44:26 signaling signaling[487054]: janus_client.go:469: Unable to deliver message {
Nov 26 19:44:26 signaling signaling[487054]:    "janus": "detached",
Nov 26 19:44:26 signaling signaling[487054]:    "session_id": 1659264813566575,
Nov 26 19:44:26 signaling signaling[487054]:    "sender": 385973569225015
Nov 26 19:44:26 signaling signaling[487054]: }. Handle 385973569225015 gone?
Nov 26 19:44:26 signaling janus[487005]: [janus.plugin.videoroom-0x7f70a000fe10] No WebRTC media anymore; 0x7f7100044a00 0x7f71000353a0
Nov 26 19:44:26 signaling janus[487005]: [7203867215673431] WebRTC resources freed; 0x7f7100044a00 0x7f7100006ae0
Nov 26 19:44:26 signaling signaling[487054]: janus_client.go:469: Unable to deliver message {
Nov 26 19:44:26 signaling signaling[487054]:    "janus": "detached",
Nov 26 19:44:26 signaling signaling[487054]:    "session_id": 1659264813566575,
Nov 26 19:44:26 signaling signaling[487054]:    "sender": 7203867215673431
Nov 26 19:44:26 signaling signaling[487054]: }. Handle 7203867215673431 gone?
Nov 26 19:44:26 signaling janus[487005]: [7203867215673431] Handle and related resources freed; 0x7f7100044a00 0x7f7100006ae0
Nov 26 19:44:26 signaling janus[487005]: [janus.plugin.videoroom-0x7f70a00434f0] No WebRTC media anymore; 0x7f71000459c0 0x7f71000ea440
Nov 26 19:44:26 signaling signaling[487054]: mcu_janus_publisher.go:146: Room 5986181967668486 destroyed
Nov 26 19:44:26 signaling janus[487005]: Detaching handle from JANUS VideoRoom plugin; 0x7f71000459c0 0x7f70a00434f0 0x7f71000459c0 0x7f71000ea440
Nov 26 19:44:26 signaling janus[487005]: [2988697593053956] WebRTC resources freed; 0x7f71000459c0 0x7f7100006ae0
Nov 26 19:44:26 signaling janus[487005]: [2988697593053956] Handle and related resources freed; 0x7f71000459c0 0x7f7100006ae0
Nov 26 19:44:26 signaling janus[487005]: [janus.plugin.videoroom-0x7f70a00136c0] No WebRTC media anymore; 0x7f710004d6c0 0x7f7100042c20
Nov 26 19:44:26 signaling janus[487005]: [2150181291436870] WebRTC resources freed; 0x7f710004d6c0 0x7f7100006ae0
Nov 26 19:44:26 signaling signaling[487054]: mcu_janus_subscriber.go:68: Subscriber 2150181291436870 received hangup (DTLS alert), closing
Nov 26 19:44:26 signaling janus[487005]: Detaching handle from JANUS VideoRoom plugin; 0x7f710004d6c0 0x7f70a00136c0 0x7f710004d6c0 0x7f7100042c20
Nov 26 19:44:26 signaling janus[487005]: [2150181291436870] Handle and related resources freed; 0x7f710004d6c0 0x7f7100006ae0
Nov 26 19:44:26 signaling janus[487005]: [janus.plugin.videoroom-0x7f70a00209d0] No WebRTC media anymore; 0x7f71000088c0 0x7f710009f220
Nov 26 19:44:26 signaling janus[487005]: [1528232897166430] WebRTC resources freed; 0x7f71000088c0 0x7f7100006ae0
Nov 26 19:44:26 signaling signaling[487054]: mcu_janus_subscriber.go:68: Subscriber 1528232897166430 **received hangup (DTLS alert)**, closing
Nov 26 19:44:26 signaling janus[487005]: Detaching handle from JANUS VideoRoom plugin; 0x7f71000088c0 0x7f70a00209d0 0x7f71000088c0 0x7f710009f220
Nov 26 19:44:26 signaling janus[487005]: [1528232897166430] Handle and related resources freed; 0x7f71000088c0 0x7f7100006ae0

Also this participant is the only one who sees a duplicate participant within the call.

All those anomalies were not noticed when the participant changed browser to firefox.

By seeing CSRF mismatch in the inspect element screenshot, that makes me think of other old issues caused by chrome's caching like in this issue:
https://help.nextcloud.com/t/csrf-check-fehler/188776

@nickvergessen
Copy link
Member

nickvergessen commented Dec 9, 2024

Nextcloud Version: 29.0.0

That version is very outdated and no longer supported, only the last version of each feature branch is, so in this case Nextcloud 29.0.10

Web server: Apache behind Nginx Reverse Proxy

Are you running a multi-webserver setup? In that case sticky-sessions are required.

And well the message in the Signaling Server log is basically "the user stopped sending data for too long", and therefore they are disconnected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants