Problems with calender and Nextcloud

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

sdetweil

@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 window

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

Pakmann

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

@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-x

you don’t know if what you read is real or needs 4 hours more of investigation…

Pakmann

@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?

sdetweil

@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

Pakmann

@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

@Pakmann booooo