Update issues with Nextcloud - extra file solvable_files.sh

[EazyFreight]

I am self hosting next cloud and to be honest I have given up on updating it as it work with the version I was using and trying to update just became tiresome and to be honest I was scared I made things worse…

The first issue I want to cover is the encryptiom key reset

It hangs here. it doesnt matter how long I leave it, it will not go past this… What do I need to do?

second issue is updates. I have treid countless times over the last year or so but now I am more determined as the version I am running will no longer be supported

The following extra files have been found:
solvable_files.sh
unsolvable_files.sh

The statement makes it seem as though they are surplus to requirement which shouldnt be there but upon searching, it looks as though they are required files

There has to be an easier way to manage next cloud!

[tflidd]

@EazyFreight

The statement makes it seem as though they are surplus to requirement which shouldnt be there but upon searching, it looks as though they are required files

Yes they are not supposed to be there. What resource makes you think they are required?

@EazyFreight

It hangs here. it doesnt matter how long I leave it, it will not go past this… What do I need to do?

The encryption module was designed for external storage, if you are on fully self-hosted environments, there is no real benefit to it.
The key files are protected with the user’s password, if you change it, the passwords of the keyfile has to be changed. What I am not sure, if it is just the password of the main key, or if all the file keys have to be changed. In the latter case, this can take some time.

If processes take a long time and might trigger an error, it is required to check the log files for more information. Like this, we cannot guess what goes wrong.

Problem with the encryption module, if it does not bring any or just little more security, you have a lot of code and complexity added to your system.

[EazyFreight]

Unknown MySQL server host issue with solvable_files.sh script

@gmarques - I have the same issue. I suspect that solvable_files.sh doesn’t support snap installations, but I’m out of my depth trying to modify it to do so. With snap you need to use nextcloud.mysql-client to access the database. In my case I have broken mdates on both client and server files. Updating the client files’ mdate didn’t fix the problem (although I do now get green ticks), nor did updating the server files’ mdate.

this mentions the files and that they are required for snap updates.
I am not sure what update procedure is used. I installed nextcloud via the plesk terminal and get the same error wether I try up update via plesk or directly via the app.

[EazyFreight]

I moved solvable_files.sh and unsolvable_files.sh to a different folder and the updater worked.

What is the purpose of these files? Why did they end up there? Am I safe to permanently delete them

After the update, I now have a new problem… Where Nextcloud was working fine with an older version. I now have

this has been there for quite a while

[jtr]

@EazyFreight

What is the purpose of these files? Why did they end up there? Am I safe to permanently delete them

They’re not part of Nextcloud. Presumably they’re files you placed there at some point manually. Technically they appear to be (based on the names) the scripts that were distributed around to those impacted by a bug in the Desktop client several years ago. You can safely delete them.

After the update, I now have a new problem… Where Nextcloud was working fine with an older version. I now have

Check your Nextcloud log (nextcloud.log). We can’t guess.