I had the same Problem. I disabled all Modules and Test which one make the problems. It was the Google Maps Traffic Module.

@sdetweil as you wish i opened issue #1891. Its my first one, i hope everythink is ok

Looking forward for an solution :-)

Hi together,

a few weeks ago i had a chat with Sam regarding TLS1.3 Support. We Need newer Libs for NodeJs etc. This was no problem to reinstall MM with newer Packages. Problem was the Calendar Module which Not Support TLS1.3.

A complete solution should be usefull to be state of the art.

Regards
Pak

today i reconfigured the cloud system to TLS1.2 to make a check. Its working.
I check the access log also and found the request:

"GET /remote.php/dav/calendars/USER/personal/?export HTTP/1.1" 200 79020 "-" "Mozilla/5.0 (Node.js 10.2) MagicMirror/2.9.0 (https://github.com/MichMich/MagicMirror/)"

Very curious here is the information about the request with Nodejs 10.2. On the system 10.2 should not be available. When i check the version, v12 is visible.

Do you have any dependencies in MM Code to the old NodeJS ?

Its just a stro, but maybe here is the root cause ?

@sdetweil
short overview what i did…

cp -r /home/pi/MagicMirror/ /home/pi/MagicMirrorOLD/
suro rm -r /home/pi/MagicMirror/

Download script and change NODE_TESTED = “v12.1.0”

Update to NodeJS V12:

 curl -sL https://deb.nodesource.com/setup_12.x | sudo bash -
 sudo apt-get install -y nodejs

Install new MM

 bash raspberry.sh

Copy old config

cp /home/pi/MagicMirrorOLD/config/config.js /home/pi/MagicMirror/config/

I delete all modules, only standard configuration with weather etc. Calender of course.
Set TLS1.3 and start MM:

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

Result: In your link from IBM is written in NodeJS 12 TLS1.3 is configured by default. It doesnt matter if i set the export expression or not. I still get an error message regarding TLS. Same like before.

I could not finde somethink how i can check if TLS1.3 is really configured in NodeJS.

@sdetweil i know what you mean. this is what i really hate on linux side. A lot of dependencies… you have to update on package? Welcome on highway to hell.

Netherleless, on buster stable Node 10.17.0 is installed. This is the version what i used. Obviously wont work.

Found this: https://github.com/nodejs/node/issues/27666
When i understood it right the feature is not implemented on 10.x ? The ticket for the implementation is still open

It could be a solution to update Nodejs to v11 or v12. Any estimation if MM is compatible so far? Or other ideas?

it could so easy… :-(

pi@MagicMirror:~/MagicMirror $ export NODE_OPTIONS=--tls-max-v1.3
pi@MagicMirror:~/MagicMirror $ npm start
node: --tls-max-v1.3 is not allowed in NODE_OPTIONS

@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

@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 :-(

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

MM is on another PI.

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 ?