nextcloud / nextcloud/talk-desktop

Nextcloud Talk Desktop with Load Balancer do not work

Open
#1,144 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

First I want to say that when going directly to the Nextcloud server and not using the LB with the same settings and software it works fine, also when turning of sticky sessions in the LB and use source ip Load Balancing instead . Our enviroment has two Nextcloud servers behind the LB and Talk in the WebGUI and other stuff in Nextcloud works fine through the LB with sticky sessions enabled.

Steps to reproduce

  1. Put Nextcloud server behind a Load Balancer (LB) with Sticky session algoritm for load balancing.
  2. Install Nextcloud Desktop on Windows client (Win 10 or 11) and point to the DNS name of the LB
  3. Open a chat in Talk and it will refresh by itself and say "The conversation does not exist"
Expected behaviour

The chat in Talk stays visible.

Actual behaviour

When having a chat in Talk open in Talk Desktop Client (Windows) pointing to the LB DNS it refresh the windows and say "The conversation does not exist"

Diagnosis and logs

Diagnosis report
Diagnosis report
Nextcloud Talk Desktop
Version v1.1.5
Built-in Talk version v21.0.0
Release channel stable
Operating system Windows_NT 10.0.22631 (Windows 11 Enterprise)
Executable Path C:\Users\user\AppData\Local\NextcloudTalk\app-1.1.5\Nextcloud Talk.exe
Connected to -
Nextcloud server version 29.0.11 Enterprise
Nextcloud Talk version 19.0.12
notifications app enabled ✅ yes
notify_push app enabled ❌ no
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
}
Client logs

No logs attached but it says "Failed to load resource: the server responded with a status of 404 (Not Found)" on statuses URL.


</details>

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

Start by reproducing the issue with the Windows Talk Desktop client against two Nextcloud servers behind a sticky-session load balancer, then inspect the failed statuses request returning 404. Done means a Talk conversation remains visible through the load balancer instead of refreshing with “The conversation does not exist.”

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.