<![CDATA[Update, unable to connect.]]>Just ran an update from the guide here, and now MM says unable to connect

pi@magicmirror:~/MagicMirror $ git pull && npm run install-mm
Already up to date.

> magicmirror@2.24.0 install-mm
> npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/console@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/core@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/environment@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/expect@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/expect-utils@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/fake-timers@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/globals@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/reporters@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/schemas@29.4.3',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/source-map@29.4.3',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/test-result@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/test-sequencer@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/transform@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/types@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'babel-jest@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'babel-plugin-jest-hoist@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'babel-preset-jest@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'diff-sequences@29.4.3',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'eslint-plugin-jest@27.2.2',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'expect@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-changed-files@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-circus@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-cli@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-config@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-diff@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-docblock@29.4.3',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-each@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-environment-node@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-get-type@29.4.3',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-haste-map@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-leak-detector@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-matcher-utils@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-message-util@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-mock@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-regex-util@29.4.3',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-resolve@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-resolve-dependencies@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-runner@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-runtime@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-snapshot@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-util@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-validate@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-watcher@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-worker@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'pretty-format@29.5.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'write-file-atomic@5.0.1',
npm WARN EBADENGINE   required: { node: '^14.17.0 || ^16.13.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.1.0', npm: '7.11.2' }
npm WARN EBADENGINE }

> magicmirror@2.24.0 postinstall
> npm run install-vendor && npm run install-fonts && echo "MagicMirror² installation finished successfully! 
> "


> magicmirror@2.24.0 install-vendor
> echo "Installing vendor files ...
> " && cd vendor && npm install --loglevel=error --no-audit --no-fund --no-update-notifier

Installing vendor files ...


changed 3 packages in 17s

> magicmirror@2.24.0 install-fonts
> echo "Installing fonts ...
> " && cd fonts && npm install --loglevel=error --no-audit --no-fund --no-update-notifier

Installing fonts ...


up to date in 2s
MagicMirror² installation finished successfully! 


> magicmirror@2.24.0 prepare
> [ -f node_modules/.bin/husky ] && husky install || echo no husky installed.

no husky installed.

up to date in 52s
pi@magicmirror:~/MagicMirror $ pm2 start all
[PM2] Applying action restartProcessId on app [all](ids: [ 0 ])
[PM2] [MagicMirror](0) â
[PM2] Process successfully started
ââââââ¬âââââââââââââââââââââ¬âââââââââââ¬âââââââ¬ââââââââââââ¬âââââââââââ¬âââââââââââ
â id â name               â mode     â ⺠   â status    â cpu      â memory   â
ââââââ¼âââââââââââââââââââââ¼âââââââââââ¼âââââââ¼ââââââââââââ¼âââââââââââ¼âââââââââââ¤
â 0  â MagicMirror        â fork     â 76   â online    â 0%       â 584.0kb  â
ââââââ´âââââââââââââââââââââ´âââââââââââ´âââââââ´ââââââââââââ´âââââââââââ´âââââââââââ
pi@magicmirror:~/MagicMirror $

Now when I go to a browser on a local machine, I get
Unable to connect
Firefox can’t establish a connection to the server at 192.168.1.21:8080.

IP address is correct, “fixed” at router level for years.

]]>https://forum.magicmirror.builders/topic/17912/update-unable-to-connectRSS for NodeSun, 13 Sep 2026 18:01:24 GMTSat, 15 Jul 2023 15:55:06 GMT60<![CDATA[Reply to Update, unable to connect. on Sat, 15 Jul 2023 16:27:00 GMT]]>@Richard238 unable to connect is because MM is not running

next time for upgrade use my script… it checks and upgrades node/npm/pm2 if needed as well as other stuff…

https://github.com/sdetweil/MagicMirror_scripts

short fix,
a. run my upgrade script with force instead of apply
or
b. upgrade node js to 16.x (will probably be 16.20)
then do npm install again

]]>https://forum.magicmirror.builders/post/110254https://forum.magicmirror.builders/post/110254Sat, 15 Jul 2023 16:27:00 GMT<![CDATA[Reply to Update, unable to connect. on Sat, 13 Sep 2025 17:16:08 GMT]]>@Richard238 use my script
It will record incremental changes

https://github.com/sdetweil/MagicMirror-backup-restore

]]>https://forum.magicmirror.builders/post/128247https://forum.magicmirror.builders/post/128247Sat, 13 Sep 2025 17:16:08 GMT<![CDATA[Reply to Update, unable to connect. on Sat, 13 Sep 2025 15:55:30 GMT]]>@sdetweil

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

]]>https://forum.magicmirror.builders/post/128246https://forum.magicmirror.builders/post/128246Sat, 13 Sep 2025 15:55:30 GMT<![CDATA[Reply to Update, unable to connect. on Tue, 09 Sep 2025 22:11:51 GMT]]>@Richard238 said in Update, unable to connect.:

And then I remembered the orig MM was still on a SD Card before I swapped over to a USB drive

