-
Notifications
You must be signed in to change notification settings - Fork 23
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
Comments
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.
|
What do you use for sticky session? |
F5 Load balancer , if you mean what product. |
No, I mean, how the sticky session is configured in your setup. |
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. |
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
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
notifications
app enablednotify_push
app enabledApplication config
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.
The text was updated successfully, but these errors were encountered: