talk-desktop icon indicating copy to clipboard operation
talk-desktop copied to clipboard
verified publisher icon nextcloud

calls fail with Connection failed. Conversation not found or not joined

Open kaincenteno opened this issue 7 months ago • 16 comments

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. Leave the talk desktop app open for a while on a specific user (let's call them Doug)
  2. After a while the talk app will show "failed to establish signaling connection. Retrying ..." and never going away
  3. Have that user (Doug) start a call with you. The call will fail.

Update: i actually was able to reproduce the issue without step 2 happening

Image

both outgoing and incoming calls have the same issue

Expected behaviour

The call should go through as usual. This does not happen on the browser. Can leave the app open forever and will never see the call failing or the "failed to establish signaling connection. Retrying ...."

I would actually see this message briefly but then it would go away after a second(if im away from the window for too long)

Actual behaviour

The call will ring, will be able to accept it but then will be shown the screenshot bellow. Connection failed. Conversation not found or not joined.

Image

This will happen several times. The only way to mitigate this is by going to a different user, and reloading that faulty user then the call will go through without issues.

Diagnosis and logs

Diagnosis report

Diagnosis report

Nextcloud Talk Desktop
Version v1.1.8
Built-in Talk version v21.0.4
Release channel stable
Operating system Darwin 24.4.0 (Darwin Kernel Version 24.4.0: Fri Apr 11 18:32:43 PDT 2025; root:xnu-11417.101.15~117/RELEASE_ARM64_T8103)
Executable Path /Applications/Nextcloud Talk.app/Contents/MacOS/Nextcloud Talk
Connected to -
Nextcloud server version 31.0.4
Nextcloud Talk version 21.0.3
notifications app enabled ✅ yes
notify_push app enabled ✅ yes

Application config

{
  "launchAtStartup": false,
  "theme": "default",
  "systemTitleBar": false,
  "monochromeTrayIcon": true,
  "zoomFactor": 1,
  "playSoundChat": "respect-dnd",
  "playSoundCall": "respect-dnd",
  "enableCallbox": "respect-dnd",
  "secondarySpeaker": false,
  "secondarySpeakerDevice": null,
  "trustedFingerprints": []
}
Client logs

Press:

  • 🪟 Windows: Ctrl+Shift+I
  • 🍎 macOS: Cmd+Option+C
  • 🐧Linux: Ctrl+Shift+I

Or use the context menu to open the developer tools, then go to the Console tab.


[console_log.txt](https://github.com/user-attachments/files/20173731/console_log.txt)

kaincenteno avatar May 12 '25 17:05 kaincenteno

Do you have Nextcloud installed in a sub path? If yes - try v1.1.9

ShGKme avatar May 12 '25 18:05 ShGKme

Do you have Nextcloud installed in a sub path? If yes - try v1.1.9

ah apologies i should have mentioned it's installed in AIO container

kaincenteno avatar May 12 '25 20:05 kaincenteno

Did it work with previous versions, for example, 1.1.6? Or with a new version, 1.1.9?

This will happen several times. The only way to mitigate this is by going to a different user, and reloading that faulty user then the call will go through without issues.

Could you clarify what you mean here?

ShGKme avatar May 12 '25 20:05 ShGKme

Did it work with previous versions, for example, 1.1.6? Or with a new version, 1.1.9?

This will happen several times. The only way to mitigate this is by going to a different user, and reloading that faulty user then the call will go through without issues.

Could you clarify what you mean here?

i never saw this error on the past 2 versions. I have version 1.1.5 in my other device and don't see the "conversation not found or not joined" error

To clarify what i said. The error once it happens, its easily reproducible by having the person in the chat call me or trying to make the call. To stop having this issue, i would have to move away to a different person (so if i was in a message with person A, move to person B, then move back to person A again) and then it would start working again.

I have just upgraded to version 1.1.9 and it's the same issue. Also updated to the current AIO container

Diagnosis report

Nextcloud Talk Desktop
Version v1.1.9
Built-in Talk version v21.0.4
Release channel stable
Operating system Darwin 24.4.0 (Darwin Kernel Version 24.4.0: Fri Apr 11 18:32:43 PDT 2025; root:xnu-11417.101.15~117/RELEASE_ARM64_T8103)
Executable Path /Applications/Nextcloud Talk.app/Contents/MacOS/Nextcloud Talk
Connected to -
Nextcloud server version 31.0.4
Nextcloud Talk version 21.0.3
notifications app enabled ✅ yes
notify_push app enabled ✅ yes

Application config

{
  "launchAtStartup": false,
  "theme": "default",
  "systemTitleBar": false,
  "monochromeTrayIcon": true,
  "zoomFactor": 1,
  "playSoundChat": "respect-dnd",
  "playSoundCall": "respect-dnd",
  "enableCallbox": "respect-dnd",
  "secondarySpeaker": false,
  "secondarySpeakerDevice": null,
  "trustedFingerprints": []
}

kaincenteno avatar May 13 '25 03:05 kaincenteno

disregard the issue also happens with 1.1.5

I returned to my computer this morning after it was sleep. And saw the "failed to establish signaling connection. Retrying ...." so i asked the current person show on my talk messages to call me. I get the ringing but then afterwards get the "failed to establish signaling connection. Retrying ...." when accepting the call

more_logs.txt

Image

kaincenteno avatar May 13 '25 14:05 kaincenteno

i have the same problem is there any news about this?

Diagnosis report

Nextcloud Talk Desktop
Version v1.2.3
Built-in Talk version v21.1.0
Release channel stable
Operating system Darwin 24.5.0 (Darwin Kernel Version 24.5.0: Tue Apr 22 19:53:27 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6041)
Executable Path /Applications/Nextcloud Talk.app/Contents/MacOS/Nextcloud Talk
Connected to -
Nextcloud server version 30.0.6
Nextcloud Talk version 20.1.6
notifications app enabled ✅ yes
notify_push app enabled ✅ yes

Application config

{
  "launchAtStartup": false,
  "theme": "default",
  "systemTitleBar": false,
  "monochromeTrayIcon": true,
  "zoomFactor": 1,
  "playSoundChat": "respect-dnd",
  "playSoundCall": "respect-dnd",
  "enableCallbox": "respect-dnd",
  "secondarySpeaker": false,
  "secondarySpeakerDevice": null,
  "trustedFingerprints": []
}

Overpass4014 avatar Jul 04 '25 12:07 Overpass4014

If failing to connect to call it's preceded by failing PUT request to apps/spreed/api/v4/room/{token}/participants/state, then it fails because you don't have a session anymore (expired / disconnected / anything else).

We're working on a solution to catch such cases and recover failed sessions. ATM best workaround is to reload page / restart app

Antreesy avatar Jul 04 '25 16:07 Antreesy

is this only happening on macos or also happens on linux/windows?

kaincenteno avatar Jul 04 '25 17:07 kaincenteno

is this only happening on macos or also happens on linux/windows?

On any OS, on both desktop client and web client

ShGKme avatar Jul 04 '25 17:07 ShGKme

If failing to connect to call it's preceded by failing PUT request to apps/spreed/api/v4/room/{token}/participants/state, then it fails because you don't have a session anymore (expired / disconnected / anything else).

We're working on a solution to catch such cases and recover failed sessions. ATM best workaround is to reload page / restart app

@Antreesy Should I go ahead and open an issue in the spreed repo so it gets visibility if other people are having this issue?

@Overpass4014 were you able to fix this issue on your end, haven't really seen people complain about this so unsure if there is something in our AIO setup wrong or cause i am using a caddy reverseproxy

kaincenteno-doordash avatar Sep 22 '25 16:09 kaincenteno-doordash

Should I go ahead and open an issue in the spreed repo so it gets visibility if other people are having this issue?

If you can reproduce this behaviour with browser tab left open (e.g. for a night), we can just transfer this issue to spreed repo

Antreesy avatar Sep 22 '25 17:09 Antreesy

Should I go ahead and open an issue in the spreed repo so it gets visibility if other people are having this issue?

If you can reproduce this behaviour with browser tab left open (e.g. for a night), we can just transfer this issue to spreed repo

oh for sure this is reproduceable a couple times a day and def overnight. Do you want me to grab more logs?

kaincenteno-doordash avatar Sep 22 '25 17:09 kaincenteno-doordash

You can try, whether this flag helps with an issue: https://nextcloud-talk.readthedocs.io/en/latest/settings/#experiments

occ config:app:set spreed experiments_users --value=2

If that's the thing, we can just consider resolve the experimental condition, and it's fixed for everyone

Antreesy avatar Sep 22 '25 17:09 Antreesy

You can try, whether this flag helps with an issue: https://nextcloud-talk.readthedocs.io/en/latest/settings/#experiments

occ config:app:set spreed experiments_users --value=2 If that's the thing, we can just consider resolve the experimental condition, and it's fixed for everyone

i check yesterday morning and today and only saw briefly that error message and went away. I haven't tried making a call early in the morning. I'll try tomorrow morning.

I am still seeing 404 error but they are not in the thousands. I'll clear my logs today and try again will keep you updated

kaincenteno-doordash avatar Sep 24 '25 16:09 kaincenteno-doordash

woke up my macbook this morning and called the person that was currently in the desktop app today, was able to connect without issues. Will try again tomorrow to receive a call first thing in the morning

kaincenteno-doordash avatar Sep 25 '25 19:09 kaincenteno-doordash

@Antreesy confirmed working. It no longer experiences the same issues so that looks awesome =D

kaincenteno avatar Sep 28 '25 21:09 kaincenteno