Nextcloud warning 'check_for_working_wellknown_setup'

Support
,
1

NS8 with nextcloud Hub9

there is a warning:

Es gibt einige Warnungen in der Systemkonfiguration.

    `check_for_working_wellknown_setup` ist in deiner Konfiguration auf "false" gesetzt, daher wurde diese Prüfung übersprungen.

Bitte überprüfe noch einmal die Installationsanleitungen ↗ und kontrolliere das Protokoll auf mögliche Fehler oder Warnungen.

or in english:

There are some warnings in the system configuration.

    `check_for_working_wellknown_setup` is set to "false" in your configuration, so this check was skipped.

Please review the installation instructions ↗ and check the log for any errors or warnings.

Is it possible to change the settings ?
or is it the neth standard configuration ?

2

The same here. But this does not harm the function of the Nextcloud. At least I don’t notice any restrictions

1 Like
3

I think the check doesn’t work as Nextcloud is running behind a reverse proxy so it’s disabled, see also Reverse proxy — Nextcloud latest Administration Manual latest documentation

1 Like
4

Hi,

I’ve The following messages in Nextcloud

  • One or more mimetype migrations are available. Occasionally new mimetypes are added to better handle certain file types. Migrating the mimetypes take a long time on larger instances so this is not done automatically during upgrades. Use the command occ maintenance:repair --include-expensive to perform the migrations.

  • Detected some missing optional indices. Occasionally new indices are added (by Nextcloud or installed applications) to improve database performance. Adding indices can sometimes take awhile and temporarily hurt performance so this is not done automatically during upgrades. Once the indices are added, queries to those tables should be faster. Use the command occ db:add-missing-indices to add them. Ontbrekende indexen: “dav_shares_resourceid_type” in table “dav_shares”, “dav_shares_resourceid_access” in table “dav_shares”, “oc_npushhash_di” in table “notifications_pushhash”, “fs_name_hash” in table “filecache” Voor meer informatie word je verwezen naar de documentatie↗.

  • check_for_working_wellknown_setup is set to false in your configuration, so this check was skipped.

Not a big issue i think, but would be nice have them set correctly
How can i do this the best way

5

runagent -m nextcloud(no.of your instance) occ maintenance:repair --include-expensive

runagent -m nextcloud(no.of your instance) occ db:add-missing-indices

And then be happy…

2 Likes