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

**URL:** <https://community.start9.com/t/error-checking-file-existence-when-saving-exporting-from-collabora/5764>\
**Category:** Services Support\
**Tags:** nextcloud\
**Created:** [September 24, 2026, 6:56pm UTC](https://community.start9.com/t/error-checking-file-existence-when-saving-exporting-from-collabora/5764 "2026-09-24T18:56:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AtomicPossum](https://community.start9.com/user_avatar/community.start9.com/atomicpossum/32/2358_2.png) [@AtomicPossum](https://community.start9.com/u/AtomicPossum)\
**Post date:** [September 24, 2026, 6:56pm UTC](https://community.start9.com/t/error-checking-file-existence-when-saving-exporting-from-collabora/5764/1 "2026-09-24T18:56:02Z")

</div>

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](https://community.start9.com/uploads/default/original/2X/4/4ed398c80b99de1a709f7b7504b5ee732ea72a7a.png)

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](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?

---

<div class="post-metadata">

**Author:** ![StuPleb](https://community.start9.com/user_avatar/community.start9.com/stupleb/32/195_2.png) [@StuPleb](https://community.start9.com/u/StuPleb)\
**Post date:** [September 25, 2026, 2:04pm UTC](https://community.start9.com/t/error-checking-file-existence-when-saving-exporting-from-collabora/5764/2 "2026-09-25T14:04:34Z")

</div>

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](https://github.com/nextcloud/end_to_end_encryption/pull/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.

---

<div class="post-metadata">

**Author:** ![system](https://community.start9.com/uploads/default/original/1X/2dcde8aa6ad3ce3d7873096ee4b3e5395e19a7b5.png) [@system](https://community.start9.com/u/system)\
**Post date:** [September 27, 2026, 2:05pm UTC](https://community.start9.com/t/error-checking-file-existence-when-saving-exporting-from-collabora/5764/3 "2026-09-27T14:05:19Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.