MagicMirror is Failing to start at all

[Sampleswow]

@sdetweil
pi@raspberrypi:~/MagicMirror $ bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)” apply
update log will be in /home/pi/MagicMirror/installers/upgrade.log
doing test run = false
Node currently installed. Checking version number.
Minimum Node version: v22.14.0
Installed Node version: v24.4.1
Check current Node installation …
Node currently installed. Checking version number.
Minimum Node version: v22.14.0
Installed Node version: v24.4.1
No Node.js upgrade necessary.
Check current NPM installation …
NPM currently installed. Checking version number.
Minimum npm version: V10.9.2
Installed npm version: V11.4.2
No npm upgrade necessary.

want /var/swap=200MByte, checking existing: keeping it
saving custom.css
local version 2.32.0 already same as master 2.32.0
restoring custom.css
pi@raspberrypi:~/MagicMirror $

Still will not start

[sdetweil]

@Sampleswow

Because you did this manually the script will abort if the same version is already

I provide another option, instead of apply use
force
At the end of the command

I don’t document this because I dont want everyone using force and getting into more trouble.

[Sampleswow]

@sdetweil
So i used the force protocol and it took some time and did some things. after it was done i attempted to start the MM using both the old way and they way the release notes said and i still get this,

pi@raspberrypi:~ $ cd MagicMirror
pi@raspberrypi:~/MagicMirror $ npm start

magicmirror@2.32.0 start
node --run start:x11

node: bad option: --run
pi@raspberrypi:~/MagicMirror $ node --run
node: --run requires an argument
pi@raspberrypi:~/MagicMirror $

[sdetweil]

@Sampleswow can you show the output of

node -v

[Sampleswow]

@sdetweil
pi@raspberrypi:~ $ node -v
v24.4.1
pi@raspberrypi:~ $ cd MagicMirror
pi@raspberrypi:~/MagicMirror $ node -v
v24.4.1

[sdetweil]

@Sampleswow thanks

Try this

sudo n 22.14
hash -r
node -v

You should get 22.14 or 22.15

Then try npm start in the MagicMirror folder

[Sampleswow]

@sdetweil
pi@raspberrypi:~ $ sudo n 22.14
copying : node/22.14.0
installed : v22.14.0 (with npm 10.9.2)
pi@raspberrypi:~ $ hash -r
pi@raspberrypi:~ $ node -v
v22.14.0
pi@raspberrypi:~ $ cd MagicMirror
pi@raspberrypi:~/MagicMirror $ npm start

magicmirror@2.32.0 start
node --run start:x11

node: bad option: --run
pi@raspberrypi:~/MagicMirror $

[sdetweil]

@karsten13 have any debug advice here?

[karsten13]

@sdetweil

can you see what I’m doing right now ;)

I used my containers a few minutes ago to see if I can reproduce but I can’t. So no idea.

[sdetweil]

@Sampleswow ok, it makes no sense

I would suggest starting over
Reflash the SD card
Use the script to Install

[Sampleswow]

@sdetweil
is that the only way? I have a lot of setup, I would hate to lose by starting over.

also again What script i have no idea what your referring to, or how to use it. I am a basic user of Magic Mirror

[sdetweil]

@Sampleswow

I have two sets of scripts, install/update are listed in the MagicMirror doc

Install/upgrade
https://github.com/sdetweil/MagicMirror_scripts

Backup/restore, which can save your MagicMirror setup and place it in a GitHub repo, with versions (it does not backup folders, only info required to restore the config onto a new MagicMirror install.).

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

You can backup Your config now, copy off system, upload to GitHub as part of backup
config.js, custom.css, all the installed modules and where they came from. And any new files they created

I always recommend using a new SD card anyhow, just in case there is something (which I will fix)

Nodejs is just a tool we use to launch Our app, and run our code.
I don’t see any reports of problems like this so, I don’t know

[KristjanESPERANTO]

If --run is a bad option let’s try run the long command directly and see what happens.

So instead of npm run, try this:

On Wayland:

WAYLAND_DISPLAY="${WAYLAND_DISPLAY:=wayland-1}" ./node_modules/.bin/electron js/electron.js --enable-features=UseOzonePlatform --ozone-platform=wayland

On X11:
DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js

This may show us the real core of the problem, or it works and starts MM properly and we could make it a little more comfortable (even if it is a bit hacky).

[Sampleswow]

@KristjanESPERANTO said in MagicMirror is Failing to start at all:

DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js

This Command STARTED my Mirror!!!

Im super excited everything is the way I left it even no loading google images lol (I know i have to find and alternative now )

[sdetweil]

@Sampleswow awesome

edit the package.json
and change the “start”
to “startx”
then add this line after

"start":"DISPLAY=${DISPLAY:=:0} ./node_modules/.bin/electron js/electron.js",

then

npm start

should start your MagicMirror

this was the way it was before this release

[Sampleswow]

@sdetweil
That worked i picked the right start because there is apparently 2 of them in the text code

[Sampleswow]

@sdetweil
Update for the Jan 1 2026,
This no longer fixes the issue. I used your update script and now i get this error;
sh: 1: ./node_modules/.bin.electron.js: not found

[sdetweil]

@Sampleswow should not say electron.js

Do

cd ~/MagicMirror 
ls node_modules/electron

If not found do

npm install electron@39.2.7

If successful
Do

npm start

Please advise

[Sampleswow]

@sdetweil
That fixed it for now. I guess will talk again next update lol, Thank you for your dedication to resolving my issue!

[sdetweil]

@Sampleswow can you send me the ~/MagicMirror/installers/upgrade.log
Via email.

The same userid as here at gmail