Read the statement by Michael Teeuw here.
Problems with calender and Nextcloud
-
@Pakmann try
wget -o your nextcloud_urlon the terminal window…
i think the calendar fetcher is having trouble negotiating the ssl (https) handshake…
-
@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 -
but I said
wget -o your nextcloud_urlwhatever the https://… nextcloud thing is in config.js
-
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] … -
@Pakmann just remove the -o parm
-
of course :-) i uses O (not zero)
-
@Pakmann just do wget nextcloud-url
-
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 versionNow i remember, a few months ago i configure the nginx to TLS1.3. Maybe its not compatible with MM ?
-
@Pakmann wget is not MM, and it also fails
-
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 ?
-
@Pakmann where did u configure tls3? may have to do the same on pi
-
nextcloud is hostet on a separate pi. here the nginx is configured for TLS1.3
MM is on another PI.
-
@Pakmann so the nginx system is the gateway… all things must speak tls3…
so you now need to config MM pi to peak tls3 -
@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 :-( -
@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 startAnythink 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?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login