@joseph I did not. I will try restoring from backup to make a copy.
In the meantime I have created a cifs share on a windows machine, added it as a volume in cloudron, attached that volume to the failed nextcloud instance, rsynced all the data out of it over to the cifs share, and added that file share to all the users computers.
I have been trying to get off using windows for our file shares for a few years and we had cutover to nextcloud on cloudron about a month ago.
The nextcloud client update process has been a consistent pain point across all users, in one instance losing the ability to sync properly requiring it to be uninstalled and reinstalled to get the files to sync even though the client said they were already in sync, silent un perceptible to the user failure that resulted in them using files they thought were up to date but were older versions.
Now with the entire instance going offline when there was no software update and the only app we had installed in the instance was onlyoffice it is making me question if this is reliable enough to depend on.
I have setup another nextcloud instance without only office and just leaving everything complete vanilla and am working on figuring out how to move the files over and then get users's connected to the new instance.
I am not super particular about what tool we use but I really want to get rid of company wide file shares.
We need to have paths that windows programs can save files into and read them from easily, all the paths are shared with everyone in the company. Really wish cloudron just had Samba as an app or something like that so we could use shared storage across the company.
Looking around it looks like there are large production deployments of nextcloud so it should be the right tool for our use case. I don't see other's having issues like this running it on cloudron so maybe this is a one off and isolated just something in our environment.