backup , backup, backup…

]]>https://forum.magicmirror.builders/post/128197https://forum.magicmirror.builders/post/128197Tue, 09 Sep 2025 22:11:51 GMT<![CDATA[Reply to Update, unable to connect. on Sun, 31 Aug 2025 15:13:17 GMT]]>@Richard238 awesome… thanks for the feedback…

]]>https://forum.magicmirror.builders/post/128093https://forum.magicmirror.builders/post/128093Sun, 31 Aug 2025 15:13:17 GMT<![CDATA[Reply to Update, unable to connect. on Sun, 31 Aug 2025 15:05:43 GMT]]>@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. :)

]]>https://forum.magicmirror.builders/post/128092https://forum.magicmirror.builders/post/128092Sun, 31 Aug 2025 15:05:43 GMT<![CDATA[Reply to Update, unable to connect. on Sun, 17 Aug 2025 13:02:42 GMT]]>@Richard238 my backup also gets the module source url for every add on module, so that they can be reinstalled again
and gets files created (like access tokens etc) which may be needed to make each module work

]]>https://forum.magicmirror.builders/post/127934https://forum.magicmirror.builders/post/127934Sun, 17 Aug 2025 13:02:42 GMT<![CDATA[Reply to Update, unable to connect. on Sun, 17 Aug 2025 12:58:44 GMT]]>@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.

]]>https://forum.magicmirror.builders/post/127933https://forum.magicmirror.builders/post/127933Sun, 17 Aug 2025 12:58:44 GMT<![CDATA[Reply to Update, unable to connect. on Sun, 17 Aug 2025 11:58:42 GMT]]>@Richard238 of course you dont need to do npm start if the other stuff fsiled

cd ~/MagicMirror 
rm package-lock.json 
rm -rf node_modules 
npm cache clean --force
npm install

let me know the results

]]>https://forum.magicmirror.builders/post/127928https://forum.magicmirror.builders/post/127928Sun, 17 Aug 2025 11:58:42 GMT<![CDATA[Reply to Update, unable to connect. on Sun, 17 Aug 2025 11:38:11 GMT]]>@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
]]>https://forum.magicmirror.builders/post/127927https://forum.magicmirror.builders/post/127927Sun, 17 Aug 2025 11:38:11 GMT<![CDATA[Reply to Update, unable to connect. on Sun, 17 Aug 2025 11:24:21 GMT]]>@Richard238 did the

npm install

complete?

do this

pm2 stop all
cd ~/MagicMirror 
rm -rf node_modules
npm install

the start MagicMirror manually

npm start
]]>https://forum.magicmirror.builders/post/127923https://forum.magicmirror.builders/post/127923Sun, 17 Aug 2025 11:24:21 GMT<![CDATA[Reply to Update, unable to connect. on Sun, 17 Aug 2025 11:22:15 GMT]]>@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);
]]>https://forum.magicmirror.builders/post/127922https://forum.magicmirror.builders/post/127922Sun, 17 Aug 2025 11:22:15 GMT<![CDATA[Reply to Update, unable to connect. on Sun, 17 Aug 2025 07:07:52 GMT]]>@Richard238 said in Update, unable to connect.:

0|MagicMirror | [2025-08-16 19:11:32.117] [ERROR] Your configuration file contains syntax errors :(
0|MagicMirror | Line 99 column 21: ‘Log’ is not defined.

This seems to indicate that there is an error in config/config.js. Run the following on the command line in the ~/MagicMirror/ directory: npm run config:check

]]>https://forum.magicmirror.builders/post/127917https://forum.magicmirror.builders/post/127917Sun, 17 Aug 2025 07:07:52 GMT<![CDATA[Reply to Update, unable to connect. on Sat, 16 Aug 2025 18:13:16 GMT]]>@sdetweil said in Update, unable to connect.:

pm2 logs --lines=20

Seems to loop through this:

0|MagicMirror  | > magicmirror@2.32.0 start
0|MagicMirror  | > node --run start:x11
0|MagicMirror  | [2025-08-16 19:11:31.316] [LOG]   Starting MagicMirror: v2.32.0 
0|MagicMirror  | [2025-08-16 19:11:31.359] [LOG]   Loading config ... 
0|MagicMirror  | [2025-08-16 19:11:31.363] [LOG]   config template file not exists, no envsubst 
0|MagicMirror  | [2025-08-16 19:11:31.976] [INFO]  Checking config file /home/pi/MagicMirror/config/config.js ... 
0|MagicMirror  | [2025-08-16 19:11:32.117] [ERROR] Your configuration file contains syntax errors :(
0|MagicMirror  | Line 99 column 21: 'Log' is not defined. 
PM2            | App [MagicMirror:0] exited with code [1] via signal [SIGINT]
PM2            | App [MagicMirror:0] starting in -fork mode-
PM2            | App [MagicMirror:0] online
0|MagicMirror  | bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
]]>https://forum.magicmirror.builders/post/127910https://forum.magicmirror.builders/post/127910Sat, 16 Aug 2025 18:13:16 GMT<![CDATA[Reply to Update, unable to connect. on Sat, 16 Aug 2025 17:48:32 GMT]]>@Richard238 pm2 logs --lines=20

]]>https://forum.magicmirror.builders/post/127909https://forum.magicmirror.builders/post/127909Sat, 16 Aug 2025 17:48:32 GMT<![CDATA[Reply to Update, unable to connect. on Sat, 16 Aug 2025 17:19:09 GMT]]>@sdetweil

