Read the statement by Michael Teeuw here.
Error in the calendar module check logs for more details
- 
 @sdetweil I’ve got the same issue since today. Any other solutions? To change the fetchtimeout doesn’t help. 
- 
 @Niggich but it should recover and fetch again 
- 
 @sdetweil later I’ll try. The version is the last one 
- 
 @sdetweil Today everything is working normally. I don’t know what happend yesterday. 
- 
 @Niggich network congestion probably… there have been some severe DNS denial of service (hacking) storms in the last few days 
- 
 @sdetweil Ok, maybe. For me the problem is solved. 
- 
S sdetweil has marked this topic as solved on
- 
 @sdetweil 
 I’m sorry Sam, I didn’t figure out where I have to configure the
 mmFetchTimeout. Where is it located? Thanks
- 
 I put it here in config.js module: "calendar", header: "Our Calendar", position: "bottom_right", config: { mmFetchTimeout: 60000, calendars: [
- 
 @nowayto it is an environment variable So you add it to the script used to launch MagicMirror If using my installer and select pm2 then its ~/MagicMirror/installers/mm.shBefore the npm start line 
 For 45 secondsexport mmFetchTimeout=45000
- 
 @sdetweil Did it. Hope it solve my issue. Thanks 
