nextcloud / nextcloud/talk-desktop

Error "Failed to join the conversation.

Open
#1,658 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs info
Dominant language
JavaScript
Stars
525
Forks
85
Avg merge
8h 5m
Merged PRs (30d)
35

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. Install Nextcloud Plesk extension ([Nextcloud Hub 10] (31.0.13))
  2. Install Nextcloud Talk app (version 21.1.8)
  3. Install Nextcloud Talk desktop app, windows (version 2.0.6)
  4. Log in on nextcloud domain, with any user.
  5. Click any conversation, you will get an error "Failed to join the conversation. Please try to restart the app."
  6. You are unable to type any message, or join/start any call. (cannot click on 'type-text-field' and the start-call button is disabled.)
Expected behaviour

I would like to send texts and start/join calls from the app.

Actual behaviour

I can not send text and join/start calls. I can't click on the field to type messages, and the start-call button is disabled (very light blue colour).

Image

From the browser everything works fine, and the desktop app does recieve the text-mesages, new chats etc.
I started without a Turn server configured, and have since installed coturn on my system.
I don't really have a way to test it, but I think it works all right.
The issue remains.

Diagnosis and logs

Diagnosis report
Diagnosis report
APPLICATION ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Version v2.0.6
Built-in Talk version v22.0.8
Release channel stable
SYSTEM ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Operating system Windows_NT 10.0.26200 (Windows 11 Pro)
Executable path C:\Program Files\Nextcloud Talk\app-2.0.6\Nextcloud Talk.exe
SERVER ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Server version v31.0.13
talk app v21.1.8
notifications app βœ… Enabled
notify_push app ⚠️ Not available
Application config
{
  "launchAtStartup": false,
  "theme": "default",
  "systemTitleBar": false,
  "monochromeTrayIcon": false,
  "zoomFactor": 1,
  "playSoundChat": "respect-dnd",
  "playSoundCall": "respect-dnd",
  "enableCallbox": "respect-dnd",
  "secondarySpeaker": false,
  "secondarySpeakerDevice": null,
  "trustedFingerprints": [],
  "lastAppVersion": "2.0.6"
}
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.

index.js:24 Using locale "en_US" for language "en"
/ocs/v2.php/apps/spreed/api/v4/room/cvvu7wfd/participants/active:1  Failed to load resource: the server responded with a status of 405 (Method Not Allowed)
4053.js?v=bb181e2db7ad8c1de441:9 B
joinConversation @ 4053.js?v=bb181e2db7ad8c1de441:9
/ocs/v2.php/apps/spreed/api/v4/room/cvvu7wfd/participants/state:1  Failed to load resource: the server responded with a status of 404 (Not Found)
4053.js?v=bb181e2db7ad8c1de441:238 B
d @ 4053.js?v=bb181e2db7ad8c1de441:238
/ocs/v2.php/apps/spreed/api/v4/room/cvvu7wfd/participants/state:1  Failed to load resource: the server responded with a status of 404 (Not Found)
4053.js?v=bb181e2db7ad8c1de441:238 Bcode: "ERR_BAD_REQUEST"config: {transitional: {…}, adapter: Array(3), transformRequest: Array(1), transformResponse: Array(1), timeout: 0, β€¦}message: "Request failed with status code 404"name: "AxiosError"request: XMLHttpRequest {onreadystatechange: null, readyState: 4, timeout: 0, withCredentials: false, upload: XMLHttpRequestUpload, β€¦}response: {data: {…}, status: 404, statusText: 'Not Found', headers: ti, config: {…}, β€¦}status: 404stack: "AxiosError: Request failed with status code 404\n    at OI (https://mydomain.com/talk_desktop__window_talk/index.js:9:1111)\n    at XMLHttpRequest.JI (https://mydomain.com/talk_desktop__window_talk/index.js:9:5895)\n    at wE.request (https://mydomain.com/talk_desktop__window_talk/index.js:11:2075)\n    at async u (https://mydomain.com/talk_desktop__dist/chunks/4053.js?v=bb181e2db7ad8c1de441:238:23922)"[[Prototype]]: Error
u @ 4053.js?v=bb181e2db7ad8c1de441:238

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

Reproduce the failure in the Windows desktop app, then inspect joinConversation in chunks/4053.js and the requests from index.js. Compare the 405 Method Not Allowed and 404 responses for the participants/active and participants/state endpoints with the reported Talk versions. Done means a user can join a conversation, type messages, and start or join calls.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, javascript
Domain
api, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.