Nextcloud Talk Desktop with Load Balancer do not work

[robake1]

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>

[ShGKme]

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

Were there any other errors? Could you check the Network tab, and what was the error with the conversation request?

[robake1]

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

Were there any other errors? Could you check the Network tab, and what was the error with the conversation request?

I checked the Network tab now when the error occurs , its a "404 Not Found" , pasting below from Headsers output , some thing replaced with xxxxxxxxxxxx and our url to nc.company.com.

Request Method: GET
Status Code: 404 Not Found
Remote Address: x.x.x.x
Referrer Policy: strict-origin-when-cross-origin
access-control-allow-credentials: true
access-control-allow-headers: Authorization, Content-Type, If-None-Match, Depth, requesttoken, OCS-APIRequest, X-OC-MTIME, X-Requested-With
access-control-allow-methods: GET, POST, PUT, PATCH, DELETE, PROPFIND, MKCOL, SEARCH, REPORT
access-control-allow-origin: file://
access-control-expose-headers: ETag, x-nextcloud-talk-modified-before, x-nextcloud-talk-hash, x-nextcloud-has-user-statuses, x-chat-last-given, x-chat-last-common-read
cache-control: no-cache, no-store, must-revalidate
connection: Keep-Alive
content-length: 111
content-security-policy: default-src 'none';base-uri 'none';manifest-src 'self';frame-ancestors 'none'
content-type: application/json; charset=utf-8
date: Fri, 28 Feb 2025 08:27:11 GMT
feature-policy: autoplay 'none';camera 'none';fullscreen 'none';geolocation 'none';microphone 'none';payment 'none'
keep-alive: timeout=15, max=96
referrer-policy: no-referrer
server: Apache
strict-transport-security: max-age=15552000; includeSubDomains
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-permitted-cross-domain-policies: none
x-request-id: ZwURqu81cOac3bMa0Efo
x-robots-tag: noindex, nofollow
x-xss-protection: 1; mode=block
accept: application/json, text/plain, */*
accept-encoding: gzip, deflate, br, zstd
accept-language: sv
connection: keep-alive
cookie: oci7vo1hnprx=slsfg16j0h1jgte69qfcvidali; oc_sessionPassphrase=XXXXXXXXXXXXXXXXXXXXXXX; __Host-nc_sameSiteCookielax=true; __Host-nc_sameSiteCookiestrict=true; LO_LB=xxxxxxxxxxxxxxxxxxxxxxxxxx
host: nc.company.com
ocs-apirequest: true
requesttoken:
sec-ch-ua: "Not A(Brand";v="8", "Chromium";v="132"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Windows"
sec-fetch-dest: empty
sec-fetch-mode: cors
sec-fetch-site: cross-site
user-agent: Mozilla/5.0 (Windows) Nextcloud-Talk v1.1.5
x-requested-with: XMLHttpRequest

[ShGKme]

What do you use for sticky session?

[robake1]

What do you use for sticky session?

F5 Load balancer , if you mean what product.

[ShGKme]

No, I mean, how the sticky session is configured in your setup.

[ShGKme]

I don't see the F5's default cookie used for sticky session in your response.

[robake1]

I don't see the F5's default cookie used for sticky session in your response.

I will check with my collegue that works with F5 and get back to you with a reply next week.

[robake1]

Now I have some more information regarding F5 and Cookies from our F5 technician.

We use F5s default cookie persistence profiles for sticky session.. With added encryption. Meaning that it is a session cookie used to determine the node to which it should forward traffic to. Settings for our cookie profile as follows.

[robake1]

Hi,

Any update on this issue we are facing ? , we would like to use the Talk Desktop client but its impossible now since this bug / problem.

@ShGKme have had time to investigate more ? :)

Thanks.