levster

I just went to check if there was un update for Nextcloud under the Docker page and I no longer see the Nextcloud at all! I am baffled. I did not remove it yet it is gone!!! Any suggestions? I re-added it, but am not sure why or how it disappeared from the Docker page...

So, just to be sure, even though the updater within the Nextcloud administration page says that a new version is available (27.0.2), nothing should be done until the docker update is available?

I started seeing this in my log: {"reqId":"rx6zq8d3izegG5GwOJqU","level":3,"time":"2023-07-16T01:05:49+00:00","remoteAddr":"24.189.29.9","user":"user","app":"PHP","method":"GET","url":"/apps/serverinfo/update","message":"Trying to access array offset on value of type null at /app/www/public/lib/private/App/AppStore/Fetcher/Fetcher.php#202","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36","version":"27.0.0.8","data":{"app":"PHP"},"id":"************"} Error: Trying to access array offset on value of type null at /app/www/public/lib/private/App/AppStore/Fetcher/Fetcher.php#202 GET /apps/serverinfo/update from 24.189.29.9 by user at 2023-07-16T01:05:49+00:00 {"reqId":"rx6zq8d3izegG5GwOJqU","level":3,"time":"2023-07-16T01:05:49+00:00","remoteAddr":"24.189.29.9","user":"user","app":"PHP","method":"GET","url":"/apps/serverinfo/update","message":"foreach() argument must be of type array|object, null given at /app/www/public/lib/private/Installer.php#424","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36","version":"27.0.0.8","data":{"app":"PHP"},"id":"*************"} [PHP] Error: foreach() argument must be of type array|object, null given at /app/www/public/lib/private/Installer.php#424 GET /apps/serverinfo/update from 24.189.29.9 by user at 2023-07-16T01:05:49+00:00 Already a few times.

What is the command to rescan folders / files in nextcloud? I used to use the sudo -u abc php /config/www/nextcloud/occ files:scan --all but am not sure if that is correct syntax. Also, for an individual user substitute --all for --path="user" Thanks, Lev Found it: docker exec -it nextcloud occ files:scan --path="user"

I think that I figured out why I was having "some" of the problems. Even though I completely removed the docker and the associated appfolders, something was left behind. I finally used docker system prune and subsequently reinstalled the dockers. Now, most of the WebDev errors have gone away. The email now sticks and it seems to be running smother. I noticed that when I am syncing large files, I see a lot of messages such as server replied "413 Request Entity Too Large" to "PUT https://nexctloud.myserver.com/remote.php/dav/uploads/user/#######/###### Does this mean that the files are too large when syncing, and if yes, how to address that? Thanks, Lev PS. My \\TOWER\cache\appdata\swag\nginx\proxy-confs\nextcloud.subdomain.conf has client_max_body_size 0; So I am assuming that I do not have a max set. Is there another value elsewhere that I need to look at? Noticed that \\TOWER\cache\appdata\nextcloud\nginx\site-confs\default.conf had client_max_body_size 512M; Changed that. Let's see what happens. Is there any way to remove limits alltogether?

I am using Swag and do not see anything odd in the log. Also, I am seeing a lot of these: Errorno app in contextOCP\Security\Bruteforce\MaxDelayReached: Reached maximum delay2023-07-10T08:27:41-0400 ntextOCP\Security\Bruteforce\MaxDelayReached: Reached maximum delay /app/www/public/lib/private/User/Session.php - line 431: OC\Security\Bruteforce\Throttler->sleepDelayOrThrowOnMax() /app/www/public/lib/private/User/Session.php - line 580: OC\User\Session->logClientIn("*** sensiti ... *") /app/www/public/lib/base.php - line 1143: OC\User\Session->tryBasicAuthLogin() /app/www/public/ocs/v1.php - line 61: OC::handleLogin() /app/www/public/ocs/v2.php - line 23: require_once("/app/www/public/ocs/v1.php") Errorno app in contextOCP\Security\Bruteforce\MaxDelayReached: Reached maximum delay2023-07-10T08:27:41-0400 Errorno app in contextOCP\Security\Bruteforce\MaxDelayReached: Reached maximum delay2023-07-10T08:27:37-0400 Errorno app in contextOCP\Security\Bruteforce\MaxDelayReached: Reached maximum delay2023-07-10T08:22:31-0400 On a side note, when I go to update my personal info, the email address cannot be changed from something that I used a long time ago. As soon as I change it, it reverts to the old, original one.

