nextcloud / nextcloud/richdocuments

Encryption corrupts documents after some hours

Open
#3,151 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

integration: encryption (server-side)
Dominant language
JavaScript
Stars
453
Forks
147
Avg merge
14h 54m
Merged PRs (30d)
83

Description

Describe the bug
I and co-workers wrote a documentation about a network in nextcloud office. After about 4 hours of writing the document suddenly went blank. I then tried to restore a older version with the "versions" feature, all corrupted. I then tried restarting NGinx and PHP, didn't help. After that I tried downloading it and open it with Microsoft Word. Word couldn't open it, because it was corrupted. Today it happend again with an Excel file.

To Reproduce
Steps to reproduce the behavior:

  1. Open Word/Excel/(probably also PowerPoint) file
  2. Write something
  3. After some hours there are 2 possibilities: either it gets corrupted while you still write or it gets corrupted while it's closed.

Expected behavior
It should not get corrupted.

Client details:

  • OS: Debian 12
  • Browser: Microsoft Edge

Server details

Operating system: Debian 12

Web server: NGinx

Database: MariaDB

PHP version: PHP 8.1

Nextcloud version: 27.0.2

Version of the richdocuments app 8.1.1

Version of Collabora Online 23.5.305

Logs
Nextcloud log (data/nextcloud.log)
https://paste.miichelle.moe/upload/snail-shark-bee

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked data/nextcloud.log output and the reported richdocuments, Collabora Online, PHP, Nginx, and MariaDB versions. Investigate whether the corruption can be reproduced for Word or Excel files after several hours, and consider the issue complete only when documents remain readable during and after editing.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, mariadb, nginx, php
Domain
backend, web-dev
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.