Same for me, 3.6.0 did not work, a second nextcloud instance on the same server which is on app version 3.5.3 works without trouble (and yes it uses the same docker container for collab online)
So something with 3.6.0 is weird
Same here on UCS Univention Docker Installation.
This works perfectly! Thanks
I use Collabora Online 3.6.0. And it works! But i don’t use Docker. There is no problem with this app. This is a problem with the configuration of your Collabora Online server!
Its a docker installation… Problems dont exist with docker. So its a problem with the app
The docker collab installation did work since years (and yes it is up to date) Same collab docker container works with 3.5.3 , just 3.6.0 stopped to work, so it is definitely the app.
And before you ask, I did have this problem on different and in now way connected setups!
1 Like
They should have documented that there are changes in the communication!
Older setup’s miss these two lines in the apache setup for the proxy setting:
# Endpoint with information about availability of various features
ProxyPass /hosting/capabilities https://127.0.0.1:9980/hosting/capabilities retry=0
ProxyPassReverse /hosting/capabilities https://127.0.0.1:9980/hosting/capabilities
These are now necessary!
Could someone in the nextcloud universe try to writeup useful release notes ?
2 Likes
There should be test for missing /hosting/capabilities added instead of just silently failing?
I’ve read the posts. Everyone writes that they have the same problem. And they all don’t give any useful information about their setup.
What can anyone do to help?
Also, changes in the apache setup of Collabora Online are no problem for the Nextcloud app.
Oh, u use an apache reverse proxy, not nginx? The first part of an useful information.
It would be helpful if the app would why it failed, like: “Missing /hosting/capabilities” or something else.
Same Problem, Docker installation and Collabora Online 3.6.0 Collabora error “Online is not setup yet”.
Back to version 3.5.3 works perfectly. Will now be more careful when updating this app, it is apparently not being tested.
@helge – How do you discover the exact version of your docker container? My compose file is setup to use latest collabora docker image and it was last updated 9 days ago. When I look at docker hub I’m seeing version 4.2.3.1 as the latest and not 3.6.0
@kevdog It is the Collabora Online App 3.6.0 Version, not the docker version. https://apps.nextcloud.com/apps/richdocuments
The solution is to set the following entry in Apache VirtualHost. https://nextcloud.com/de/collaboraonline/
# Endpoint with information about availability of various features
ProxyPass /hosting/capabilities https://127.0.0.1:9980/hosting/capabilities retry=0
ProxyPassReverse /hosting/capabilities https://127.0.0.1:9980/hosting/capabilities
This is how the Collabora Online Version 3.6.0 works.
3 Likes
Thank you very much for your solution.
It perfectly solves the problem on a bare-metal installation made with the D. Hansson VM scripts.
3 Likes
I faced the same problem with Collabora after upgrade at Debian 9 / Nginx / PHP-FPM installation.
I wonder why developers had not proposed any solution to this bug until now.
Such major releases should be tested thoroughly before publishing.
Adding those lines to apache’s config file works perfect.
It doesn’t seem to be a bug, but an improvement.
As a suggestion, the warning message telling that collabora is not well configured could be more accurate, or address a link with an explanation.
Anyway, thank you for improving the app!!! I find it one of the most usefull ones for nextcloud platform.
Hello,
Thanks, it works for me with the nginx configuration. I added the following lines :
# Capabilities
location ^~ /hosting/capabilities {
proxy_pass https://localhost:9980;
proxy_set_header Host $http_host;
}
But I had a bad gateway Nginx webpage. I tried to update collabora with docker pull collabora/code. You can find all command lines at this webpage :
After update, everything was ok.
1 Like
Thank you!
I added Capabilities and now everything works fine for Nginx/FPM as well.
Thanks, that worked for me too. Using nginx as proxy 
The only thing i had to do on top of changing the nginx config i had to click the “save” button on Collaboras settings page.
1 Like
The problem remains. I updated the application, made changes to the host configuration and restarted Apache.
I even compared character configuration of the host with the configuration on the site, the differences are only in the address of the site and the path to the certificates.
In the settings of the Collabora Online I enter the server address I click save it shows that everything is fine but it costs to refresh the page or re-enter the settings everything stops working.
Returned to version 3.5.3 
Maybe you intermixed http and https in the prox config?