Problems with calender and Nextcloud

Pakmann

of course :-) i uses O (not zero)

sdetweil

@Pakmann just do wget nextcloud-url

Pakmann

looks like the direction to find the root cause is good.

Get following response:

GnuTLS: A TLS fatal alert has been received.
GnuTLS: received alert [70]: Error in protocol version

Now i remember, a few months ago i configure the nginx to TLS1.3. Maybe its not compatible with MM ?

sdetweil

@Pakmann wget is not MM, and it also fails

Pakmann

hmm… each other devices are running:

Phone, Tablet or try to download the ICS directly in a desktop browser. Should be sometink on the PI ?

sdetweil

@Pakmann where did u configure tls3? may have to do the same on pi

Pakmann

nextcloud is hostet on a separate pi. here the nginx is configured for TLS1.3

MM is on another PI.

sdetweil

@Pakmann so the nginx system is the gateway… all things must speak tls3…
so you now need to config MM pi to peak tls3

Pakmann

@sdetweil
Today i solved the problem regarding TLS1.3 connection. Wget is working fine and i can download the ICS data.
On MM side i have the same issue like before. No data is shown in calender. When i start the MM its still the same error message :-(

sdetweil

@Pakmann looks like you will have to add a parameter to the launcher to enable tls 1.3

https://developer.ibm.com/blogs/migrating-to-tls13-in-nodejs/

my adding this to the script starting MM (either mm.sh or run-start.sh)

Enable TLS1.3 using CLI options
With Node.js 11.x or 10.x, you can use the --tls-max-v1.3 CLI option to enable TLS1.3 by default. It can be provided directly on the command line, or set in the environment with NODE_OPTIONS=–tls-max-v1.3. The option can also be specified to Node.js 12.x, even though its already the default.

export NODE_OPTIONS=--tls-max-v1.3