Jessie

If you are using the client, there is a checkbox in settings which restricts to 500mb. You need to uncheck it.

Try uninstalling the nextcloud office app and reinstall. Then goto settings and make it refind the path.

I have one machine on 25. The only notable issue initially was the password app not working. The solution was to set the upgrade flag to beta but dont update nextcloud. This made the beta version of password available for download. Switched back to stable after I got it. Problem solved.

Rule 1. Always upgrade nextcloud via the app before upgrading the docker. Else use krusader and go to the nextcloud folder. There will be backup folder in there. Select the most recent or the one before that and copy it in the corresponding position in appdata. Rename the old nextcloud folder to nextcloudbad. Rename the copied folder to nextcloud. Restart nextcloud. If lucky you will boot back to the previous version. Login and start the upgrade again. Then upgrade the docker.

Hi, Is anyone using the new backup app in nextcloud? Any tutorials to assist in setup? I've found one on youtube but in a different language. Having trouble with the barrier.

A longshot, but there is an unraid app called nerdtools. Python might be in there. Just switch it on to load it.

I'm probably the last person to work this out, but I thought i'd put it out there. I've found that you get a big improvement in response time with nextcloud in unraid if you pin a dedicated cpu and thread to the nextcloud docker.

Remove the entries for the exclude field and just include disk 10 and 11. You normally only have one or the other on the share. You might need to migrate the directory on disk 5 to disk 10 or 11. eg use unbalance to move it. After all gone frrom disk 5, ,you should be right.

Using Samsung evo 980 nvme's. Regularly getting temp warnings for 84 degrees C. Surely a bug.

I have had success dumping vbios on a ASUS Gt1030. Tried on a new machine the other day and got a warning that the file might be a bit small. (<> 50kb) The previous dumps on the same card were around 130k. The 50 k version also does not work. Cant explain what went wrong other than I might have done the good dump using unraid 6.9.2 and the bad one using 6.10.3. Could the unraid version be a factor?

Be patient with it. Update is cantankerous at best. Standard procedure for me is start the update process. Wait untul the crash. Press the back button to go back to previous menu. (The update menu) Wait. It is still performing the update. Try again. If the procedure is still in progress, press back and wait some more. Eventually you will get back to the update procedure and it will be waiting at the next step. Press continue and repeat above as long as it hasnt passed maintenance mode. If it has passed maintenance mode, dont go back. Just wait for a while, then try again. You should get there eventually.

Also in unraid, you can lock the share down. Make it invisible to smb and restrict access. On;y nextcloud can get to it.

In the old docker template in unraid, the password was in there. It is now hidden in the new template I think you may find it in config.php in nextcloud. Else, I think your physical data is safe in the nextcloud directory. It is only the database that is corrupted. Pretty sure you can rebuild your database from the source files but not on top of that yet.

Use notepad++ or your preferred editor and edit ssl.conf. It is in there. delete the hash in front to activate it. Then refresh your check to hopefully get the tick.

So do you have to insert that key in the token field when you define your server or does it happen in the docker?

Thanks. I'll go for a look.

I'm on a learning curve with this, but I created an A record for my domain and pointed t to my server. (rustdesk.mydomain.com) Then I opened the ports in the router. Then I went to the rustdesk site and downloaded the clients. To point the clients to my server I changed the config in the client to point to rustdesk.mydomain.com Then the connection between the clients was similar to a teamviewer connection. Not sure about encryption with this docker. Have asked the question

I have done the experiment and it seems to work. What about encryption though? Is the docker set to use encryption? how do we access public and private keys during setup?

Unraid v6.9.2 I have a machine which will periodically drop a drive. The array has 3 drives and a parity. Any of the drives can drop. To repair, I rebuild the drive and all will be good until the next one drops. The computer is a ryzen7 2700 with 16gb ram Power supply is a 650w Coolermaster bronze semi modular. It runs a windows vm and nextcloud with its associated dockers in the background. It also has a couple of 500gb ssd's for the cache. I have included the logs from the last crash. Can anyone help me as to a possible cause? younghometower-diagnostics-20220504-1733.zip

I have had plenty of success doing this procedure in conjunction with the unassigned drive plugin and the drive physically plugged into the unraid server. My question is, is it possible to do this procedure by connecting the source disk as a SMB share? eg leave the disk in the original machine and connect via "Add Remote SMB" If possible, what would be the syntax of the qemu-img convert command for the source? I second guessed "qemu-img convert -p -O raw /mnt/remote/name of share ....blah blah But it did not recognise the source.

As of 11/4/22 the collabora docker crashes and burns in unraid. You manually start it. It stops a few seconds later. No config file will fix this. I went to UNRAID forums and cannot find a reference to collabora and CHVB in the same sentence. Does that mean it is abandoned? Edit A workaround. If you put collabora/code:21.11.2.4.1 in the repository field in the unraid docker template, it will load the last known working version of collabora. Not a fix, but at least it unbreaks it.

I'm still on a learning curve for this as as well but i've found you need to recreate the users before scan:all will work.. And you can't create the user if the file for that user exists in the store. so I used krusader to rename the file in the store. eg user = test to testa. Then I created user = test. Then I went back to the store and there is now a new user = test. I then deleted user = test with krusader and renamed testa to test. Repeat for all other users. (Good luck if you have a hundred of them) Restart then run scan --all I'm sure there must be an elegant way to copy the users over from the old database, but I don't know how to do it. Seems noone else does either. I've asked the question numerous times here and the best answer was "I did that not too hard." which of course is no help to anyone. I notice there is a new line in the linuxserver mariadb template which suggests it might merge a database but the documentation is almost non existent, so no idea whether it would do it or what it actually does anyway. Edit. I missed a step. After you recreate the users, you need to log into each one so nextcloud creates the profile. Then you go to krusader and delete the new user and unrename the file you changed earlier. The usernames are case sensitive so make sure the unrename matches the case of the newly created username

The gui updater has its moments. It seems to time out before completing the task. The work around is to press the back button on the browser, go back to settings and wait. The task is still working in the background. After a couple of minutes press update and it will be waiting for you at the next step. I find it usually crashes at create backup and downloading. Each time it does go back wait then proceed. After the updater gets past the enable maintence mode step, dont go back to settings else you will need to go to console and turn it off with commands. It will probably hang on "move new files into place". Wait a few seconds, try again and it will eventually get to the end. I wouldn't do a ctrl c because that would stop the process.

In the swag docker, set port 80 to 8088. Then in your router make sure you have forwarded ports 80 to 8088 to the ip address of your unraid server. Also forward port 443 to the unraid server. Then in the unraid interface, go to settings/managementaccess and set "use SSL/TLS" to no. This will disable the unraid interface from the internet which is a personal choice else there will be a clash on port 443. My preference for outside access to the unraid interface is via a vpn tunnel. (More secure imo) If you want the unraid interface to access the internet you have to change settings for port 443.

If you are obtaining certificates via http, have you pointed port 80 and 443 in your router to the unraid server? 80 and sometimes 443 are usually redirected to other ports in the swag docker) Also have you created an "A" record or a cname for collabora.yourdns.com to point to your server?