After setting a new instance of Nextcloud I have the following warnings: The "X-Content-Type-Options" HTTP header is not set to "nosniff". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly. The "X-Frame-Options" HTTP header is not set to "SAMEORIGIN". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly. The "X-XSS-Protection" HTTP header does not contain "1; mode=block". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly. I checked and in the nginx/site-confs/default.conf these are all listed. Should they be elsewhere?

I think that I managed to "fix" this issue. I reinstalled the entire trio one more time, paying close attention to the logs, and in the initial Nextcloud log, right after the first launch, here is what is in the log: Setting resolver to 192.168.1.1 Setting worker_processes to 32 generating self-signed keys in /config/keys, you can replace these with your own keys if required Initializing nextcloud 27.0.0.8 (this can take a while) ... Setting permissions New nextcloud instance Please run the web-based installer on first connect! Initializing finished After completing the web-based installer, restart the Nextcloud container to apply default memory caching and transactional file locking configurations. Alternatively, you can apply your own configurations by editing /config/www/nextcloud/config/config.php following the documentation: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/caching_configuration.html https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/files_locking_transactional.html # do daily/weekly/monthly maintenance # min hour day month weekday command */15 * * * * run-parts /etc/periodic/15min 0 * * * * run-parts /etc/periodic/hourly 0 2 * * * run-parts /etc/periodic/daily 0 3 * * 6 run-parts /etc/periodic/weekly 0 5 1 * * run-parts /etc/periodic/monthly # nextcloud cron */5 * * * * s6-setuidgid abc php -f /app/www/public/cron.php [custom-init] No custom files found, skipping... [ls.io-init] done. Exception: Not installed in /app/www/public/lib/base.php:285 Stack trace: #0 /app/www/public/lib/base.php(705): OC::checkInstalled() #1 /app/www/public/lib/base.php(1173): OC::init() #2 /app/www/public/cron.php(43): require_once('...') #3 {main} I am not sure if following this did the trick, or it was something else, but, for the time being I am in Nextcloud WebUI.

Here is the config.php (\\TOWER\cache\appdata\nextcloud\www\nextcloud\config) '<?php $CONFIG = array ( 'datadirectory' => '/data', 'instanceid' => '***************', 'passwordsalt' => '******************', 'secret' => '**********************', 'trusted_domains' => array ( 0 => '192.168.1.130:444', 1 => 'nextcloud.mysite.com', ), 'trusted_proxies' => ['swag'], 'dbtype' => 'mysql', 'version' => '27.0.0.8', 'overwrite.cli.url' => 'https://nextcloud.mysite.com/', 'overwritehost' => 'nextcloud.mysite.com', 'overwriteprotocol' => 'https', 'dbname' => 'nextcloud', 'dbhost' => '192.168.1.130:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'user', 'dbpassword' => 'password', 'installed' => true, );

So, I finally decided and pulled the trigger. Wiped all of the dockers relating to Nextcloud - MariaDB, Swag and Nextcloud and followed Spaceinvader One video to a t. When trying to launch the WebUI I get This site can’t be reached, and in the Nextcloud log the following line: Can't start Nextcloud because the version of the data ('27.0.0.8) is higher than the docker image version (27.0.0.8) and downgrading is not supported. Are you sure you have pulled the newest image version? How do I proceed?

I was debating wiping and completely reinstalling the Nextcloud / MariaDB, but am dreading the prospect... I may need a day or two to come up with the strength to come this realization

I modified your suggestions a bit, and disabled some of the apps in Nextcloud. I'll keep you appraised. Also, why would deleting the apps folder in Nextcloud effect the overall system so much that I was unable to even run a restore from the Backup/Restore Appdata plugin? Well, all I had to do was look at the Nextcloud, and it stopped. The Load and Memory bars went blank. All I can do, is restart the container... If everything is setup correctly, why does it crash?

I just checked, and I do I see Nextcloud, as a share under my shares page. It's the one that is assigned to disk10

Everything is stored on the server. Or, at least I think so. I have a few folders linked through the external storage. Which share concerns you? I'll check.

Here is my latest diagnostics Also, right now, I am back up and disabled most of the apps running in Nextcloud. I believe the port is 1443 tower-diagnostics-20230701-1622.zip

