Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collabora files fail to load unless a workaround is used #68

Open
csolisr opened this issue Oct 24, 2022 · 9 comments
Open

Collabora files fail to load unless a workaround is used #68

csolisr opened this issue Oct 24, 2022 · 9 comments

Comments

@csolisr
Copy link

csolisr commented Oct 24, 2022

Describe the bug

When attempting to load a document from Nextcloud, it will invariably fail until several dozen attempts later, unless a specific window is opened in another tab (see details below)

Context

  • Hardware: Personal x86 server
  • YunoHost version: 11.0.10.1
  • I have access to my server: Through SSH, webadmin, direct access
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
  • Using, or trying to install package version/branch: 21.11.4.1

Steps to reproduce

  • Install Nextcloud and Collabora in different subdomains of the same server (e.g. cloud.example.net and collabora.example.net)
  • Log into Nextcloud, configure the office server to use your subdomain
  • Try to open a file. An error message appears stating that the file could not be opened and to please try again later. (Repeat this step as many times as necessary)
  • Check the console log in your browser, the following message appears:
    Invalid X-Frame-Options header found while loading “https://collabora.example.net/browser/abd9205/cool.html?WOPISrc=https%3A%2F%2Fcloud.example.net%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F2266025_oc6x9qsw4o82&title=file.odt&lang=en-US&closebutton=1&revisionhistory=1”: “ALLOWALL” is not a recognized directive.
  • Open https://collabora.example.net/browser/abd9205/cool.html?WOPISrc=https%3A%2F%2Fcloud.example.net%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F2243256_oc6x9qsw4o82&title=file.odt&lang=en-US&closebutton=1&revisionhistory=1 in a new tab, then try reloading the first tab. The application will finally load.

Expected behavior

The file should open directly, without requiring a workaround.

@LAfricain
Copy link

I have exactly the same issue. But I can't use the workaround, nothing like you in the firefox log console.

@ericgaspar
Copy link
Member

I can't reproduce this issue on my server using Nextcloud 25.0.1 with collabora 22.05.8.2.

@gokceozan
Copy link

I had the exact same problem. Solved the issue by changing the "Visitors" permissions at /yunohost/admin/#/groups

It started working for me when I added Nextcloud app (and not just API) permissions to the visitors user group.

Hope that helps!

@csolisr
Copy link
Author

csolisr commented Dec 7, 2022

It started working for me when I added Nextcloud app (and not just API) permissions to the visitors user group.

Does that mean that the issue is with external permissions?

@gokceozan
Copy link

I assume it is.

But were you able to replicate the fix?

@csolisr
Copy link
Author

csolisr commented Dec 9, 2022

I moved to the integrated Code server supplied as a Nextcloud app. I'll try uninstalling that and reinstalling Collabora over YunoHost later.

@csolisr
Copy link
Author

csolisr commented Dec 12, 2022

I have tested to reinstall Collabora, and by default it gives "All Users" and "Visitors" permissions for all three of "Collabora Online", "Nextcloud" and "Nextcloud (api)". The same error message still appears.

@gokceozan
Copy link

Could also be related to WOPI end-points. I couldn't figure out how to configure those so I don't have an allow list. Could it be the issue is a WOPI allow-list on your connector (like /nextcloud/settings/admin/richdocuments if you are using the generic Nextcloud Office one).

@lapineige
Copy link
Member

Could also be related to WOPI end-points. I couldn't figure out how to configure those so I don't have an allow list.

#86

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants