Latest Nextcloud/Collabora cannot open documents. #21
Comments
|
FIXED! There were changes in Collabora CODE 2.0 updates 2. The following changes have to be made in the Apache proxy configuration for Collabora.
This information needs to be updated on Nextcloud's instructions. |
|
Hello great news. But do you know how to get it fixed for nginx users? Kind regards |
|
I don't know, directly. I've never used nginx. However, I do know the breakdown of the changes to Apache2's configuration. If you can figure out the equivalents, you can solve the rest.
You would need to find the nginx equivalent of this behavior for your websocket proxy.
I hope that helps, and all the best! Please post the solution here if you find it. |
|
I have the same issue on Caddy but haven't been able to figure out how to resolve this issue yet. |
|
I did a bit of research, and both Apache2 changes relate to the same principle - the new version of Collabora requires slashes to NOT be encoded. Take a look at this nginx bug report. Still doing some digging. |
|
Collabora just posted the updated nginx configuration instructions. These should work, so cross check them with yours. |
|
I found this as well but it is not working neither. |
|
@nephilim75, what's your new configuration file look like? |
|
I have the same problem - this is the nginx configuration file of my VM with a public IP. The reverse proxy points to the docker container running inside an other VM via private IP. |
|
Here is mine: configurationKind regards |
|
I'm having the same issue using the above nginx configuration:
|
|
@milan475 You probably using aufs (and/or old kernel) in docker which possibly will not work - it's failing to set up privileged caps. |
|
Im having the same issues with the updated nginx configuration "Well, this is embarrassing, we cannot connect to your document.". Im using overlay2 storage driver for docker on Debian Testing, php7. The docker logs are: wsd-00027-0028 13:26:16.769784 [ client_req_hdl ] WRN WOPI host did not pass optional access_token_ttl| wsd/FileServer.cpp:255 There was a supposed temporary "solution" here but it didn't work for me.
I also tried asking about setting the nginx equivalents of the nocanon and AllowEncodedSlashes options on #nginx freenode but to no avail. |
|
Hi! |
|
kuchlbauer1 |
|
Thanks, methuselah-0, I added the proxy as explained in your links, but to no avail. |
|
kuchlbauer1 yes, either Docker or install from source. You can check out linuxbabe's tutorial for it, it's pretty neat and for Ubuntu and apache. https://www.linuxbabe.com/cloud-storage/integrate-collabora-online-server-nextcloud-ubuntu-16-04 |
|
Dear methuselah-0, thanks for the link, that seems to be a feasible way to do it. I will try that, the instructions seem to be very detailed :-) |
|
I tried linuxbabe's instructions and still get the error mentioned above. I'm using Nginx. Has anyone had success using their Apache setup? |
|
joekerna I'm using nginx and it works for me. In a separate subdomain.conf file in the server block I have location statements like this which works. Then in the Collabora Online App page in the admin section of the cloud I have in the url bar: https://subdomain.mydomain.tld:9980 which works for me. |
|
I forgot the port in my url in the admin section. Now I get
That's a new error I can search for... |
|
@methuselah-0 I've added my domain to loolwsd.xml inside my docker. Sadly the problem persists |
|
joekerna: sorry I got confused with your post and kuchlbauer1 who isn't using the docker version. I couldn't make it work with nginx for docker so I switched to installing lool from source instead which has the added benefit of not being limited to 10 documents. However, if you want to try and fix your config I think CodeMouse92's post earlier on this page gave the correct hints about solving it. The second mofication to the conf-file was about using apache's NoDecode option in nginx and my attempt at it looked something like below but it didn't work for me, possibly because of not setting the nocanon option: |
|
I've switched to Apache and built if from source... I still can't open documents. I think I'll have to give up... |
|
joekerna, did you build libreoffice online, or the docker collabora image? You might wanna see the full guide provided here: https://help.nextcloud.com/t/howto-install-onlineoffice-on-ubuntu-debian-no-docker-no-limitation/8958 |
A lot of users are getting an uninformative Access Forbidden page after using the official setup instructions like in nextcloud#21. Logging and showing the actual exception will help troubleshooting these issues.
|
@joekerna, if you get an Access Forbidden page, there is most probably an unhandeld exception in the background. You can get it displayed like in #37. For me the exception was the following:
I am using Let's Encrypt certs, so I needed to download the root certs and update my store. Richard Bairwells's blogpost has the commands. The Access Forbidden error with Apache is now solved for me. |
|
Here is what worked for me (based on https://stackoverflow.com/a/20514632): Note the |
|
I just upgraded the nextcloud collabora app to 2.0.13 and nextcloud couldn't open any files in collabora. I found this "crazy" solution here - may be completely irrelevant too.
|
OMG, thank you so much. I wasted one and a half our on this. Restarting the docker service did the trick! |
|
All issues discussed in here seem to be either related to the server setup or caused by a non-functional docker container. Please head over to the forum for further setup questions, as this is just the issue tracker for the Nextcloud integration of Collabora Online. |
|
If you check out the forums, many users have been having this issue ongoing for months now. This issue is not resolved and it leaves a bad taste in everyone's mouths. No one has been able to get an answer for this so I am suggesting this remain opened until which time this is resolved. |
|
any progress in this issue? |
|
This is still an issue ? Docker: port mapping of 127.0.0.1:9980:9980, and capacity added MKNOD and in nextcloud URL is protocol://your.nextcloud.domain Now, if your website is in mixed content (http and https) this possible will cause issues so, please set up https all way. Hope this will help someone. |
|
I had similar problems: I could see the icons of "File" ... but not click them. The document wasn't opened and I hang in a loop of connecting to collabora... And yes I know this issue is old |
|
I know it's late, but I've encountered the same problem. I've enabled WebSockets in the NGiNX proxy configuration and it work like a charm. I found this tip in this other thread. |
and others
I just upgraded my Nextcloud server from 10.3 to 11.0.1, by way of 11.0. All went well, and then I updated the Collabora Office app and pulled down the latest Collabora docker...all following Nextcloud's official instructions.
Now I can't open files in Collabora Office.
Steps to reproduce
Expected behaviour
The document should open.
Actual behaviour
On Nextcloud, I get ""Well, this is embarrassing, we cannot connect to your document. Please try again."
This is true of any file I open, even a newly created one.
On the docker logs for Collabora (
sudo docker logs th3d0ck3rpr0c3ssid), I see multiple copies of the following (with an actual token instead of [SCRUBBED], of course):Server configuration
Operating system:Ubuntu 16.04 LTS 64-bit Server
Web server: LAMP
Database:
mysql Ver 14.14 Distrib 5.7.17, for Linux (x86_64)PHP version:
PHP 5.6.30-1+deb.sury.org~xenial+1 (cli)Nextcloud version: 11.0.1
Updated from an older Nextcloud/ownCloud or fresh install: Updated from 11.0, which itself was a manual update from 10.3.
Where did you install Nextcloud from: Manual install from .ZIP originally, automatic updates to 10.3. (Everything worked to this point.) Manual upgrade from .zip for 10.3 -> 11.0.0. Automatic upgrade tool for 11.0.0 -> 11.0.1.
Signing status:
Signing status
List of activated apps:
App list
The content of config/config.php:
Config report
Are you using external storage, if yes which one: NO
Are you using encryption: NO
Are you using an external user-backend, if yes which one: LDAP
LDAP configuration (delete this part if not used)
LDAP config
Client configuration
Browser: Vivaldi
Operating system: Ubuntu 16.04 LTS 64-bit
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
The text was updated successfully, but these errors were encountered: