Update reverse-proxy.md for Collabora Compatibility #6299
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 <[email protected]>
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. 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. |
szaimen
added
2. developing
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.