Here is the pdf. does it help? By the way, now that the docker is restored, I go to anything other than dashboard, I get Internal Server Error I restored the original apps folder, and at least I am back to square one.... Tower_UpdateContainer_next.pdf

I renamed the apps and restarted the container. Now, can't seem to reach the Nextcloud page at all. It did recreate the apps folder, but the site cannot be reached. And, on top of everything, I cannot start the container! I am getting Execution error. When I try to edit and pull the container again, I am getting the command failed error. Under the settings / Docker - I am getting One or more paths do not exist. And, when I try to go back and restore the dockers, I made a back up, I am getting invalid source... So, it seems that when I restart the unRaid itself, the Backup/Restore Appdata can complete it's job and restore the docker to it's saved state. It seems that when I rename the www/nextcloud/apps it throws the entire server off balance. Please, someone who can make heads and tails out of this, let me know what is going on. If I leave the newly created apps folder, I get the Page not found

Thank you very much. I will definitely try this out and get back to you. So far, everything you said is correct.

Sorry, but could you please elaborate? I don't want to screw it up. I've got Nextcloud, swag, plex, duckdns, and mariadb that are running.

This is getting to be a real pain. My Nextcloud docker freezes up / crashes every 10 to 20 minutes, stopping it's syncing with a client and I have to manually restart it. On the Admin / System page the Load and Memory graphs go completely blank, which tells me that the docker crashed. I restart the docker and all is well for another 10 to 20 minutes. How can I figure out what causes it to crash and fix it? This is VERY frustrating...

