Nextcloud AIO, upgrade to NC 35 not working

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
,
1
Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

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:

(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).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 34.0.4
  • Operating system and version (e.g., Ubuntu 24.04):
    • Raspberry Pi OS

Summary of the issue you are facing:

I get the following error when trying to upgrade:
[ ] Check for expected files … K;41m[✘] Check for expected files failed;49m
;41mUnknown files detected within the installation folder. This can be fixed by manually removing (or moving) these files. The following extra files have been found:;49m
;41m core.7;49m
;41mUpdate failed. To resume or retry just execute the updater again.;49m
Nextcloud 34.0.4

Steps to replicate it (hint: details matter!):

  1. Just upgrade to NC35 in the web ui of NC AIO
2

Hi, you would need to remove that file from your nextcloud folder. You can likely do so by execing into the container and then removing the file with the rm command.

  1. First create a backup via the AIO-interface
  2. Start the containers again
  3. After all of them are running, run via CLI:
    sudo docker exec -it nextcloud-aio-nextcloud bash
  4. List all files and folders in the current dir via ls -la
  5. Remove the unexpected file via rm core.7
  6. Log out of the container via exit
  7. Try to run the update again via the AIO-interface

I hope it helps!

3

OK, I will try that out. But I never created this file so the problem seems to be a bit deeper.

4

Your instruction worked. Note, that I had to use sudo docker exec -it nextcloud-aio-nextcloud bash
Thank you.