nextcloud / nextcloud/spreed

Logged-in and guest inconsistent call behaviour when guest has a connectivity issue.

Open
#13,498 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: call 📹 feature: frontend 🖌️
Dominant language
PHP
Stars
2.2k
Forks
587
Avg merge
17h 55m
Merged PRs (30d)
350

Description

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. As a logged in account, start a public call
  2. Join the call as a guest
  3. Simulate a network problem in the guest device (ex. unplug the ethernet cable)
  4. Wait a few seconds (10-30seconds)
Expected behaviour

Not sure about the expected behaviour but I'd say:

  • the logged in participant should see that the guest leaves the call when 3. happens
  • the guest should see a reconnection attempt and then the typical browser offline page. If the offline time is not too long, maybe an automatic reconnection should occur.
Actual behaviour

But definitely I'd say it shouldn't happen what is happening now:

  • a guest who has a connection problem (in the screen recording, this happens at 00:15), for example caused by his network provider, ends up in a “The conversation does not exist” page. He must then reopen the link in a new tab or by using browser navigation buttons (“go back one page”). In the latter case he must refresh the tab in order to join the call again.
  • the moderator continues to see the guest in the room even though he is disconnected. It is only at the time when the guest refreshes the tab (in the screen recording, this happens at 01:05), that he sees a disconnection event, followed eventually by a reconnection.

Here is a videorecording (logged-in account: left, guest: right):

https://github.com/user-attachments/assets/508ec69a-bb30-47a0-b016-236b2bd1ffab

I'm not sure this is due to my setup, so it would be great if this can be replicated and confirmed by someone else.

Talk app

Talk app version: 19.0.9

Custom Signaling server configured: 2.0.0

Custom TURN server configured: yes, coTURN stock version in Ubuntu Server 22.04

Custom STUN server configured: same as TURN

Browser

Microphone available: no

Camera available: no

Operating system: Ubuntu Desktop 24.04

Browser name: Firefox

Browser version: 124/125/...

Browser log

Server configuration

Operating system: Ubuntu Server 22.04

Web server: Apache2

Database: MariaDB

PHP version:

Nextcloud Version: 29.0.7

List of activated apps:

Nextcloud configuration:

Server log (data/nextcloud.log)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is named. Reproduce the listed logged-in and guest call steps with a simulated network failure, then inspect the browser behavior and available logs; done means the guest receives appropriate offline or reconnection handling and the moderator sees the guest disconnect without requiring a refresh.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
audio-video-rtc, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.