iXNyNe

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

You can read https://www.linuxserver.io/blog/2019-09-14-customizing-our-containers and use a custom-cont-init.d script. I'm not going to go into a lot of detail on this because it's kind of advanced, and we document the general concepts, but not the specifics because we can't support every customization everyone wants to do (thus the DIY approach documented in the blog post). If you can figure out how to install the extension via the custom init script you'll be all set. If not I would advise you wait until a stable release of the extension is available. It would have to show up in a branch that isn't testing and has an actual release version number like 3.19 (if it gets included there in the future). alpine very rarely adds new packages to existing releases, so it's unlikely we would see it in 3.18 or below.

rename /config/crontabs to something else like /config/crontabs.bak and then restart the container. it will recreate the folder. compare the files in your renamed backup folder to the files in the newly created folder. if you intentionally customized anything, you can reapply your customizations. the line it comes with should not be modified though, it would just be if you needed to add extra lines. you can delete the renamed backup folder once you've confirmed you have any customizations reapplied (or didn't have any to apply).

If you're using swag as a reverse proxy make sure your configs for swag are up to date (check the container log). If you're using something else, there may be a conflict in the configurations between the proxy and nextcloud. If you're accessing directly without a proxy then we've got something wrong in the nginx confs and will have to investigate a fix.

That's normal. The scheduled task runner triggers before you've completed the web UI first time setup, and it depends on the setup being complete. Nothing to worry about.

There looks to be an extra single quote in there. Check your config.php

you can delete the listed files manually to make it go away.

docker exec -it nextcloud touch /config/www/nextcloud/config/needs_migration docker restart nextcloud Then rescan using the link in the Nextcloud admin status page. That should fix the integrity check. Running the occ command should not be needed, and without the steps above it won't fully fix the issue.

This should work, and I also believe there is a way to trigger an integrity check rescan for everything at once from inside the web UI.

Manually deleting the listed files shouldn't hurt anything.

The pdlib extension for php 8.2 does not seem to be available in the alpine package repository. There is a pdlib extension for php 8.0 in edge/testing, but we need 8.2. This is the search for the package: https://pkgs.alpinelinux.org/packages?name=php*pdlib*&branch=edge&repo=&arch=x86_64&maintainer= We need one specifically named php82-pdlib

For anyone having issues running occ, the correct command to use with the LSIO container is: docker exec -it nextcloud occ Also, I forgot to mention an important detail about the file integrity fix that has been released (entirely my bad!) docker exec nextcloud touch /config/www/nextcloud/config/needs_migration Then restart the container. The reason is the fix is only meant to run when you upgrade from a previous version (which includes the migration process that moved nextcloud's files inside the container). This will make the container think it needs to perform an upgrade and cleanup the integrity check files, and nextcloud will recognize it's already up to date and carry on fine.