Sorry, but now I am getting these errors in my log: ErrorwebdavSabre\DAV\Exception\ServiceUnavailable: Storage unauthorized. / /app/www/public/3rdparty/sabre/dav/lib/DAV/Tree.php - line 78: OCA\DAV\Connector\Sabre\Directory->getChild() /app/www/public/3rdparty/sabre/dav/lib/DAV/Server.php - line 971: Sabre\DAV\Tree->getNodeForPath() /app/www/public/3rdparty/sabre/dav/lib/DAV/Server.php - line 1662: Sabre\DAV\Server->getPropertiesIteratorForPath() /app/www/public/3rdparty/sabre/dav/lib/DAV/Server.php - line 1647: Sabre\DAV\Server->writeMultiStatus() /app/www/public/3rdparty/sabre/dav/lib/DAV/CorePlugin.php - line 346: Sabre\DAV\Server->generateMultiStatus() /app/www/public/3rdparty/sabre/event/lib/WildcardEmitterTrait.php - line 89: Sabre\DAV\CorePlugin->httpPropFind() /app/www/public/3rdparty/sabre/dav/lib/DAV/Server.php - line 472: Sabre\DAV\Server->emit() /app/www/public/3rdparty/sabre/dav/lib/DAV/Server.php - line 253: Sabre\DAV\Server->invokeMethod() /app/www/public/3rdparty/sabre/dav/lib/DAV/Server.php - line 321: Sabre\DAV\Server->start() /config/www/nextcloud/apps/dav/lib/Server.php - line 364: Sabre\DAV\Server->exec() /config/www/nextcloud/apps/dav/appinfo/v2/remote.php - line 35: OCA\DAV\Server->exec() /app/www/public/remote.php - line 172: require_once("/config/www ... p") 2023-07-02T12:25:40-0400Errorno app in contextIcewind\SMB\Exception\ConnectionRefusedException: / /config/www/nextcloud/apps/files_external/3rdparty/icewind/smb/src/Native/NativeState.php - line 75: Icewind\SMB\Exception\Exception::fromMap() /config/www/nextcloud/apps/files_external/3rdparty/icewind/smb/src/Native/NativeState.php - line 92: Icewind\SMB\Native\NativeState->handleError() /config/www/nextcloud/apps/files_external/3rdparty/icewind/smb/src/Native/NativeState.php - line 351: Icewind\SMB\Native\NativeState->testResult() /config/www/nextcloud/apps/files_external/3rdparty/icewind/smb/src/Native/NativeShare.php - line 305: Icewind\SMB\Native\NativeState->getxattr() /config/www/nextcloud/apps/files_external/3rdparty/icewind/smb/src/Native/NativeFileInfo.php - line 43: Icewind\SMB\Native\NativeShare->getAttribute() /config/www/nextcloud/apps/files_external/3rdparty/icewind/smb/src/Native/NativeFileInfo.php - line 69: Icewind\SMB\Native\NativeFileInfo->stat() /config/www/nextcloud/apps/files_external/3rdparty/icewind/smb/src/Native/NativeShare.php - line 114: Icewind\SMB\Native\NativeFileInfo->getSize() /config/www/nextcloud/apps/files_external/lib/Lib/Storage/SMB.php - line 191: Icewind\SMB\Native\NativeShare->stat() /config/www/nextcloud/apps/files_external/lib/Lib/Storage/SMB.php - line 647: OCA\Files_External\Lib\Storage\SMB->getFileInfo() /app/www/public/lib/private/Files/Storage/Common.php - line 117: OCA\Files_External\Lib\Storage\SMB->filetype() /app/www/public/lib/private/Files/Storage/Wrapper/Wrapper.php - line 114: OC\Files\Storage\Common->is_dir() /app/www/public/lib/private/Files/Storage/Wrapper/Availability.php - line 131: OC\Files\Storage\Wrapper\Wrapper->is_dir() /app/www/public/lib/private/Files/Storage/Wrapper/Wrapper.php - line 114: OC\Files\Storage\Wrapper\Availability->is_dir() /app/www/public/lib/private/Files/Cache/Watcher.php - line 111: OC\Files\Storage\Wrapper\Wrapper->is_dir() /app/www/public/lib/private/Files/View.php - line 1321: OC\Files\Cache\Watcher->update("*** sensiti ... *") /app/www/public/lib/private/Files/View.php - line 1356: OC\Files\View->getCacheEntry() /config/www/nextcloud/apps/dav/lib/Connector/Sabre/Directory.php - line 216: OC\Files\View->getFileInfo() /app/www/public/3rdparty/sabre/dav/lib/DAV/Tree.php - line 78: OCA\DAV\Connector\Sabre\Directory->getChild() /app/www/public/3rdparty/sabre/dav/lib/DAV/Server.php - line 971: Sabre\DAV\Tree->getNodeForPath() /app/www/public/3rdparty/sabre/dav/lib/DAV/Server.php - line 1662: Sabre\DAV\Server->getPropertiesIteratorForPath() /app/www/public/3rdparty/sabre/dav/lib/DAV/Server.php - line 1647: Sabre\DAV\Server->writeMultiStatus() /app/www/public/3rdparty/sabre/dav/lib/DAV/CorePlugin.php - line 346: Sabre\DAV\Server->generateMultiStatus() /app/www/public/3rdparty/sabre/event/lib/WildcardEmitterTrait.php - line 89: Sabre\DAV\CorePlugin->httpPropFind() /app/www/public/3rdparty/sabre/dav/lib/DAV/Server.php - line 472: Sabre\DAV\Server->emit() /app/www/public/3rdparty/sabre/dav/lib/DAV/Server.php - line 253: Sabre\DAV\Server->invokeMethod() /app/www/public/3rdparty/sabre/dav/lib/DAV/Server.php - line 321: Sabre\DAV\Server->start() /config/www/nextcloud/apps/dav/lib/Server.php - line 364: Sabre\DAV\Server->exec() /config/www/nextcloud/apps/dav/appinfo/v2/remote.php - line 35: OCA\DAV\Server->exec() /app/www/public/remote.php - line 172: require_once("/config/www ... p")

So, how can I figure out what exactly caused the unclean shut down? I I'm also having issues with my nextcloud, where the docker crashes frequently. Could it be related to that?

For some reason, now after a system restart, triggered by regular reboot from the GUI, the system begins a parity check. Can someone please shed some light on to why? Thanks. tower-diagnostics-20230701-1622.zip

I just updated the unRaid to the latest, and noticed that it triggered parity check. Not sure why. However, in the Nextcloud logs I now see this: using keys found in /config/keys **** The following site-confs have extensions other than .conf **** **** This may be due to user customization. **** **** You should review the files and rename them to use the .conf extension or remove them. **** **** nginx.conf will only include site-confs with the .conf extension. **** /config/nginx/site-confs/default.conf.2021 [custom-init] No custom files found, skipping... [ls.io-init] done. Not sure why this came back.

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;