skois

I just migrated on my test server from postgres to linuxserver/mariadb (10.4). How i can know if 4byte support is enabled? After conversion i see this on my config.php But using dbeaver i see Default charaset: uft8 Default Collation: utf8_general_ci also on variables i see binlog_format: MIXED tx_isolation: REPEATABLE-READ Docs says to change to binlog_format: ROW tx_isolation: READ-COMMITTED If needed, How i can fix the above?

Hey, is there any way to remove the playback delay at all? I can't understand why it have so much delay (10sec+) I saw on a lot of posts that is because we are playing from browser. Blue iris does play via browser too but the delay is max 1sec. (Note that this delay is while 3 users watching all the streams *3 for now*) I really like shinobi, but this delay is a deal breaker I have tried every codec and "fix" i found online but cant get it down from 8-10 secs..

You probably tried to execute the command on the unraid's terminal. This command is to be runned bu the nextcloud container. So, click on the NC docker and click console. Run the mentioned command there

The command is in the first line of the warning... occ db:add-missing-primary-keys Also this have nothing to do with the updater errors you got on the updater. On this version NC made some changes in the database, and need to add some primary keys

Today i did some further investigation. When i uploaded a file and gave me the 504 error i open dev tools on chrome and noticed the url path. included the "dav" So i mapped in Windows a network driver with webdav. Tried to upload 1gb file, it copied the file almost all. and it stuck at 99% (it was then uploading it to server) So after waiting for about 1 minute i got an error saying i should check my connection and try again. I though it was a random error because 1 min to upload 1gb with 20mbps is too fast. Tried again. about a minute in again. error. Tried 4gb, same time. With some math 20mbps in one minute can upload a little more than 100MB. Then it hit me. Cloudflare proxy free tier have 100mb limitation on uploads (that also is a hint that webdav does not do any chunking.) So i set my nextcloud CNAME on cloudflare to DNS only instead of proxy. BOOM files start to upload correctly. Problem solved right? Nop. There is a new limit now. I can upload with mapped webdav drive until 2gb. (2gb +1 byte failes instantly). (This needs further investigation) So now was the time to test file uploads from WebGUI. 2GBs (exactly) uploaded succesfully! 2.1GB also succesfully! (Didn't expect that) Now trying 4GB file. *EDIT1* 4GB returned the 504Error. I'll start looking on the reverse proxy nginx timeout configs.. *EDIT2* Changed some timeouts to 15min on NPM and now i got "Error when assembling chunks, status code 524" instead of 504. ill try again with some huge time outs like 1day and see what happens. *EDIT3* I use NginxProxyManager, after adding my proxy host i go to /mnt/user/appdata/NginxProxyManager/nginx/proxy_host/numberoftheNChost.conf i copied the whole "location / " block and then i edited again the proxy host though webui (npm webui), Advanced tab. Pasted the location / block and added the following lines. proxy_connect_timeout 1d; proxy_send_timeout 1d; proxy_read_timeout 1d; send_timeout 1d; Anywhere in the block doesn't matter. After that a 5gb file upload is completed successfully. When i had it at 15min it didn't work, probably because the whole upload took almost an hour. I don't upload usually that large files through web gui but its nice to know that if i need to it will work ok. Also there is open issue on nginxproxymanager github that someone asks to add the feature to edit the timeout from withing the gui. So we might see it there soon. I think for now this is where my quest ends *EDIT4* The above config helps also on the updater! No longer times out! (Just updated to NC 21 Beta1 on my test server. NC21 feels a bit faster! BUT even if it succeeds it does not make ANY sense. Cloudflare shouldn't block this upload though webgui because of the chunking. If i'm not mistaken default chunking size is 10mb. Actually the upload was never blocked just failed assembling (but not!) If you wait a minute and refresh the page. The file is uploaded correctly and playable. This might be a timeout setting. I'll edit the last part later when file upload completes and if i have more findings

Ok if the file size is the problem only, then let's start with simple "fixes" go to path/to/appdata/nextcloud/php edit your php-local.ini The part you actually need is the first and specifically post_max_size. The rest is just optimizations i did. If you want you are welcome to include them. ; Edit this file to override php.ini directives and restart the container date.timezone = Europe/Athens upload_max_filesize=16G memory_limit=8G max_execution_time=7200 max_input_time=7200 post_max_size=16G max_file_uploads = 200 default_socket_timeout = 7200 ; Enable PHP OPcache https://docs.nextcloud.com/server/latest/admin_manual/installation/server_tuning.html#enable-php-opcache opcache.enable=1 opcache.interned_strings_buffer=8 opcache.max_accelerated_files=10000 opcache.memory_consumption=128 opcache.save_comments=1 opcache.revalidate_freq=1

Please link the post on the NC community, ill try to find the said files!

I'm trying to tune preview generator, and i found this https://ownyourbits.com/2019/06/29/understanding-and-improving-nextcloud-previews/ Which suggets running occ config:app:set previewgenerator squareSizes --value="32 256" occ config:app:set previewgenerator widthSizes --value="256 384" occ config:app:set previewgenerator heightSizes --value="256" while the heightSizes works fine. the other 2 gives me root@24b78faef1b1:/# occ config:app:set previewgenerator widthSizes --value="256 384" Too many arguments, expected arguments "command" "app" "name". config:app:set [--output [OUTPUT]] [--value VALUE] [--update-only] [--] <app> <name> When i try with 1 value only it works. The same syntax have on the github page of previewgenerator. Which it doen't work also. Any ideas?

Click on next cloud docker and open it'd console. There you run the command Sent from my Mi 10 Pro using Tapatalk

HSTS by itself it wont do anything, you need to use something like cloudflare which there you can enable HSTS. I dont know much about it. This is what i read somewhere. Caching assets i had it on on everything, but one day i had some problems with nextcloud. If you run NPM on the same machine as your services you reverse proxy. I don't think you will get any benefit by caching them. Also caching is only beneficial on static content. If you have much static content and you need more speed, I would create a cloudflare account and cache it there. This is all the info i could give, i'm sure the big brains here will help you more!

I will look into that, but i guess it will have its downsides also? Any good starting point to read? Thanks!

I need some help with networking, i have NC behind reverser proxy (NginxProxyManager). When i access the cloud.mydomain.com from the local network and transfer files, the speed is awful because the file has to go public and come back here. How i can setup my pfsense to route the cloud.mydomain.com to my local NC address. And i do that. Should i also change the config to NOT overwrite host to cloud.mydomain.com?

Ok, i made some edits that improved a little the "Error when assembling chunks". Edited the file in appdata/nextcloud/php/www2.conf adding the following UNDER the [www] ; Tune PHP-FPM https://docs.nextcloud.com/server/latest/admin_manual/installation/server_tuning.html#tune-php-fpm pm = dynamic pm.max_children = 150 pm.start_servers = 15 pm.min_spare_servers = 10 pm.max_spare_servers = 30 Also on appdata/nextcloud/php/php-local.ini i have the following date.timezone = Europe/Athens upload_max_filesize=16G memory_limit=8G max_execution_time=7200 max_input_time=7200 post_max_size=16G max_file_uploads = 200 default_socket_timeout = 7200 ; Enable PHP OPcache https://docs.nextcloud.com/server/latest/admin_manual/installation/server_tuning.html#enable-php-opcache opcache.enable=1 opcache.interned_strings_buffer=8 opcache.max_accelerated_files=10000 opcache.memory_consumption=128 opcache.save_comments=1 opcache.revalidate_freq=1 Note that some of the above options are redundant. But i decided to group the together so i know what's going on. Tried to upload a 1,5GB file and completed fine (before i was getting the error). Trying now a 4GB file. Will edit soon to let you know how it goes. Aaaaand i got the error again

So, i did some testing, and looks like the nextcloud instance is "locked" at 20Mbps max. I tried to upload from desktop client a new file (2gb) and the max speed i could see on task manager was 20Mbps. At the same time i tried to upload from the Web, another 2gb file (different), speed was bouncing from 0-20mbps on both streams, but always the total was 20mbps. Then i tried to upload from a different device, (maybe was limit per ip?) When the upload started, the speed is again split. but the total was never more than 20mbps. All this tests done in the same lan through the reverse proxy. I dont have a solution yet. but this might help some people look for a solution! So, the main problem here is the reverse proxy. When i tried uploading the same from web by using the container ip instead of the domain name. It is uploading at 100-200Mbps (which is again slow considering the 1Gbps ethernet link) but more reasonable. This could be fixed for internal transfers with a NAT rule maybe?

Can you try force update the docker again and try using mail without my fix (might the new update fixed it and fix is not needed?) If not working try then to apply the fix again and see if the error comes up again. I just checked for updates but it says up to date. And i dont have this error..

So to enter nextcloud docker console, click on the docker icon and select console option unfortunately nextcloud docker doesn't include rsync, but since you know that with krusader did that in about 10 sec. While on docker's console do cp input_path output_path e.g. cp /data/admin/files/testfile.mp4 /data/test/testfile.mp4 if you want to cp folder you have to do it like this cp -r /data/admin/files/ /data/test/ If it takes lot more that 10 seconds for the same file. Probably something is up with the docker engine? Not sure what you cause that. But this will help you narrow it down

Download speed and upload speed shouldn't be a database problem. Database is only read to list the files and tell you the path where the file is stored so you can start downloading. And written when you uploaded the file to store the path and the Metadata. If you copy a file from nextcloud's console from the data dir to another dir in the docker, what speeds you get? Try with rsync I thing it can report speeds Sent from my Mi 10 Pro using Tapatalk

I have enabled it on all, didn't see any problems or any difference when disabled, so I left it on! But I'll keep an eye if I have any problem Thanks!! Sent from my Mi 10 Pro using Tapatalk

Thanks! Sent from my Mi 10 Pro using Tapatalk

linux is case sensitive. on your mount "/mnt/user/downloads/completed/Music" change it to music

Also linux is case sensitive to on your remote path "/mnt/yser/downloads/completed/Music" change it to music

[emoji6][emoji6] Sent from my Mi 10 Pro using Tapatalk

Trigger re-scan

If you want to map a share via external storages, you don't map it in the docker template. You just go to external devices and fill the forms. You just have the share to be visible on network. On host put your server ip address and on share put the share path excluding the /mnt/user/ Sent from my Mi 10 Pro using Tapatalk