Read the statement by Michael Teeuw here.
Problems with calender and Nextcloud
-
@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
-
@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
-
@Pakmann said in Problems with calender and Nextcloud:
pi@MagicMirror:~/MagicMirror $ NODE_OPTIONS=–tls-max-v1.3
you must export the env variable, else it is not passed to children processes,
issue this command from the terminal windowexport NODE_OPTIONS=--tls-max-v1.3
-
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
-
@Pakmann looks like that only works with node 10.16 and above… love when they leave out that little detail!..
https://stackoverflow.com/questions/57839965/how-to-use-tlsv1-3-with-nodejs-10-xyou don’t know if what you read is real or needs 4 hours more of investigation…
-
@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 openIt could be a solution to update Nodejs to v11 or v12. Any estimation if MM is compatible so far? Or other ideas?
-
@Pakmann the installers (my new one and the current) are both forcing node V10.
we haven’t tried 11/12 as far as I know… wanna test!?
download my script,
curl -sL https://www.dropbox.com/s/rlh710ng0zwv3vp/raspberry.sh?dl=1
edit the NODE_TESTED=“v10.1.0” at the top to V11.1.0 or V12.1.0
and give it a try… of course this is a re-install, so rename the current MM folder out of the way -
@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.
-
@Pakmann booooo
-
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 ?