Problems with calender and Nextcloud

sdetweil

two ways to see things

1… use npm start to start the mirror, not pm2… then messages will be displayed on the terminal window.
you should see the fetcher for calendar created and any errors in the fetch process
2. on the Mirror UI do ctrl-shift-i to open the developers window, and then select the tab labeled console, and scroll up… you can also filter the messages, by putting part of the module name in the filter field.
‘calendar’ for example (no quotes)

Pakmann

@sdetweil
Great, Thanks for the instructions.

I try step one and obviously i get an error during loading calender content (Link to calender replaced):

Calendar Error. Could not fetch calendar:  CALENDER LINK { Error: write EPROTO 19413              98784:error:1409442E:SSL routines:ssl3_read_bytes:tlsv1 alert protocol version:../../vendor/node/deps/openssl/openssl/ssl/record/rec_layer_s3.c:1407:SSL alert n              umber 70

    at WriteWrap.afterWrite [as oncomplete] (net.js:833:14) errno: 'EPROTO', code: 'EPROTO', syscall: 'write' }

For Step 2 i have the problem to have only access with an putty terminal at the moment.

Any idea so far what the error message means ?

sdetweil

@Pakmann said in Problems with calender and Nextcloud:

version:…/…/vendor/node/deps/openssl/openssl/ssl/record/rec_layer_s3.c:1407:SSL

how did u configure the url in the config.js

http://
or
https://

Pakmann

My nextcloud server accept only https connections. I checked it with the config.js - it is https

sdetweil

@Pakmann try

wget -o  your nextcloud_url

on the terminal window…

i think the calendar fetcher is having trouble negotiating the ssl (https) handshake…

Pakmann

@sdetweil said in Problems with calender and Nextcloud:

wget -O

Maybe it is to late on my side… The request told me i dont have an URL in the request…
Request like below.

wget -O https://www.google.de

sdetweil

@Pakmann

but I said

wget -o  your nextcloud_url

whatever the https://… nextcloud thing is in config.js

Pakmann

yes, i try the complete URL for download die ICS file from nextcloud kalender. Include credentials inside the link:

 wget -O https://USER:PASSWORD@DOMAIN/remote.php/dav/calendars/USER/personal/?export
wget: URL fehlt
Aufruf: wget [OPTION]... [URL] …

sdetweil

@Pakmann just remove the -o parm

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

Pakmann

@sdetweil
for a first try i set the option directly via termine and start MM. Same result like before - i got an error message for SSL.

pi@MagicMirror:~/MagicMirror $ NODE_OPTIONS=–tls-max-v1.3
pi@MagicMirror:~/MagicMirror $ npm start

Anythink wrong here ? Any idea how i can check if the option was accepted correctly?

On buster stable nodejs 10.17.0 is availble. But i found the binaries for v12. Obviously after an update i have other problems :D Therefore its better with v10 so far