Jessie

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?

If the old instance doesn't work anymore, you could copy the files directory for your username in the nextcloud store file. (These files should be intact.) Then connect the client in your new instance to the copied files directory and let them sync back. Not elegant but would work.

I have a nextcloud instance running on a MYSQL docker. I can't upgrade beyond V20 because MYSQL needs a later version. Can anyone share a procedure to migrate the data to Mariadb?

1 store your data on the array (in the nextcloud folder) and cache it. Unraid will manage it overnight. If the database doesn't agree with the store contents try opening a console and entering sudo -u abc php /config/www/nextcloud/occ files:scan --all. Allegedly it will rebuild the database.

Upgrade nextcloud first (In nextcloud settings.) It will move progressively up to v22. Then upgrade the docker. With each upgrade check and fix security settings along the way.

Need to set up subdomain for collabora eg collabora.mydomain.com as well as cloud.mydomain.com and point them to your server. Then declare them in swag and check the logs for certificate creation. Run them all under proxynet. Check the config file in swag relating to collabora as well as cloud.Don't forget to rename them as .conf. Then configure collabora in nextcloud settings. Otherwise no idea.

Not expert on this but move the data to the nextcloud folder. I assume you have created the users. You then need to update the database. Open a shell and put this in.. sudo -u abc php /config/www/nextcloud/occ files:scan --all Then go to bed and don't hold your breath.

Which version of nextcloud? I've come across an issue when upgrading to v21, then upgrading to latest mariadb docker. The fix was to revert Mariadb to an earlier version. All good again after going to V22.

I'm trying to create a simple method to switch between 2 operating systems which share a common GPU. I created 2 scripts in script editor to shut down the working operating system and boot the other. However I don't want the user to access the unraid GUI. Is it possible to run these scripts from the operating system vm interface by clicking an icon?

I put a post up on page 195. Try that.

Try installing Bruteforce then go to settings and whitelist the gateway. Else install a pfsense vm and move your router onto that. (Last option not a 5 minute job)

Are you using unraid and the linuxserver.io docker? abc user is relevant to that. other setups use a different username which slips me atm. It might be worth getting it out of maintenance mode. if abc doesn't work go to the config.php file and there will be a line for maintenance mode in there. set it to false or "0" then restart. It might give you the opportunity to have another go. What version are you on? and what are you trying to update to? One of the traps is to update the docker before you update nextcloud itself. Docker at some point updates to a later version of php which nextcloud can't handle if too old. I think this happened back around v15 to 17. As a general rule, always update nextcloud first before updating the docker.

Not at the moment, but I see them as potentially useful. Why take them out? How much overhead does it add to the system? I guess if they were removed, if the function could be available as an addin if needed?

Thanks. I'll have a look.

Care to share steps with us? In my case it is my main nextcloud database. Mysql support is going away, so I want to get it right. Or I will guess. 1/ Backup mysql database 2/ Load mariadb docker and point to nextcloud store 3/ Import mysql database into mariadb. Couldn't be that simple could it? Are there any other steps needed. If it fell apart, could I simply turn the mysql docker back on and back to square 1? Help appreciated...

Will do