Support intro
Sorry to hear you’re facing problems. 
The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.
If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.
Getting help
In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.
Before clicking submit: Please check if your query is already addressed via the following resources:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).
The Basics
- Nextcloud Server version (e.g., 29.x.x):
35.0.2
- Operating system and version (e.g., Ubuntu 24.04):
Linux
- Web server and version (e.g, Apache 2.4.25):
Apache
- Reverse proxy and version _(e.g. nginx 1.27.2)
?
- PHP version (e.g, 8.3):
8.4
- Is this the first time you’ve seen this error? (Yes / No):
Yes
- When did this problem seem to first start?
After updating to NC 25.0.x
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
Shared hosting one-click-installation
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
No
Summary of the issue you are facing:
In the administration panel, I’m getting an code integrity error regarding the file
tmp/sfi_file_sequence_xxxxxxxxxxx/seq-009.lock
tmp/sfi_file_sequence_xxxxxxxxxxxx/seq-009.lock] => Array
(
[expected] =>
[current] => bb0fbec93af3af1e9631f848682849802645aa2c16fdba307969cc2674d9db75db06849f0be60446379680daabfe8788d582138e6e8e2852fd2decfbeeb0a051
)
Deleting the file seq-009.lock removes the message, but the file ist generated again and so is the error message…
Steps to replicate it (hint: details matter!):
- Update NC to 35.0.x
PASTE HERE