If perhaps it could show the nature of the error?
And the route to the logs, because most of us have to look up where they are! ;-)

Noticed neither of my two calendars were working on my MM over the weekend.
Not having time to investigate, I left it for another day.
Then one calendar worked but not the other, then they swapped over!
Now they’re both working.
On checking the logs, there are a lot of these timeout errors:

[2025-12-07 16:11:33.349] [ERROR] Calendar Error. Could not fetch calendar:  https://calendar.google.com/calendar/ical/#################group.calendar.google.com/private-5##############################/basic.ics TypeError: fetch failed
    at node:internal/deps/undici/undici:13510:13
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
  [cause]: ConnectTimeoutError: Connect Timeout Error (attempted address: calendar.google.com:443, timeout: 30000ms)
      at onConnectTimeout (/home/pi/MagicMirror/node_modules/undici/lib/core/util.js:876:19)
      at Immediate._onImmediate (/home/pi/MagicMirror/node_modules/undici/lib/core/util.js:845:11)
      at process.processImmediate (node:internal/timers:485:21) {
    code: 'UND_ERR_CONNECT_TIMEOUT'
  }

Looks like a timeout error at calendar_dot_google_dot_com and nothing to do with MM.
However, a more user friendly error message in place of the failed calendar would be nice to see.

@sdetweil

Hahhahaaaa! Yes, well I do make regular backups of config and CSS, it was the modules folder I was missing. Lesson learned there.

@hs said in Embed Grafana Charts - xframe issue:

allow_embedding=true

For future me and of course anyone else looking for this, the setting is in the [Security] section of /etc/grafana/grafana.ini (Assumes Grafana is hosted on a Pi or other Linux distro)

@sdetweil

I couldn’t use that as I the Pi had no network, no file manager. It was bricked :(

New OS, new default vanilla MM all good.

And then I remembered the orig MM was still on a SD Card before I swapped over to a USB drive.
Copied all I needed, seems to be all good so far!

Thanks for your help. :)

Apologies if this request is in the wrong place…

MMM-doomsDay isn’t listed anywhere, yet is still on GitHub and working just fine on my MM.
What’s the reason for it not being on the module list or the module wiki page?

Thank you.

+1 for this, please. I have a Pi Aware in the loft and would be interested in adding its data to MM.

@sdetweil

Pi (Pi4 in metal heat-sink case) was running really warm. Powered it off and left it for a while.

Powered on, it has no networking and file manager does nothing.
If I can get networking enabled, I’ll make a config and CSS backup.

Looks like it’s going to need an OS reinstall which will have to wait until I have time to do so.
I’ll report back when that’s done.

@sdetweil

pi@mmv2:/ $ pm2 stop all
[PM2] Applying action stopProcessId on app [all](ids: [ 0 ])
[PM2] [MagicMirror](0) â
ââââââ¬âââââââââââââââââââââ¬âââââââââââ¬âââââââ¬ââââââââââââ¬âââââââââââ¬âââââââââââ
â id â name               â mode     â ⺠   â status    â cpu      â memory   â
ââââââ¼âââââââââââââââââââââ¼âââââââââââ¼âââââââ¼ââââââââââââ¼âââââââââââ¼âââââââââââ¤
â 0  â MagicMirror        â fork     â 300  â stopped   â 0%       â 0b       â
ââââââ´âââââââââââââââââââââ´âââââââââââ´âââââââ´ââââââââââââ´âââââââââââ´âââââââââââ
pi@mmv2:/ $ cd ~/MagicMirror
pi@mmv2:~/MagicMirror $ rm -rf node_modules
pi@mmv2:~/MagicMirror $ npm install
npm error code EIO
npm error syscall read
npm error errno -5
npm error EIO: i/o error, read
npm error A complete log of this run can be found in: /home/pi/.npm/_logs/2025-08-17T11_35_16_106Z-debug-0.log
pi@mmv2:~/MagicMirror $ npm start

> magicmirror@2.32.0 start
> node --run start:x11

/bin/sh: 1: ./node_modules/.bin/electron: not found

@mumblebaj said in Update, unable to connect.:

npm run config:check

pi@mmv2:~/MagicMirror $ npm run config:check

> magicmirror@2.32.0 config:check
> node js/check_config.js

[2025-08-17 12:14:16.030] [INFO]  Checking config file /home/pi/MagicMirror/config/config.js ... 
[2025-08-17 12:14:16.285] [ERROR] Your configuration file contains syntax errors :(
Line 99 column 21: 'Log' is not defined. 

Lines 97/98/99:

                // Override start method.
                start: function () {
                    Log.log("Starting module: " + this.name);