levster

Looks like deleting and restarting did the trick. What, if anything different will I notice from this change? Thanks, Lev NextLog2.txt PS. also, deleting the "invalid files" is a pain as I have to do it via terminal or MC. doing it through Windows yields - I do not have permission. Also, now the there is a "Strict-Transport-Security" HTTP header is not set to at least "15552000" seconds. Message - fixed that by add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;" always;

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

Sorry, do you mean this? nextLog.txt

OK. Hope that this can help. Thanks! Lev Next.txt

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

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.

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.

Got it. I'm backing up the dockers now, just in case and will recreate image afterwards. I did not find anything that would issue an upgrade command. Do you have any idea of where that may be? I looked under all of the tabs in the Admin settings, to no avail. What did you mean by "spec issue"? Is this something that needs to go to Nextcloud directly? Lev

OK. I think that I understood most of this. It's like picking out the weeds. Annoying, but perhaps not a big deal. If I recreate the image, you mean remove the docker and reinstall it? Sorry for what is likely a noob question. Also, do there errors in the log mean anything? These are all from today. When I try to sync large folders, the docker frequently crashes and needs to be restarted. I thought that perhaps my old Mobo/CPU were not up to the job, but I am now running z790 with a i9-13900k and 32G, and am still getting same issues. ErrorPHPforeach() argument must be of type array|object, null given at /app/www/public/lib/private/Installer.php#4242023-06-25T19:43:41-0400 ErrorPHPTrying to access array offset on value of type null at /app/www/public/lib/private/App/AppStore/Fetcher/Fetcher.php#2022023-06-25T19:43:41-0400 ErrorPHPforeach() argument must be of type array|object, null given at /config/www/nextcloud/lib/private/Installer.php#4242023-06-25T18:03:42-0400 ErrorPHPTrying to access array offset on value of type null at /config/www/nextcloud/lib/private/App/AppStore/Fetcher/Fetcher.php#2022023-06-25T18:03:42-0400 ErrorPHPUsing ${var} in strings is deprecated, use {$var} instead at /config/www/nextcloud/3rdparty/scssphp/scssphp/src/Compiler.php#34912023-06-25T17:15:18-0400 ErrorwebdavSabre\DAV\Exception: An exception occurred while executing a query: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction2023-06-25T16:39:43-0400 ErrorwebdavSabre\DAV\Exception: An exception occurred while executing a query: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction2023-06-25T09:54:44-0400 ErrorwebdavOC\DB\Exceptions\DbalException: An exception occurred while executing a query: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction2023-06-25T08:24:49-0400 ErrorwebdavSabre\DAV\Exception: An exception occurred while executing a query: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction2023-06-25T04:39:52-0400 ErrorwebdavOC\DB\Exceptions\DbalException: An exception occurred while executing a query: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction2023-06-25T03:29:07-0400 ErrorPHPforeach() argument must be of type array|object, null given at /config/www/nextcloud/lib/private/Installer.php#4242023-06-25T03:03:03-0400 ErrorPHPTrying to access array offset on value of type null at /config/www/nextcloud/lib/private/App/AppStore/Fetcher/Fetcher.php#2022023-06-25T03:03:03-0400 Thanks for your help, Lev

Just to be clear, I would go into: \\TOWER\cache\appdata\nextcloud\www\nextcloud\apps and delete the files listed in the text? That's a lot of files to delete individually. Have they been there all along, and why did the error only now popped up? What would happen if I just leave them alone? And, if Nextcloud is reporting them as not passed... Why can't it automatically remove them? It just seems strange that the application would install them and now report them as errors. Lev

After updating to the latest docker I am getting the following error under Security & setup warnings: 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…) I am attaching what is under the list of invalid files. Running Nextcloud Hub 27.0.0 Nextcloud log is too large to attach... Technical information.txt

Hi, After upgrading to 6.12.0 Nextcloud is displaying an error: Server reported no ETag. This is for an external storage mounted in the Nextcloud. Any ideas how to fix it? I've attached the latest diagnostics, if that can help. Not sure how to attach a Nextcloud log. Thanks. PS. After restarting the docker, I do not see that message anymore... tower-diagnostics-20230615-0047.zip

Can some please tell me how to "permanently" fix the memory limit and Upload Max Size? I used the video: that goes nicely about changing the php.ini file, updating all of the values. However, as soon as there is un update to the docker, the updated values revert to their original values. Also, in that video several values are changed, upload_max_filesize, post_max_size, max_input_time, max_execution_time and memory_limit. What do all of these really do? Would someone use different values or not change some of them at all? I know that before changing these values, my Nextcloud instance would freeze up if I was syncing large files to several clients at the same time. After updating them, so far so good. Thanks, Lev

I hope that someone can shine a light a small problems that I am having. Whenever I am syncing multiple clients to the server, transferring large files, usually video, the Nextcloud instance stops responding within less than a minute, and all clients crash. If I disable all but one client, the transfer process completes. I would have to do this one at a time, allowing one client to finish before re-enabling next. Is there a fix to this? Not sure where to begin troubleshooting. Thanks, Lev

I noticed that when my Nextcloud docker is active, the overall load on the server CPU is in the 70 - 90 %. There is tremendous amount of outbound traffic, and some disks show 10,000,000 to 100,000,000's reads! And they go nonstop, even when the remote clients crash and the Nextcloud WebUI stops responding. As soon as I restart the docker, the server activity drops precipitously, and disk utilization also stops. Also, I noticed that if I manually exit out of all remote clients, the server activity does NOT stop. There is still high disk and CPU utilization.

I am having issues syncing my nextcloud files by constantly getting the "No connection to Nexctloud at https://... Timeout". I cannot get into the WebUI nor does the desktop application work until I restart the docker. Once the docker is restarted, the WebUI and the desktop app work fine, for some time, and then the entire process repeats. This seems to happen when I am syncing large files. Can anyone point to where I should troubleshoot? Thanks, Lev

Thank you very much. I'll keep an eye on it. Lev

I know that there is an entire thread or two on this issue, but am not sure how to proceed with my situation. If someone can point me in the right direction, that would be very helpful. Recently I noticed that my Nextcloud has been acting up, constantly reporting something like closed connection, needing me to shut down the client and restarting the docker. Thank you, Lev tower-diagnostics-20230211-1043.zip

While looking at my server's dashboard, I see network traffic, both inbound and outbound. I do see that there is reading and writing to some of the discs, including the cache. Is there a way for me to tell where that traffic is either originating from or going to? In other words, is there a way for me to see the IP addresses, either local or remote? Also, it would be great to see which files are being accessed, both read and write. Is there a log that I can look at? Thank you, Lev

I can see on the main page which disks were read from, but do not know which files were accessed. Is there a way to see which files were accessed, and keep track of when and by whom?

Haha! You're right! Completely forgot about that one.

Oh no, it's trash... Or, eBay jk

By the way, here is the SMART report. To my very novice eye, doesn't look good. tower-smart-20220907-1654.zip

OK, thank you.

I think that I will go with this route. So, what's the best way to do this. Stop the array, un-assign the parity 2 disc. Assign a new one to it. Restart the array, and have the parity rebuild? Do I need to do anything else in between those steps?