iXNyNe

Switch your image to lscr.io/linuxserver/nextcloud:version-26.0.2 then run docker exec -it nextcloud updater.phar # if successful, repeat until there are no more updates then switch back to lscr.io/linuxserver/nextcloud:latest

Set your image to lscr.io/linuxserver/nextcloud:version-26.0.2 run in the unraid terminal (not the container terminal) docker exec -it nextcloud updater.phar # if successful, run it again until it says there are no more updates let us know the results

Sorry for the delay. I would delete /config/www/nextcloud/index.php and set your image to lscr.io/linuxserver/nextcloud:version-23.0.4 and restart the container then run docker exec -it nextcloud updater.phar # if it succeeds, run it again until it says no updates Edit: I see there's a newer reply from you after this one I quoted, and I don't think these instructions are what you need (yet). It looks like your database needs a repair of some sort. I don't have specific instructions for that, but some commands you could try docker exec -it nextcloud occ maintenance:repair docker exec -it nextcloud occ db:add-missing-columns docker exec -it nextcloud occ db:add-missing-indices docker exec -it nextcloud occ db:add-missing-primary-keys If none of those fix it, it could be something you'll have to fix with the sqlite command (and google the error message).

You can use lscr.io/linuxserver/nextcloud:version-26.0.2 Go to CA as if you were adding the app for the first time and it'll bring back your original container with your settings and you can set the image to lscr.io/linuxserver/nextcloud:version-26.0.2

I would try running docker exec -it nextcloud occ update And see if it still throws a fit. Also, try accessing the web interface and check the admin status page for any errors or recommended commands.

Prior to 27.x our image required you to manually update nextcloud. You should be able to run the updater.phar command listed in the article without changing your image to get updated. You may need to run it multiple times until it says there are no available updates. Once you get to that point, check which version you are on and follow along the article. If you have any issues, post logs here.

The current latest image should be lscr.io/linuxserver/nextcloud:version-27.0.1 If you set your image to that it should stay pinned until you change it. You can track when new versions are released by subscribing to release notifications at https://github.com/linuxserver/docker-nextcloud Note that we do sometimes update the version tags, so there may at times be updates available even if you pin the version, but it would be for things like OS dependencies, and not for nextcloud itself. If you want to pin to exactly how things are running right now and not get updates for underlying things like OS or package dependencies you can use lscr.io/linuxserver/nextcloud:27.0.1-ls259 That tag matches exactly with the release names from https://github.com/linuxserver/docker-nextcloud/releases and will be static builds we do not update/replace over time (you would have to change the tag to a new tag to get an update).

Switch to the image for 26.x and try running the updater

The "fatal: unable to exec php7" error is from cron and can be ignored for now. I would continue running the image for lscr.io/linuxserver/nextcloud:version-24.0.12 and delete /config/www/nextcloud/www/index.php and restart the container. Then delete /data/updater-<randomstring>/.step and run "docker exec -it nextcloud updater.phar"

It could be baked in, but nextcloud's official image doesn't do it, and our general stance is we don't want to in case it's destructive. this should be done manually after backing up your database and appdata. That being said I haven't had any issues with doing it, but that doesn't mean nobody ever has.

The built in updater in the web UI is no longer supported when using our docker image (I believe the official image from nextcloud also doesn't support it). The correct way to update nextcloud is to update the container image.

I'll chat with the rest of the team about updating the first post. I believe one of the other members has the credentials for the account that can edit it.

You are correct. Wait for lscr.io/linuxserver/nextcloud:version-27.0.1 to be available or switch to lscr.io/linuxserver/nextcloud:latest and let auto update handle it (although we do recommend pinning the specific version and manually updating rather than relying on auto updates). Simply updating the image will update nextcloud itself. No manual commands should be necessary.

This may require adjusting the nginx configs. I haven't tried to do this recently.

I didn't go that far back in the version history to list an image for 20.x, but I think it works up to PHP 7.4. https://info.linuxserver.io/issues/2023-06-25-nextcloud/ Basically from this post, follow the instructions as if you were currently running 22.x

Core files are in /app/www/public inside the container. The best thing to do is recreate the container. I don't know of a short way to do this on unRAID, but when the container image updates (usually weekly) it should solve itself.

Should be fixed, follow that comment.

make sure you're running the latest image (check the image tag, it's usually "latest"), check to make sure nextcloud's admin status page shows it's version 27.x, and then delete /config/crontabs folder and restart the container. it may take 5 minutes after that, but the cron should run.

If running occ doesn't fix the issue, try switching the image to lscr.io/linuxserver/nextcloud:version-25.0.4 and deleting /config/www/nextcloud/index.php and restarting the container, then run docker exec -it nextcloud updater.phar until it says you have installed NC 27, and then switch the image to lscr.io/linuxserver/nextcloud:latest or pin lscr.io/linuxserver/nextcloud:version-27.0.0

There are ways to remove the limits, but they exist for a reason (preventing potential abuse/attacks). Increasing the limits is safer than removing them. And actually we're currently shipping higher limits for PHP to allow large file uploads, but I forgot to increase the limits for nginx, so I need to do that (opening a PR now for the change, next release should have it).

sorry for the typo, my keyboard at home has some wicket chatter on the O key. I usually try to keep an eye on it. Anyway, the -R isn't a concern here, the container permissions need to be set that way. And there have been some significant changes to the container recently, but nothing i can think that would cause a permission issue like this.

try running this in the unraid terminal chown -R 99:100 /mnt/user/appdata/nextclouod chown -R 0:0 /mnt/user/appdata/nextclouod/crontabs/root then restart the container and see if the logs still show the same message

What values do you have for PUID and PGID on the nextcloud container?

I believe the cron runs every 5 minutes. Can you check if you still have the error about the scheduler not running? There was a recent change to the cron file (that should have automatically applied) to update the path of the file being executed.

You might try disabling the brute force app, then uninstalling it, then reinstalling it. Maybe try changing your email while it's uninstalled? I haven't seen that issue before and might be something you'd need to ask about on the nextcloud forum as that doesn't sound like a container issue (and I'm not really sure how to fix it).