Cloudron Forum

@whitespace I see that earlier in the thread you said you had no backups. But just wanted to double check, if you had any (even ancient ones) ? The reason is config.php has passwordsalt and secret which is what is used to hash the db entries. https://github.com/nextcloud/server/issues/34780 has some suggestions which may or may not work .

As for your question, not a nextcloud expert, but if I had to guess user settings and password will be reset since the data files is only the files.

I think we have to 100% move to auto-generated passwords for the initial user in apps from the next release. We will make this a priority.

@whitespace ask @BrutalBirdie about his magic with Zabbix. Perhaps this is an option for your use case.

@nebulon So throwing off the unused linux images and restarting unbound helped. Consider it solved. Thank you.

Thanks, it works.

@nebulon Thanks! If that´s the case, we will be patient and wait for it to find its way upstream.

Thank you very much for resolving the issue. I would love to understand what i did wrong.

I tried deleting the nginx.conf and certs and let them be regenerated as you have described in other threads. Yet I did not manage to get nginx back up and running. Are there additional steps besides deleting cofings, restarting box, nginx and unbound?

Muchas Gracias for saving the day!

Solution:

./bin/tootctl media remove

has an option

--days

which defaults to 7 days of not set.

Our instance is only 3 days old. Since i did not set the flag it defaulted to 7 days.
The system did everything right. There were no files as old or older than 7 days. Accordingly it did not delete anything. Computer smart.

I was able to delete the cached media files.