OPCache needs to be disabled - Is that forever?

I have also tried to activate OPcache in the system in the PHP area, but unfortunately I have not succeeded. Therefore, I would like to join you.

I would also like to know a solution to the other messages.

Since there are some tips on the Internet for resolving such messages for standard Linux installations, I was able to resolve such messages relatively easily in VMs and native installations with Nextcloud. With Grommunio, however, the Linux is "rebuilt", so it's not quite as easy.

So, if you have a native installation of Grommunio on Debian, so Debian is a standard Linux as I meant, such as Ubuntu or Suse. So maybe search in the internet in connection with Nextcloud for solutions in the different in the forums.

Andy I have managed to locate the files to resolve some of these warnings/errors but not all of them. See below:-

This is for the Grommunio OpenSuse appliance (built on the 28-12 ISO)

Locate the directory:- /usr/share/grommunio-common/nginx/locations.d

Edit the file grommunio-files.conf

Update the lines as follows:-
add_header X-Robots-Tag none always;
add_header X-XSS-Protection "0" always;
to
add_header X-Robots-Tag "noindex, nofollow" always;
add_header X-XSS-Protection "1; mode=block" always;
also add this line at the end of the add_header block
add_header Referrer-Policy no-referrer always;

Save the file

Now edit the file grommunio-dav.conf

change the first 2 lies from
rewrite ^/.well-known/caldav /dav redirect;
rewrite ^/.well-known/carddav /dav redirect;
to
rewrite ^/.well-known/caldav /files/remote.php/dav redirect;
rewrite ^/.well-known/carddav /files/remote.php/dav redirect;

Save the file

Add these to your build notes and notes for whenever Grommunio-Files get an update (as in early February 2024), as these settings get set back to their original values.

I haven't tracked down the /.well-known/webfinger or /.well-known/nodeinfo warning fixes yet, doesn't seem much info out on the web for this.

I have also played around with the OPCache settings but never got anywhere, then saw @WalterH's article about OPCache form a week more so ago and decided as it has known issues with Grommunio it was time to leave well alone. Anyhow, @WalterH also mentioned that we should try another caching option, php8-ACPu, but this has been included since December last year according to @mwilliams , and when I tried to load it that was confirmed as it said it was already installed. Whether it is working or not I do not know.

Maxx in a way that you have a solution already

Then I apologize that you understood it in that way. If I knew that for Debian, I would share that. I can tell you something in connection with a NC in a VM from Hansson IT, or when it comes to a native installation on Synology NAS. As you may know, each distribution has a slightly different approach to problems and that's where my advice comes from.

Mister2 locate the files to resolve some of these warnings/errors but not all of them

Same here. Many thanks for the instructions, four messages goes away.

Mister2

Some remarks:

• this way you block (and terminate) the integration of grommunio-office which does need to inject to files to allow a seamless interaction.

• in the next paragraph you redirect caldav and carddav away from grommunio-dav to grommunio-files, breaking the integration with some DAV clients that want to access calendar/contacts.

• the failings of opcache are unfortunate, however APCu is a good replacement and is confirmed and certified to work with grommunio and also grommunio-files.

• for nodeinfo and webfinger we have replaced these to be "well-known", ignoring them.

@mwilliams Thanks for your comments on this. There seems very little discussion/input from the community and development team regarding Grommunio Files (GF) in this forum - in fact most of the posts here concern the core Grommunio product (mail). After many years in the IT industry I have developed a general dislike for applications giving warnings/errors so started looking at what files were causing the errors being reported in the GF Admin console.

If the changes I have made/suggested to reduce the warnings/errors in the GF Admin Console should not be made, then what should we be doing to remove the entries in the console. These warnings/errors have been posted a few times by contributors on this forum, but to date I have not seen any direct input from the development team as to what we should be doing to resolve them. As an analogy, if I have a warning light appear on my car dashboard I need to find out what is causing it and fix it, not just drive around with the light on. The same goes for software, if it generates a warning/error I want to fix it before some big goes wrong (potential loss of data).

Some other points.
Does the APCu product need any configuration. OPCache has a large config file to control how it works, but nothing has been said about APCu. It is good to know that it is included in the latest build ISO's for the appliance, but does that also go for those who use the other versions of Grommunio (I can't recall if that was mentioned in @WalterH article or not). If there are tweaks that can or should be made, where can we find the information, to get the best performance for the product.

@mwilliams for nodeinfo and webfinger we have replaced these to be "well-known", ignoring them

If these have been replaced, why does the console still generate an error/warning. It makes us (the user) think there is something wrong when there probably isn't.

As a user of the Community version, I expect to get some errors/warnings from time to time, but some guidance from the development team would be useful. Clearly, in GF the errors are not critical as it works OK without making changes, its just I have spent many years trying to get rid of these types of messages so it has become a habit to try. I know there are probably far more important issues for the developers to work on as this is only an issue for those of us who dislike seeing errors.

Finally, I really do appreciate the hard work that the 'Grommunio Team' having been doing on the whole product over the nearly 2 years I have been using the product.

Mister2

You might want to check out grommunio-files-26.0.12.

For APCu: While there are possibilities to enrich APCu (see also https://www.php.net/manual/en/apcu.configuration.php), this is not really required for default setups.

Finally, thanks for the kind words. The best appreciation for open source software is the support through customers. So if it is of any value for you as it seems, feel free to consider the purchase of a subscription and get all the extra benefits from it.

Andy

When the check is running, you get a prompt, you should enter valid credentials and you will see that all your checks are green. You need to authenticate because as mentioned before, CalDAV and CardDAV are not provided by files but by grommunio-dav instead.

I confirm

If I know in the right way, since v2023.11.3 from Feb. 2024 php8-APCu is included per default in all appliances.

Maxx
I am also on Debian 12 with grommunio and Nextcloud. Grommunio uses php8.2 therefore i disabled opchache for php8.2 and installed php8.3 in addition because it is possible to have opcache disabled for php8.2 but enabled for php8.3.
In the nginx vhost of Nextcloud i specified php8.3-fpm as my upstream php handler.
So this is my temporary workaround, until the bug with opcache is fixed in grommunio.