Sorry for my late answer, but I had to go out in the heat shoppingâŠ
I do use custom filtering, but my goal is a bit differentâŠ
I wanted to filter out irritating system users from the user list shown in Nextcloud. Itâs hard to explain to clients for what all those (Samba / Windows) System users / groups are doing in NC⊠Theyâre not needed in NC and are there just because NC uses AD AuthentificationâŠ
So I use a Nethserver-AD group called nextcloud-users, and that is the basis for any user (group) to be displayed in NC (eg for sharing). So no confusing system users to explain to my clientsâŠ
Itâs a bit confusing. After the upgrade to Nextcloud 21 I have 2 mysql databases in the system. The one in /var/lib/mysql contains the old db used by nethserver.
And where sits the other one? â/opt/rh/rh-mariadb105/root/bin/mysqlshow --socket=/var/run/rh-mariadb105-mariadb/nextcloud-mysql.sockâ gives me the correct answer. But how can I backup the nextcloud database? I use the app quick notes which get saved in the database. So it would be good to know where that is.
Not a stupid question but if you have two databases you failed to upgrade, could you check the messages logs and show us the content of the upgrade (please use a gist to display the log message lines )
Do you mean 2 nextcloud databases, or do you mean one database nextcloud at the new mariadb 105 and all other nethserver databases at the old place mariadb 55?
Hello
Or the latest updated nethserver and also nextcloud, everything seems to work but I can no longer log in with admin with the default password Nethesis, 1234
after updating to the final version, I now have these warnings in the log:
There are some errors in your system configuration.
Some files have not passed the integrity check. Further information can be found in our documentation. (List of invalid files ⊠/ Analyse againâŠ)
Your web server is not properly set up to resolve â/ocm-provider/â. This is most likely related to a web server configuration that has not been updated to deliver this folder directly. Please compare your configuration with the supplied rewrite rules in â.htaccessâ for Apache or those provided in the Nginx documentation on its documentation page. On Nginx, these are typically the lines beginning with âlocation ~â that need an update.
Your web server is not properly set up to resolve â/ocs-provider/â. This is most likely related to a web server configuration that has not been updated to deliver this folder directly. Please compare your configuration with the supplied rewrite rules in â.htaccessâ for Apache or those provided in the Nginx documentation on its documentation page. On Nginx, these are typically the lines beginning with âlocation ~â that require an update.
