iXNyNe

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.

Yes to anyone still seeing integrity checks. Post your container logs. Also make sure you've pulled the latest image using the check for updates button in the docker tab in unRAID and applied the update.

Correct. If you pull the latest image release yesterday those integrity issues should go away the next time you restart the container.

updater.phar has been removed from the latest releases. The update process has been built into the container image, so updating the container will perform the update to nextcloud itself going forward. If you are currently running the latest image without issues, then you don't need to take any action. If you have updated to the latest image and nextcloud is not working this post has all the info you should need https://info.linuxserver.io/issues/2023-06-25-nextcloud/ and if you follow all of that and still have issues you can post here with your container logs, nextcloud log file (in the/data volume), nginx log (in the /config/logs volume), /config/www/nextcloud/config/config.php file, and a screenshot of your nextcloud admin status page and I'll be able to help.

Check the container logs for both swag and nextcloud to see if there is any mention of updating configs. If so, there are sample files you can compare to your active files and make the necessary changes to update your configs. To make the container log warning go away, make sure you update the date at the top of your active files. If you still have trouble proxying at that point there may be an issue with our provided config for nextcloud's subfolder proxy and I can help troubleshoot that.

What errors do you have? Post your container logs, nextcloud log file (in the/data volume), nginx log (in the /config/logs volume), /config/www/nextcloud/config/config.php file, and a screenshot of your nextcloud admin status page and I'll be able to help.

The test image has been merged and the latest image release includes the fix for the integrity check issues.

This test image should fix the issue. It's been confirmed by a number of people and just awaiting LSIO team approval before merging. lspipepr/nextcloud:27.0.0-pkg-34240624-dev-d151fd013f86933409d88dbdd26222232842031f-pr-325

I can confirm I'm having this issue as well. unRAID 6.12.2 CA Auto Update Applications 2023.07.03

Deleting the apps folder shouldn't cause this. Crashing is usually preceded by errors in the container log or application log files. In the case of nextcloud this could be the nginx log in /config/logs or more likely in the nextcloud log in /data You had previously posted what looked like the nextcloud log with the php errors, which is what made me think it was a problem with the apps. At this point, since you have backups I would recommend setting one of the last known good backups aside somewhere so it doesn't rotate out when new backups are made, and then try completely deleting your nextcloud appdata and try doing a fresh install (may also need to make a new database, and possibly rename your nextcloud data folder to be sure there's no conflicts). If a fresh install of nextcloud has the same issues I'll be pretty stumped. If it works, then we just need to figure out what's going wrong with your current install.

I guess the diagnostics don't show that, or again I don't know what to be looking for (i'm not very familiar with the diagnostics, but I can see things like appdata and domains). I really have no idea why you would see internal server errors when accessing unraid. the pdf looks like you have all your settings correct.

/mnt/user/nextcloud your diagnostics don't seem to show that existing as a share in unraid. for example, if you unzip that file and search the files in the folder for appdata you'll find a bunch of config info about the share, but if you search for nextcloud it doesn't appear to be a share. Shares are normally mounted inside /mnt/user and you normally don't make other folders there, just subfolders under the share folders.

Doesn't seem like there's a port conflict. It does look like you're storing nextcloud data outside of an unRAID share. I'm not positive where that data would be stored, but I'm guessing not on your array. I could be wrong about that though, and maybe there's something I'm not understanding from the diag files.

unraid itself is showing internal server error? What port do you normally use to access unraid?

Can you go to the edit page for the nextcloud docker container in your unraid and turn on advanced (top right) and expand the "show more settings" at the bottom (don't need the docker allocations) and post screenshots of everything you see there?