Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nextcloud Talk Desktop with Load Balancer do not work #1144

Open
robake1 opened this issue Feb 27, 2025 · 7 comments
Open

Nextcloud Talk Desktop with Load Balancer do not work #1144

robake1 opened this issue Feb 27, 2025 · 7 comments
Labels
1. to develop bug Something isn't working

Comments

@robake1
Copy link

robake1 commented Feb 27, 2025

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>
@robake1 robake1 added 0. Needs triage bug Something isn't working labels Feb 27, 2025
@ShGKme
Copy link
Contributor

ShGKme commented Feb 27, 2025

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
Copy link
Author

robake1 commented Feb 28, 2025

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
Copy link
Contributor

ShGKme commented Feb 28, 2025

What do you use for sticky session?

@robake1
Copy link
Author

robake1 commented Feb 28, 2025

What do you use for sticky session?

F5 Load balancer , if you mean what product.

@ShGKme
Copy link
Contributor

ShGKme commented Feb 28, 2025

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

@ShGKme
Copy link
Contributor

ShGKme commented Feb 28, 2025

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

@robake1
Copy link
Author

robake1 commented Feb 28, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants