[Support] Linuxserver.io - Nextcloud

avinyc · June 26, 2023

14 hours ago, blaine07 said:

Oh wow, this is a big deal. I don’t see a tag for 27 that I’m on… I’m just on “latest”m

I am dumb:

Thanks for sharing the link.

I wish there was a heads up or warning before this happened. I appreciate the update being automatic with the container now, but I was caught off guard with my installation upgrading by itself. I usually hold off until all my apps have been properly upgraded to support the latest version before diving in. Now I have 3 apps that are disabled because my installation jumped ahead. Again, my fault for making everything auto-update nightly, but now I will turn that off for nextcloud since it requires special attention when upgrading.

iXNyNe · June 26, 2023

7 minutes ago, avinyc said:

Thanks for sharing the link.

I wish there was a heads up or warning before this happened. I appreciate the update being automatic with the container now, but I was caught off guard with my installation upgrading by itself. I usually hold off until all my apps have been properly upgraded to support the latest version before diving in. Now I have 3 apps that are disabled because my installation jumped ahead. Again, my fault for making everything auto-update nightly, but now I will turn that off for nextcloud since it requires special attention when upgrading.

LSIO tries pretty hard to notify about important changes:

https://github.com/linuxserver/docker-nextcloud#versions (every repo has a section like this)

https://github.com/linuxserver/docker-nextcloud/releases/tag/27.0.0-ls252 (every release has notes like this, and on GitHub you can subscribe to email notifications when releases happen)

https://info.linuxserver.io/issues/2023-06-25-nextcloud/ (if there's any big or breaking changes we usually post a notification to our info site with more detailed instructions like this post, the info site also has an RSS feed and posts also are sent to a dedicated notification channel in our discord)

Auto update is definitely not the safest thing to be doing, but we understand how common it is and try to mitigate as much as we can. Nextcloud was a special case, because prior to this update the installation files were stored on your /config volume and mostly untouched by the container without manually running the occ command to upgrade. This however lead to the container dependencies like PHP updating over time with new releases of the container, and the installed version of nextcloud not being updated, and sometimes the installed (outdated) version of nextcloud would not be compatible with the current dependencies in the image. To solve this, we've build the application itself into the container and cherry picked only the files and folders that need to be persistent to remain in the /config volume. In the future, updating the container should automatically update nextcloud itself, along with any dependencies like PHP.

All that being said, LSIO does still recommend pinning a specific version tag such as lscr.io/linuxserver/nextcloud:version-27.0.0 and applying updates manually by simply changing the version at the end. A proper backup and recovery plan is also important.

avinyc · June 26, 2023

1 hour ago, iXNyNe said:

LSIO tries pretty hard to notify about important changes:

https://github.com/linuxserver/docker-nextcloud#versions (every repo has a section like this)

https://github.com/linuxserver/docker-nextcloud/releases/tag/27.0.0-ls252 (every release has notes like this, and on GitHub you can subscribe to email notifications when releases happen)

https://info.linuxserver.io/issues/2023-06-25-nextcloud/ (if there's any big or breaking changes we usually post a notification to our info site with more detailed instructions like this post, the info site also has an RSS feed and posts also are sent to a dedicated notification channel in our discord)

Auto update is definitely not the safest thing to be doing, but we understand how common it is and try to mitigate as much as we can. Nextcloud was a special case, because prior to this update the installation files were stored on your /config volume and mostly untouched by the container without manually running the occ command to upgrade. This however lead to the container dependencies like PHP updating over time with new releases of the container, and the installed version of nextcloud not being updated, and sometimes the installed (outdated) version of nextcloud would not be compatible with the current dependencies in the image. To solve this, we've build the application itself into the container and cherry picked only the files and folders that need to be persistent to remain in the /config volume. In the future, updating the container should automatically update nextcloud itself, along with any dependencies like PHP.

All that being said, LSIO does still recommend pinning a specific version tag such as lscr.io/linuxserver/nextcloud:version-27.0.0 and applying updates manually by simply changing the version at the end. A proper backup and recovery plan is also important.

Understood, and I do understand the risks with auto-updating, but it wasn't a problem until it became one for me:) I will follow this advice and use a specific version tag moving forward.

And I also understand there was a way to discover this change if I was properly monitoring the right places, this is a learning experience for me since I didn't even know there was a discord channel as well. I'm glad this change is happening, and no matter what LSIO could have done, someone like me would have missed it anyway. I'm just glad it was nothing serious to my server setup. Thank you for the time responding, have a good day!

Edited June 26, 2023 by avinyc

jademonkee · June 26, 2023

17 hours ago, iXNyNe said:

This is expected. Please read https://info.linuxserver.io/issues/2023-06-25-nextcloud/

tldr; no more manual updates

Wonderful. I was given no notice of this, and I updated the image today not realising that it would now update my Docker to v27.

After updating the Docker, I checked the logs for any changes to sample.confs and that some had changed in Swag and NextCloud. So I updated them, and restarted both. Nextcloud was then in Maintenance mode, and i didn't know why. I disabled maintenance mode, and now on the Admin page it says the following (and that I am now on v27, which I didn't choose to upgrade to):

Some files have not passed the integrity check. Further information on how to resolve this issue can be found in the documentation ↗. (List of invalid files… / Rescan…)

Files are:

~~I have no idea how to restore my backups (or if they'll even work), and I have no idea how to replace those borked files.~~

~~I tried manually specifying the tag and restarting in the hopes that those files would be updated, but it didn't work.~~

~~I fear I may have restarted the Docker while the update process was still happening (because I didn't know it was happening, thanks LSIO!)~~

EDIT: I just realised that they're "EXTRA FILES" not borked as I thought. So I'm guessing they're fine to just delete?

EDIT2: I just tried finding those files and I can't. I have no idea where they are located.

Any help is appreciated.

I also have several security related errors, but I'll deal with them later.

Edited June 26, 2023 by jademonkee

profzelonka · June 26, 2023

5 hours ago, iXNyNe said:

The major version (the first number in the version before the decimal) is all that you need to worry about. Using

lscr.io/linuxserver/nextcloud:version-25.0.4 should be fine, even if your install is 25.0.3 or 25.0.0

The key thing you missed in the tag is the prefix: version-

Looks like that's not it. Whenever I change it to anything except lscr.io/linuxserver/nextcloud the docker freezes and makes my unraid terminal also frozen, all cpu activity stats drop to 0% usage. All other dockers continue to work but looks like it freezes all terminals. Changing it back, does NOT unfreeze terminals and a restart is required. Any ideas?

*edit Don't think it's a docker app issue, created an Unraid docker support thread instead:

Edited June 26, 2023 by profzelonka

HHUBS · June 26, 2023

3 hours ago, jademonkee said:

Wonderful. I was given no notice of this, and I updated the image today not realising that it would now update my Docker to v27.

After updating the Docker, I checked the logs for any changes to sample.confs and that some had changed in Swag and NextCloud. So I updated them, and restarted both. Nextcloud was then in Maintenance mode, and i didn't know why. I disabled maintenance mode, and now on the Admin page it says the following (and that I am now on v27, which I didn't choose to upgrade to):

Some files have not passed the integrity check. Further information on how to resolve this issue can be found in the documentation ↗. (List of invalid files… / Rescan…)

Files are:

~~I have no idea how to restore my backups (or if they'll even work), and I have no idea how to replace those borked files.~~

~~I tried manually specifying the tag and restarting in the hopes that those files would be updated, but it didn't work.~~

~~I fear I may have restarted the Docker while the update process was still happening (because I didn't know it was happening, thanks LSIO!)~~

EDIT: I just realised that they're "EXTRA FILES" not borked as I thought. So I'm guessing they're fine to just delete?

EDIT2: I just tried finding those files and I can't. I have no idea where they are located.

Any help is appreciated.

I also have several security related errors, but I'll deal with them later.

Hi @jademonkee I have fixed mine. Check my reply here(below)

levster · June 26, 2023

17 hours ago, iXNyNe said:

deadlocks seem like a bad thing in the logs

to recreate the container, just swap the image like i mentioned in my last post, then swap it back

also, check the container logs for anything that might need attention

the web admin status page might have a database upgrade command that needs to be run that might solve the deadlock issue, but i'm not positive. that could legitimately be a spec issue.

So, I removed all of the extra files, and am now getting:

Technical information
=====================
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.

Results
=======
- twofactor_backupcodes
   - FILE_MISSING
       - l10n/af.js
       - l10n/af.json

I could have gotten sloppy and deleted these files. Any way to get them back?

Also, I changed the nextcloud version as directed, and then back to regular repository. The Nextcloud crashes constantly, requiring a manual restart.

Tucubanito07 · June 26, 2023

2 hours ago, HHUBS said:

Hi @jademonkee I have fixed mine. Check my reply here(below)

I tried both commands and it didnt fix the issue. Any other ideas? I have the same issue.

iXNyNe · June 27, 2023

4 hours ago, levster said:

So, I removed all of the extra files, and am now getting:

Technical information
=====================
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.

Results
=======
- twofactor_backupcodes
   - FILE_MISSING
       - l10n/af.js
       - l10n/af.json

I could have gotten sloppy and deleted these files. Any way to get them back?

Also, I changed the nextcloud version as directed, and then back to regular repository. The Nextcloud crashes constantly, requiring a manual restart.

from the unraid terminal run

docker exec nextcloud touch /config/www/nextcloud/config/needs_migration

or if you terminal directly into the container, just

touch /config/www/nextcloud/config/needs_migration

then restart the container

That should force the init to reinstall the default files.

iXNyNe · June 27, 2023

A more permanent fix for the integrity check issue is in the works now. I'll update once it's released. Until then, it shouldn't cause any functional issues to ignore the integrity check error. For anyone who's nextcloud instance isn't working otherwise, again I'll try to reply here quickly, but you may get quicker support in the LSIO discord (where there's other team members available as well).

levster · June 27, 2023

1 hour ago, iXNyNe said:

A more permanent fix for the integrity check issue is in the works now. I'll update once it's released. Until then, it shouldn't cause any functional issues to ignore the integrity check error. For anyone who's nextcloud instance isn't working otherwise, again I'll try to reply here quickly, but you may get quicker support in the LSIO discord (where there's other team members available as well).

Thank you very much for all your help. You're actually very responsive, something that is truly appreciated.

However, my installation seems to be corrupt beyond repair now. At least by me. It seems to freeze up every time I restart the container, after about 2 minutes. I have no clue where to even begin.

PS. I reverted to a backup version, and reinstalled the default files as per the recommendations. For the last 15 minutes the installation seems to be stable.

Edited June 27, 2023 by levster

iXNyNe · June 27, 2023

1 hour ago, levster said:

Thank you very much for all your help. You're actually very responsive, something that is truly appreciated.

However, my installation seems to be corrupt beyond repair now. At least by me. It seems to freeze up every time I restart the container, after about 2 minutes. I have no clue where to even begin.

PS. I reverted to a backup version, and reinstalled the default files as per the recommendations. For the last 15 minutes the installation seems to be stable.

can you post your container logs?

levster · June 27, 2023

20 minutes ago, iXNyNe said:

can you post your container logs?

The log that is generated on the logging page is around 39mb, too large to attach. Is there any way to downsize it?

iXNyNe · June 27, 2023

6 minutes ago, levster said:

The log that is generated on the logging page is around 39mb, too large to attach. Is there any way to downsize it?

The last 50-100 lines is probably enough.

blaine07 · June 27, 2023

Anyone else seeing this issue with most recent iOS app update?;

https://github.com/nextcloud/ios/issues/2492

levster · June 27, 2023

6 minutes ago, iXNyNe said:

The last 50-100 lines is probably enough.

OK. Hope that this can help.

Thanks!

Lev

Next.txt

iXNyNe · June 27, 2023

7 minutes ago, levster said:

OK. Hope that this can help.

Thanks!

Lev

Next.txt 90.3 kB · 0 downloads

Sorry, this looks like the log file, not the container log. You should be able to run

docker logs nextcloud

From the unRAID terminal

levster · June 27, 2023

9 minutes ago, iXNyNe said:

Sorry, this looks like the log file, not the container log. You should be able to run

docker logs nextcloud

From the unRAID terminal

Sorry, do you mean this?

nextLog.txt

jademonkee · June 27, 2023

11 hours ago, HHUBS said:

Hi @jademonkee I have fixed mine. Check my reply here(below)

Thanks for the tip.

I didn't know where to find the files until you showed me the command that suggested they were apps (I didn't think to look in the apps folder).

So I've now deleted all the files marked as "Extra" and fingers crossed that everything will continue to work.

Now I just have to fix the HTTP header errors...

Thulsa Doom · June 27, 2023

Hi)

I updated the container through the Docker Unraid section and now it is not running and this is shown:

This version of Nextcloud is not compatible with PHP>=8.2.
You are currently running 8.2.7.

Now docker.img has rolled back through the backup

Do I understand correctly that now it is impossible to update automatically and you need to wait for some fixed version ?

iXNyNe · June 27, 2023

6 hours ago, levster said:

Sorry, do you mean this?

nextLog.txt 21.38 kB · 1 download

That's the correct log.

At the bottom it mentions two nginx config files you need to update (the samples in the folder with those files are the updated version). If you didn't customize those files yourself you can delete them and restart the container and they will be recreated.

iXNyNe · June 27, 2023

46 minutes ago, Thulsa Doom said:
Hi)

I updated the container through the Docker Unraid section and now it is not running and this is shown:
This version of Nextcloud is not compatible with PHP>=8.2.
You are currently running 8.2.7.
Now docker.img has rolled back through the backup

Do I understand correctly that now it is impossible to update automatically and you need to wait for some fixed version ?

Follow the instructions here to get your nextcloud running https://info.linuxserver.io/issues/2023-06-25-nextcloud/

Once that's done, if you prefer automatic updates, the post mentions using the image without a tag. Then anytime you update the docker container it should update nextcloud (no more manual command updates).

If you prefer manual updates, pin a tag for the current version and change the tag when you want to update.

Tucubanito07 · June 27, 2023

13 hours ago, iXNyNe said:

A more permanent fix for the integrity check issue is in the works now. I'll update once it's released. Until then, it shouldn't cause any functional issues to ignore the integrity check error. For anyone who's nextcloud instance isn't working otherwise, again I'll try to reply here quickly, but you may get quicker support in the LSIO discord (where there's other team members available as well).

Thank you so much for your input on this.

levster · June 27, 2023

5 hours ago, iXNyNe said:

That's the correct log.

At the bottom it mentions two nginx config files you need to update (the samples in the folder with those files are the updated version). If you didn't customize those files yourself you can delete them and restart the container and they will be recreated.

Sounds great! I'll update and get back. Thank you!

enricovandijkhuizen · June 27, 2023

I just updated to the latest version but I now have the problem that after loggin in I don't have any style... Everything is just white and I also don't have any icon images? Does someone now a solution for this?

[Support] Linuxserver.io - Nextcloud

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

linuxserver.io

CHBMB

Konijntjes

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation