0 votes
Frankly, I am disappointed that I am having to make this post at all. I expect more from a paid feature.

Has anyone else came across these installation issues on a fresh install and what are the procedure to resolve it. The

Security & setup warnings
It's important for the security and performance of your instance that everything is configured correctly. To help you with that we are doing some automatic checks. Please see the linked documentation for more information.

There are some errors regarding your setup.
Some files have not passed the integrity check. Further information on how to resolve this issue can be found in the documentation. (List of invalid files… / Rescan…)
MySQL is used as database but does not support 4-byte characters. To be able to handle 4-byte characters (like emojis) without issues in filenames or comments for example it is recommended to enable the 4-byte support in MySQL. For further details read the documentation page about this.
Your web server is not properly set up to resolve "/.well-known/caldav". Further information can be found in the documentation.
Your web server is not properly set up to resolve "/.well-known/carddav". Further information can be found in the documentation.
No memory cache has been configured. To enhance performance, please configure a memcache, if available. Further information can be found in the documentation.
The PHP OPcache is not properly configured. For better performance it is recommended to use the following settings in the php.ini:
The database is missing some indexes. Due to the fact that adding indexes on big tables could take some time they were not added automatically. By running "occ db:add-missing-indices" those missing indexes could be added manually while the instance keeps running. Once the indexes are added queries to those tables are usually much faster.
Missing index "calendarobject_calid_index" in table "oc_calendarobjects_props".
Missing index "schedulobj_principuri_index" in table "oc_schedulingobjects".
This instance is missing some recommended PHP modules. For improved performance and better compatibility it is highly recommended to install them.
Some columns in the database are missing a conversion to big int. Due to the fact that changing column types on big tables could take some time they were not changed automatically. By running 'occ db:convert-filecache-bigint' those pending changes could be applied manually. This operation needs to be made while the instance is offline. For further details read the documentation page about this.
Please double check the installation guides ↗, and check for any errors or warnings in the log.

Check the security of your Nextcloud over our security scan ↗.
Tuesday, December 22 2020, 03:53 AM
Share this post:
Responses (1)
  • Accepted Answer

    Tuesday, December 22 2020, 11:11 AM - #Permalink
    0 votes
    If it ever comes out, the upgrade to NC19 may fix some of these.

    Before fixing MySQL, note ClearOS uses the system database, so system-mariadb. The problem with fixing the 4-byte support in MySQL is that it is global, so I have no idea what it does to the rest of the database.

    See the documentation for fixing the .well-known. You need to update your /usr/share/nextcloud/.htaccess. It is dangerous to fix this programatically in case another program has set them (e.g SoGo sets them)

    You can fix the missing indices and big int support yourself using the commands mentioned, but note the mention of taking NC offline to do the big int conversion. I think the upgrade to NC19 will fix some or all of these.

    I am not sure why we get the opcache.... warnings. I get the warnings but the values are set on my system:
    [root@server ~]# grep opcache.enable= /opt/rh/* -r
    It could be that NC is incorrectly reading the base /etc/php.ini rather than the one for the version of PHP being used by NC. I think opcache.enable is defaulted on in 7.3 - My NC19 Beta runs 7.2 and you can see it is on.

    Note that NC works without all these issues being cleared. They are only warnings.
    The reply is currently minimized Show
Your Reply