skois

Also if anyone could explain when to use Websocket Support and Cache Assets (or what is the benefits/cons of using them) Thanks!

hey guys, does your NPM have updated to 2.7.1? Im stuck at 2.6.2, Tried force update, tried remove and reinstall, tried setting :latest as a tag. Nothing worked. EDIT* Now i realised this isn't the official docker image, i'll have to wait until this image is updated to 2.7.1

I'm happy it worked! I changed my timout settings to 7200 yesterday (from 3600) ill check on next update if its enough! I'll try to remember to mention here! If you see an update just ping me to remind me lol!

Just instead of hitting retry on updater, refresh the page. i'm updating my "produciton" docker and my test docker all the time like this!

I think update:check might only check for app updates but not sure. What does the gui updater says?

occ should be in /usr/bin/occ probably something is wrong with the config.php. After rollback, try updating from gui as i mentioned

If you are running LSIO docker, click on the docker icon and open console. There you can run the commands directly like "occ update:check" So, try - occ update:check - occ upgrade - updater.phar if nothing works. try - occ maintenance:repair and try the above again. And a tip while updating from GUI. When a step times out. DONT hit retry, it still running on the backgroud, just the gui timed out. Just refresh the page, it will ask you if you are sure, hit yes. If its still running it will tell you that is in progress, keep refreshing every 20seconds until its done, when its done it will take you back to GUI updater and then hit continue update EDIT* Also upload your config file, something seems misconfigure because updater couldnt read config.php. Maybe when you changed maintenace mode you made a typo? EDIT2* This is the steps I would do.

I didn't find a fix yet, i believe we must change something in nginx.conf (not in php) because LSIO runs on nginx not apache. Also we might have to do the same on the reverse proxy config. And warn you that all "failed" uploads are stored in /mnt/user/nextcloud/USER/uploads. So i tried 4 times a 11GB file and there was 4 11GB files there consuming space. This folder is the 1st folder the new uploaded files go until they are processed. So if you dont upload anything and you see files there (its probable the failed uploads) should be safe to delete

While i got the same error, after a minute or two, i refreshed the web and the file was there, so it might be a false positive!

I'm getting the same error, so now i have to investigate it also lol

Ok, give me some time, trying a 11G file through web. With client it will continiue syncing the other files if one fails (i think) and it will tell you which failed. For the 1st big transfer you can use filesytem copy and then runn occ:scan --all but not letting you transfer big files is something that need to fix.

What browser you using?

Have you changed your php-local.ini value ? *upload_max_filesize=10G* Are you trying to upload from web? or with desktop client?

You can also change the max upload size in /config/php.php-local.ini This how i have mine setup *i dont know if this is the fix for your problem, i mention it because you said you move large files *"Ignore" the pdlib section is there for the facerecognition, doing some tests ; Edit this file to override php.ini directives and restart the container date.timezone = Europe/Athens upload_max_filesize=20G memory_limit=8G max_execution_time=3600 max_input_time=3600 [pdlib] extension="pdlib.so"

I'm using model 4. Check progress with occ face:progress It should automatically group people, but you can force it with occ face:background_job Then go to settings, personal, face recognition You might have to wait a sec to load. You will see a button "there are more persons to recognize" Press this and it will ask you to name a person Sent from my Mi 10 Pro using Tapatalk

Aah, sorry. if you dont have any data on plugins like tasks/calendar etc. You can start a db from scratch and occ files:scan --all occ files:scan-app-data if you dont have any private data and you dont mind. i can give it a try to repair your db. just send me a zip of your appdata (broken)

Ouch! i have set it to 3. i find its the sweet spot. Any luck repairing?

You can also try repairing your broken ibdata1, https://dba.stackexchange.com/questions/45991/mysql-ibdata1-corrupt but i can't help you more. i have no idea about mysql inner workings sorry and gl!

Sorry, put back the ibdata from the working mariadb and then start nextcloud Sent from my Mi 10 Pro using Tapatalk

Always have backups ofc Sent from my Mi 10 Pro using Tapatalk

OK, delete ibdata and iblogs. Start nextcloud and hopefully it will create this file and all your dB data will be there. (I'm the databases/nextcloud folder) I m not sure about this, but this is what I would do.. Sent from my Mi 10 Pro using Tapatalk

and the ib_logfileXX files also!

try to copy also the ibdata1 file from broken to working appdata

Ok one more try before starting from scratch. Put back the working appdata folder. run the mysqlcheck -u nextcloud -p --auto-repair --check nextcloud to confirm we have no errors. copy from the broken appdata folder the "nextcloud" folder to the working appdata folder (its inside databases folder). and run agian mysqlcheck -u nextcloud -p --auto-repair --check nextcloud to see what you get.

Yea, you can keep a copy of the working appdata folder also just in case.