Hi. In my two recent posts I ask about problems that one major account has on the CryptPad instance I co-administrate. In this post I would like to report two errors that several working accounts as well as the “troubled” account see in the browser console, which do not seem to affect normal operations. I’d be interested to know your thoughts of what I could or should do about these, if anything.
- In my own account I regularly see eight of these together, and as far as I can see all the details for these eight are identical.
Object { error: "NOCACHE" }
worker.bundle.min.js:1:369340
init https://cryptpad.domain/common/worker.bundle.min.js?ver=2025.3.1-1749347017753:1
a https://cryptpad.domain/common/worker.bundle.min.js?ver=2025.3.1-1749347017753:1
mkAsync https://cryptpad.domain/common/worker.bundle.min.js?ver=2025.3.1-1749347017753:1
- Another group of eight errors soon follows, again the details seem identical:
Error: CHECKPOINT_DOES_NOT_MATCH_PREVIOUS_STATE
CHECKPOINT https://cryptpad.domain/common/worker.bundle.min.js?ver=2025.3.1-1749347017753:1
p https://cryptpad.domain/common/worker.bundle.min.js?ver=2025.3.1-1749347017753:1
v https://cryptpad.domain/common/worker.bundle.min.js?ver=2025.3.1-1749347017753:1
M https://cryptpad.domain/common/worker.bundle.min.js?ver=2025.3.1-1749347017753:1
O https://cryptpad.domain/common/worker.bundle.min.js?ver=2025.3.1-1749347017753:1
B https://cryptpad.domain/common/worker.bundle.min.js?ver=2025.3.1-1749347017753:1
o https://cryptpad.domain/common/worker.bundle.min.js?ver=2025.3.1-1749347017753:1
n https://cryptpad.domain/common/worker.bundle.min.js?ver=2025.3.1-1749347017753:1
worker.bundle.min.js:1:45550
I should tell you some details about the installation. After updating to 2025.3.1 I have worked to make the setup match the recommendations. For the cryptpad service, I have cloned the git repo and checked out the tag as stated in the instructions. The config file is config.example.js with only the minimal required changes. I then had to run install-onlyoffice.sh again because the OnlyOffice apps were not enabled and not available to activate in the settings before I ran the scrypt. In lib/plugins we have checked out sodium and it is up to date, I ran npm ci once again after the update. The OS is Debian Bookworm, all packages are updated, and nginx was installed from the stable nginx repository (not from Debian). The nginx instance configuration follows example-advanced.nginx.conf again with minimal changes.
I’ll be happy to give any further details.
