Default Calendar & Nextcloud Calendar - CERT_HAS_EXPIRED

[sdetweil]

@basicuser said in Default Calendar & Nextcloud Calendar - CERT_HAS_EXPIRED:

Cannot find module ‘request’

sure

see above

[BasicUser]

@sdetweil I got it figured out by just running npm install request in ~/MagicMirror/

Not super sure what you’re referring to when you say see above though.

[sdetweil]

@basicuser sorry, wrong topic
https://forum.magicmirror.builders/topic/15665/mmm-rtsp-stopped-working-on-2-17-help/2?_=1633110498656

[LdwVII]

Great info in this thread, thank you!

Weirdly enough, I’m still experiencing the CERT_HAS_EXPIRED error on the Calendar module, despite updating MagicMirror to 2.17.1.

Had the certificate error on quite a few modules prior, the update fixed all except the Calendar one. Did I miss something or is it perhaps an entirely different error?

(What kind of certificate is this anyway? I had thought an http request wouldn’t need any.)

0|launchMa | [03.10.2021 09:15.33.458] [ERROR] Calendar Error. Could not fetch calendar:  http://kalender.link/ical/best FetchError: request to https://kalender.link/ical/best failed, reason: certificate has expired
0|launchMa |     at ClientRequest.<anonymous> (/home/pi/MagicMirror/node_modules/node-fetch/lib/index.js:1483:11)
0|launchMa |     at ClientRequest.emit (events.js:315:20)
0|launchMa |     at TLSSocket.socketErrorListener (_http_client.js:469:9)
0|launchMa |     at TLSSocket.emit (events.js:315:20)
0|launchMa |     at emitErrorNT (internal/streams/destroy.js:106:8)
0|launchMa |     at emitErrorCloseNT (internal/streams/destroy.js:74:3)
0|launchMa |     at processTicksAndRejections (internal/process/task_queues.js:80:21) {
0|launchMa |   type: 'system',
0|launchMa |   errno: 'CERT_HAS_EXPIRED',
0|launchMa |   code: 'CERT_HAS_EXPIRED'
0|launchMa | }

[sdetweil]

@ldwvii https uses encryption to protect your data while traveling across the internet.

to do this, the receiving host must have registered to support that encryption.

it does this by recording it’s url and encryption type with a certificate authority ( not just anybody can be an authority), they give back a file with a key, with a specific lifetime. ( so u can’t have old sites with bad security hanging around forever)

well the authorities also have expiring rights.
in this case the authority’s certificate expired. (it’s a chain ) … and there was a bug in electron that didn’t handle it correctly

now, in your case u use an unprotected url ( no longer allowed as a standard)

http://kalender.link/ical/best

no ‘s’ on http and it was redirected to secure (https)… maybe the redirect sent to the wrong place…