nextcloud / richdocuments

📑 Collabora Online for Nextcloud
https://nextcloud.com/collaboraonline
349 stars 115 forks source link

NextCloud 25.0.2 + built-in CODE 22.5.802 does not open files, only download them #2714

Open EddyLB opened 1 year ago

EddyLB commented 1 year ago

Describe the bug It is not possible to open files online. I can only download them.

To Reproduce Steps to reproduce the behavior:

  1. Go to Files
  2. Put the cursor over an .ODT file
  3. See the URL shown by the browser
  4. The URL is a Webdav link of the type: https://…/remote.php/webdav/file.odt

Expected behavior The URL should be one opening the file: https://…/index.php/apps/files?dir=/&openfile=319304

Screenshots taken when a Collabora demo server is selected

Demo Collabora 1 Demo Collabora 2 Demo Collabora 3

Screenshots taken when the Built-in CODE is configured

Built-in CODE 1 Built-in CODE 2 Built-in CODE 3

Client details:

Server details

Operating system: Linux 4.9.182-paas-110c975 x86_64, 3 CPU, 1 GB RAM

Web server: Apache/2.4.43 (Unix) with loaded modules: core.c, event.c, http_core.c, mod_access_compat.c, mod_alias.c, mod_auth_basic.c, mod_auth_digest.c, mod_auth_form.c, mod_authn_core.c, mod_authn_file.c, mod_authz_core.c, mod_authz_groupfile.c, mod_authz_host.c, mod_authz_user.c, mod_autoindex.c, mod_cgi.c, mod_deflate.c, mod_dir.c, mod_env.c, mod_expires.c, mod_filter.c, mod_gandiacc.c, mod_headers.c, mod_include.c, mod_info.c, mod_log_config.c, mod_mime.c, mod_negotiation.c, mod_proxy.c, mod_proxy_fcgi.c, mod_request.c, mod_rewrite.c, mod_session.c, mod_session_cookie.c, mod_session_crypto.c, mod_setenvif.c, mod_so.c, mod_status.c, mod_unixd.c, mod_vhost_alias.c

Database: MySQL version: 8.0.18

PHP version: 8.0.12

Nextcloud version: 25.0.2.3

Version of the richdocuments app: Nextcloud Office version 7.0.2

Version of Collabora Online: Built-in CODE Server version 22.5.802

Logs #### Nextcloud log (data/nextcloud.log) ``` Nothing during these tests and while configuring CODE. ``` #### Browser log ``` Empty ```
killerbees19 commented 1 year ago

Confirmed, same issue here. 🫤

Workaround: Downgrade the app to v7.0.1

https://apps.nextcloud.com/apps/richdocuments/releases?platform=25

EddyLB commented 1 year ago

Thank you for the suggestion but after downgrading Nextcloud Office to version 7.0.1, the issue is still there, unfortunately.

killerbees19 commented 1 year ago

Thank you for the suggestion but after downgrading Nextcloud Office to version 7.0.1, the issue is still there, unfortunately.

Hmm, I've successfully tested this workaround at my instance:

Maybe clear your browser cache?

EddyLB commented 1 year ago

This is what I did. I also purged the Varnish and PHP caches of the (virtual) server but this did not help. Same result with Safari, Firefox and Chrome ☹️

samdakap commented 1 year ago

My 2-cent troubleshooting advice: changing ownership of the folder after extraction.

chown www-data:www-data richdocuments

EddyLB commented 1 year ago

My 2-cent troubleshooting advice: changing ownership of the folder after extraction.

chown www-data:www-data richdocuments

Already checked. group and owner are fine.

samdakap commented 1 year ago

My 2-cent troubleshooting advice: changing ownership of the folder after extraction. chown www-data:www-data richdocuments

Already checked. group and owner are fine.

Indeed, tried it myself as well, does not solve the issue.

samdakap commented 1 year ago

Ok, I solved my own problem, not sure it was the same as yours...

image
jorge-vitrubio commented 1 year ago

I have had the same issue

After downgrading to 7.0.1 and changing the WOPI directive (adding the domain of the very same nextcloud installation) the app starts loading.

another issue appeared, with the proxy.php and WOPI

redacted the chromium debub console wich outputs a 400 error

https://DOMAIN.TDL/NEXTCLOUD/apps/richdocumentscode/proxy.php?req=/cool/https%3A%2F%2FDOMAIN.TDL%2FNEXTCLOUD%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F258770_occ9vs3k9ea9%3Faccess_token%3DJbgIuIYnIRPIle4yBzBMGivsK6k2xHe7%26access_token_ttl%3D1673298286000%26permission%3Dedit/ws?WOPISrc=https%3A%2F%2FDOMAIN.TDL%2FNEXTCLOUD%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F258770_occ9vs3k9ea9&compat=/ws/open/open/0

I will keep investigating

SevHub commented 1 year ago
image

Can you tell me where these settings have to be made? I can not find these settings anywhere. I looked up each and every settings page several times...

EddyLB commented 1 year ago

Downgrading to 7.0.1 and upgrading to 7.1.0 do not help. Entering the IP address in the WOPI did not help either. But OnlyOffice works pretty well.

jorge-vitrubio commented 1 year ago

same here, it is an issue with connecting to the collabora buid-in CODE , I did coment in the Collabora repo

https://github.com/CollaboraOnline/richdocumentscode/issues/206#issuecomment-1385442043

samdakap commented 1 year ago
image

Can you tell me where these settings have to be made? I can not find these settings anywhere. I looked up each and every settings page several times...

It is on the same page as the rest of the Nextcloud Office settings. See below:

image
killerbees19 commented 1 year ago

Don't ask me why, but the downgraded v7.0.1 stopped working at my Nextcloud without updates or manual changes.

After upgrading to v7.1.0 everything runs fine again.

safranat commented 1 year ago

I have the same problem with the nextcloud 25 snap on ubuntu server 22.04. It is possible to create new collabora documents from the existing templates but it will not open any new or existing documents. If I install the same snap on ubuntu desktop 22.04 it works. I would like to know what collabora needs from ubuntu which the desktop version 22.04 provides and the server 22.04 does not.

overflow-ITA commented 1 year ago

I have the same problem with the nextcloud 25.0.4 and v7.1.1

overflow-ITA commented 1 year ago

i solved the problem setting the dns of collabora server in /etc/hosts to 127.0.0.1 collabora.domain.tld i use haproxy as ssl termination and collabora ssl disable and termination enable and nginx use port for haproxy different to 443 (in mi case use 8080) without ssl . I use a different port on nginx because otherwise I couldn't open /browser/dist/admin/ properly with haproxy ssl off. Now everything works perfectly.