Read the statement by Michael Teeuw here.
Problems with calender and Nextcloud
-
@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 ?
-
@Pakmann I got no clue… we are using the latest request module (2.88.0)
it does say special parms required for SSL 3 (and there is currently no way to pass something like this into be used)
https://www.npmjs.com/package/request#tlsssl-protocol
I do see in the calendar code, setup for the request id info
"User-Agent": "Mozilla/5.0 (Node.js "+ nodeVersion + ")
-
Hey,
3 month later and no solution?
i tried with newest version. wget nextcloud_calender_url get the calender in special format. The Name is “7863TJr9N2JJRgfG?export” and not *.ics.i tried official documentation. Add i “auth” with copy and paste, i get a config error.
in the newest build of Nextcloud i can copy a abo-link. i can download the “.ics” with this link without credentials.
how i can use it for mm calender? its a puplic calender link now but i dont get any calender infos.
my config:
{ module: "calendar", header: "Kalender", // see help for more information position: "top_left", config: { colored: true, coloredSymbolOnly: false, calendars: [ { url: 'https://domain.tld/nextcloud/remote.php/dav/public-calendars/7812hello1232JJRgfG?export', symbol: 'calendar' }, ], } },
-
@Corin-Corvus said in Problems with calender and Nextcloud:
https://domain.tld/nextcloud/remote.php/dav/public-calendars/7812hello1232JJRgfG?export
that url doesn’t work here… domain.tld not found
3 month later and no solution?
no one interested in looking at the code to fix it… this is all volunteer…
if u have the ics file,
copy the ics file into the default calendar folder
the url would then be
file:///home/pi/MagicMirror/modules/default/calendar/???.ics -
Ok, I realise it’s been a while but, for the sake of other who might hit this problem (or one like it), us Nextcloud users are generally using it because we’re security-conscious and like to keep our data private.
If you’re like me, you might have enabled 2FA which means if you enter your ‘usual’ password in your config file, you can’t then enter your second authentication method.
If this is the case, you’ll need to create a ‘one-time’ password in Nextcloud and use this instead of your ‘normal’ password. Get one by going to Nextcloud settings, Security and scroll to bottom. Hit ‘Create new app password’ and copy to the URL in the config.