Failed adding new entry: Failed writing remote file

Error message “Failed adding new entry: Failed writing remote file: /path/to/archive.bcup” is displayed when a new entry is added in Chromium browser on Windows 10. Archive file is stored in Nextcloud folder. Console output:

setup-index.js:98
VError {jse_shortmsg: "Failed adding new entry: Failed writing remote fil…trimmed/path/to/archive.bcup", jse_info: {…}, message: "Failed adding new entry: Failed writing remote fil…trimmed/path/to/archive.bcup", stack: "VError: Failed adding new entry: Failed writing re…ieckodmcppbnembejjmabajjjj/setup-index.js:1:70791"}
    jse_info: {authFailure: undefined}
    jse_shortmsg: "Failed adding new entry: Failed writing remote file: /path/to/archive.bcup"
    message: "Failed adding new entry: Failed writing remote file: /path/to/archive.bcup"
    stack: "VError: Failed adding new entry: Failed writing remote file: /path/to/archive.bcup↵    at chrome-extension://heflipieckodmcppbnembejjmabajjjj/setup-index.js:1:70791"
    __proto__: Error

Tried to lock and unlock vault in the browser extension, but still the error was shown. Tried to remove and re-add the vault - the same outcome.

It seems like permissions related error, but I have no idea what permissions should be granted as the logged in user has full access to the archive file.

[Doctor-Who]

Same error too with a local file. Try with buttercup desktop app open or close Try with Firefox and Brave (Chromium base OS : Linux openSUSE

Failed saving credentials
Failed adding new entry: Failed writing remote file

[eandersons]

@perry-mitchell Well, that is the problem that I have no idea how to reproduce this error. All I know is that everything was working, and after a while (it could be days, so I do not know the exact point or action that caused the error) I could not save new entries. Just a reminder - everything is working in Buttercup desktop application and if the same vault is added to the browser extension using DAV (I am using Nextcloud).

Additionally I checked if this error can be observed on macOS as well, and it does occur on Mac too and on other Windows machines as well.

I also did this - I removed vault from the browser extension, closed Buttercup desktop application, deleted config.json, reopened Buttercup (config.json was regenerated with a new encryption key), in the browser extension added previously removed local archive, and the error is still there.