Hi,
I have a new installation NC 20.0.4 and a update to 20.0.5.
In both versions, I can’t install the calendar and contacts.
I get an undefined error message.
I’ve been using nextcloud for many years.
But this is new.
Who can help?
Thank you
Hallo Jimmy,
this is the output:
There are some warnings about your system configuration.
You access your instance over a secure connection, but your instance generates unsafe URLs. This most likely means that you are behind a reverse proxy and that the configuration variables for overwriting are not set correctly. Please read the documentation.
Insecure page access over HTTP. We strongly recommend that you set up the server to require HTTPS, as described in the security tips 
.
No PHP memory cache has been configured. A memory cache can be configured to increase performance. More information can be found in the documentation.
The MySQL version “5.7.32-log” is used. Nextcloud 21 will no longer support this version and requires MySQL 8 or later.
Thank you
Mario
Oy Mario…
I dunno if it’s possible to run NC only in your own LAN and keeping fully functional at the same time. That idea could be the major obstacle with your instance.
Maybe you wanna check if your instance has a working internetconnection to the world
Hello Jimmy,
the nextcloud instance runs on a TrueNASS 12.1 and I installed nextcloud as a plugin.
That’s how I did it with the versions before.
There were no problems. The NASS goes into the Internet via a router.
Greeting
Mario
MySQL has version 5.7.
is that ok?
Greeting Mario
This is more of a “NOTE:” rather than a “WARNING:”
The software is monitoring how you are accessing the interface and, using a predetermined statement, thinks you are bypassing a reverse proxy. It is saying that you are logged into your nextcloud instance from a local http://192.0.0.0 IP address which, it determines as a local secure connection “You access your instance over a secure connection”. But because it is over an http and not an https “your instance generates unsafe URLs.”
If you want to clear this out of your logs. A simple nginx install and configuration would solve this automatically redirecting all http traffic to https. Automatically redirecting all calls to http://192.0.0.0 to https://192.0.0.0 .