"Error Checking File Existence" when saving/exporting from Collabora

Services Support
1

While select Save-As or Export-As any format, I am unable to save the the document and I get a ‘Error checking if file exists’ message.

image
image1390×602 53.9 KB

I find these erros in browser console:

  • Error checking file existence: Error: Invalid response: No root multistatus found 
    • Ko index.js:2

    • Ko index.js:2

    • Ko index.js:2

    • of usePropFindInterceptor.ts:32
      • SaveAs.vue:144:1
      • close SaveAs.vue:144
  • Content-Security-Policy: The page’s settings blocked the loading of a resource (default-src) at https://server-name.local:12345/browser/825c9caa93/templates/templates.js because it violates the following directive: “default-src ‘none’” NetUtil.sys.mjs:142:15

Is this feature working/not working for anyone else?

2

This isn’t Collabora. It’s a bug in Nextcloud’s End-to-End Encryption app, which is where the usePropFindInterceptor.ts line in your console comes from.

Before Save As or Export As writes anything, Nextcloud Office checks that the new file name isn’t taken, and it expects “not found” as the answer. With Enable E2EE navigation in browser switched on, the End-to-End Encryption app intercepts that check in your browser, mistakes the “not found” answer for a broken response, and raises the error you’re seeing, so the save stops.

The app’s developers have already fixed it (end_to_end_encryption#2094), but the fix isn’t in a release yet: 2.2.4 is still the newest version. It will arrive as a normal app update inside Nextcloud. Nothing needs to change on the StartOS side.

Until then:

  1. In Nextcloud, open Personal settings → Security and find End-to-end encryption.
  2. Switch off Enable E2EE navigation in browser.
  3. Reload the tab with your document and try Save As again.

That setting only affects the web interface. With it off, the browser can’t open end-to-end encrypted folders, but the desktop and mobile apps still can. Switch it back on once End-to-End Encryption updates past 2.2.4.

The Content-Security-Policy message about templates.js isn’t part of this.