-
Notifications
You must be signed in to change notification settings - Fork 894
Update reverse-proxy.md for Collabora Compatibility #6299
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
Conversation
Added 'location ^~ /*' lines for collabora compatibility as the current config does now allow for collabora use and just results in a time out. There may be some oddities so I encourage discussing what's been added to drill down to a proper solution for everyone to use. Signed-off-by: tylerbib <Zadeis@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
works for me without this change
works for me without this change
Does it? For me the current config results in a timeout. Is your nginx proxy on a separate device or local to the nextcloud host?
are you sure that you correctly configured the websocket mappings?
The default config results in a "the server responded with a status of 400 ()" in the browser console leading credence to a malformed url/request. Given the current nginx config for an external proxy makes no mention of the config entries mentioned in the Collabora documentation here further leads me to believe these are required.
In addition the optional caddy file in the apache container config mentions the the same browser, hosting and cool entries.
Ultimately I do think my websocket settings are fine as I used the default config with my relevant ip address changes and cert changes. My setup isn't exotic (luckily). Just nginx running on a NUC running debian and nextcloud AIO running on another machine accessed via the apache port. Without the changes in my commit nextcloud alone runs fine. Just when attempting to use Collabora/Nextcloud Office it times out with the error/problem mentioned.
Added 'location ^~ /*' lines for collabora compatibility as the current config does now allow for collabora use and just results in a time out.
There may be some oddities so I encourage discussing what's been added to drill down to a proper solution for everyone to use. I mainly got to this point after arguing with Google Gemini 2.5 Pro for a fair bit of time but ultimately got collabora working.