After taking a look at the nginx configuration inside of the docker container jwilder/nginx-proxy I found out that the following directive needs to be set in order for some websockets to work properly.
For everyone interested:
When buffering is disabled, the response is passed to a client synchronously, immediately as it is received. nginx will not try to read the whole response from the proxied server. The maximum size of the data that nginx can receive from the server at a time is set by the proxy_buffer_size directive.
The following steps will download the Collabora Online docker, make sure to replace “cloud.nextcloud.com” with the host that your own Nextcloud runs on. Also make sure to escape all dots with double backslashes (\), since this string will be evaluated as a regular expression (and your bash ‘eats’ the first backslash.) If you want to use the docker container with more than one Nextcloud, you’ll need to use domain=cloud\\.nextcloud\\.com\|second\\.nexcloud\\.com instead. (All hosts seperated by \|.)
Are you using the nginx proxy docker image from jwilders? With that I got it running some days before.
Do you have a valid ssl certificate for the domain office.domain.com?
I had to trick with the combination of nginx proxy and letsencrypt companion, that I could make it generate a valid certificate. The problem is, that the collabora docker image does not respond on port 80 requests, which letsencrypt needs to validate the domain.
Can you reach office.domain.com with a valid certificate, or do you get a browser warning?
I suggest enabling dns bypass in CloudFlare and see if it works with DNS resolving directly to your IP. I’ve seen MANY issues with cloudflare sitting in front of complex applications such as NextCloud, Collabora, etc unless it has specific optimizations already put in place to accommodate. I would definitely rule Cloudflare out as the problem before trying anything too drastic.
Thank you, I will work on this over the weekend and report back if this works. I still believe some updates need to be made to the example NGINX reverse-proxy configuration at https://icewind.nl/entry/collabora-online. Updates had to be made to the Apache configuration however i believe this one got forgotten. I am not sure if anyone has gotten this working yet.
Hi, i know this thread was inactive for a while, but can some elaborate how i can get a letsencrypt certificate for my office subdomain? i used the same docker run command as lachmanfrantisek and i get the little OK text when i access it via http. When i try it via https nginx-proxy redirects to the default domain…