pi@mmv2:~/MagicMirror $ node -v
v22.14.0
pi@mmv2:~/MagicMirror $ pm2 stop MagicMirror
[PM2] Applying action stopProcessId on app [MagicMirror](ids: [ 0 ])
[PM2] [MagicMirror](0) â
ââââââ¬âââââââââââââââââââââ¬âââââââââââ¬âââââââ¬ââââââââââââ¬âââââââââââ¬âââââââââââ
â id â name               â mode     â ⺠   â status    â cpu      â memory   â
ââââââ¼âââââââââââââââââââââ¼âââââââââââ¼âââââââ¼ââââââââââââ¼âââââââââââ¼âââââââââââ¤
â 0  â MagicMirror        â fork     â 2120 â stopped   â 0%       â 0b       â
ââââââ´âââââââââââââââââââââ´âââââââââââ´âââââââ´ââââââââââââ´âââââââââââ´âââââââââââ
pi@mmv2:~/MagicMirror $ pm2 start MagicMirror
[PM2] Applying action restartProcessId on app [MagicMirror](ids: [ 0 ])
[PM2] [MagicMirror](0) â
[PM2] Process successfully started
ââââââ¬âââââââââââââââââââââ¬âââââââââââ¬âââââââ¬ââââââââââââ¬âââââââââââ¬âââââââââââ
â id â name               â mode     â ⺠   â status    â cpu      â memory   â
ââââââ¼âââââââââââââââââââââ¼âââââââââââ¼âââââââ¼ââââââââââââ¼âââââââââââ¼âââââââââââ¤
â 0  â MagicMirror        â fork     â 2120 â online    â 0%       â 2.6mb    â
ââââââ´âââââââââââââââââââââ´âââââââââââ´âââââââ´ââââââââââââ´âââââââââââ´âââââââââââ
pi@mmv2:~/MagicMirror $
]]>https://forum.magicmirror.builders/post/127908https://forum.magicmirror.builders/post/127908Sat, 16 Aug 2025 17:19:09 GMT<![CDATA[Reply to Update, unable to connect. on Sat, 16 Aug 2025 17:04:46 GMT]]>@Richard238 can you show the startup messages

]]>https://forum.magicmirror.builders/post/127907https://forum.magicmirror.builders/post/127907Sat, 16 Aug 2025 17:04:46 GMT<![CDATA[Reply to Update, unable to connect. on Sat, 16 Aug 2025 16:05:29 GMT]]>Same issue today. Tried with force but still no MM.

node -v = v22.14.0

]]>https://forum.magicmirror.builders/post/127906https://forum.magicmirror.builders/post/127906Sat, 16 Aug 2025 16:05:29 GMT<![CDATA[Reply to Update, unable to connect. on Sun, 16 Jul 2023 11:53:04 GMT]]>@sdetweil

pi@magicmirror:~/MagicMirror $ node -v
v16.1.0
]]>https://forum.magicmirror.builders/post/110269https://forum.magicmirror.builders/post/110269Sun, 16 Jul 2023 11:53:04 GMT<![CDATA[Reply to Update, unable to connect. on Sun, 16 Jul 2023 11:33:43 GMT]]>@Richard238 no, the script did that for you already

on a command line do

node -v

]]>https://forum.magicmirror.builders/post/110267https://forum.magicmirror.builders/post/110267Sun, 16 Jul 2023 11:33:43 GMT<![CDATA[Reply to Update, unable to connect. on Sun, 16 Jul 2023 10:17:16 GMT]]>@sdetweil

Option ‘a’ fixed it, thank you.

With it working, do I need to update node?

]]>https://forum.magicmirror.builders/post/110266https://forum.magicmirror.builders/post/110266Sun, 16 Jul 2023 10:17:16 GMT<![CDATA[Reply to Update, unable to connect. on Sat, 15 Jul 2023 16:27:00 GMT]]>@Richard238 unable to connect is because MM is not running

next time for upgrade use my script… it checks and upgrades node/npm/pm2 if needed as well as other stuff…

https://github.com/sdetweil/MagicMirror_scripts

short fix,
a. run my upgrade script with force instead of apply
or
b. upgrade node js to 16.x (will probably be 16.20)
then do npm install again

]]>https://forum.magicmirror.builders/post/110254https://forum.magicmirror.builders/post/110254Sat, 15 Jul 2023 16:27:00 GMT