I also noticed you added a dedicated handleRestart.test.js with 210 lines of unit tests covering
both the pm2 and standalone code paths — that’s really impressive and goes well beyond just a
quick fix. Having proper test coverage for this kind of dual-mode behavior is exactly the right
thing to do. Much appreciated!

Thanks for the incredibly fast turnaround and the quality of the fix. Consider this confirmed
working on:

• MagicMirror 2.34.0
• MMM-Remote-Control 4.2.4
• Node.js v22, Electron 39.5.2
• Raspberry Pi 5, Debian 13 (Trixie)
• pm2 with file-watch

Warmest regards,
Ralf

The fix is included in v4.2.4: when MMM-Remote-Control detects it’s running under pm2 (via PM2_HOME or pm_id environment variables), it now skips app.relaunch() and only calls app.quit(), letting pm2 handle the restart cleanly.

Would be great if you could confirm it works on your setup!

1. URL parameter: ?apiKey=YOUR_KEY
2. HTTP header: Authorization: apiKey YOUR_KEY

Also, starting with v4.2.4 the error message now directly hints at the solution, so the next person running into this should find it faster 🙂

after a long time I finally managed to see your “new” modul.
First of all: Thanks a lot for your effort, again - nice piece!

In the past few days I’ve completely rebuilt my mirror and migrated it to trixie as well as to the actual mirror and node versions.

I ran into a reproducible issue with the restart functionality when MagicMirror is managed by pm2 (which is the recommended setup per the official MagicMirror documentation).

The Problem

When triggering a restart via the Remote-Control UI (or the /api/restart endpoint), MagicMirror enters an endless crash-loop with EADDRINUSE: address already in use :::8080.

Root Cause
The handleRestart function in node_helper.js (lines 717-741) uses the Electron-native restart mechanism:

const {app} = require("electron");
app.relaunch();
app.quit();

This works fine in standalone mode, but creates a race condition with pm2:

1. app.relaunch() spawns a new Electron instance (child of the current process)
2. app.quit() terminates the current Electron instance
3. pm2 detects the termination as a crash and spawns another Electron instance
4. Now two Electron instances compete for port 8080 → EADDRINUSE → both crash → pm2 keeps restarting → infinite loop

The only way to recover is to manually identify and kill the orphaned Electron process, then trigger a clean restart via touch config.js (which pm2’s file-watch picks up).

Interestingly, the catch-block fallback for server mode (lines 726-739) already does it correctly — it calls process.exit(0) and lets the process manager handle the restart. The Electron code path just doesn’t account for the pm2 scenario.

Possible Fix

When running under pm2, the Electron-native app.relaunch() should be skipped entirely.

pm2 can be detected via environment variables like PM2_HOME, pm_id, or PM2_USAGE:

handleRestart (query, res) {
  try {
    const {app} = require("electron");
    if (!app) { throw "Could not get Electron app instance."; }

    // When running under pm2, don't use app.relaunch() — pm2 handles restart
    if (process.env.PM2_HOME || process.env.pm_id !== undefined) {
      Log.log("Running under pm2, exiting cleanly for process manager restart...");
      this.sendResponse(res, undefined, {action: "RESTART", info: "Exiting for pm2 restart..."});
      setTimeout(() => app.quit(), 1000);
      return;
    }

    this.sendResponse(res, undefined, {action: "RESTART", info: "Restarting Electron..."});
    app.relaunch();
    app.quit();
  } catch (error) {
    // ... existing server mode fallback ...
  }
}

Environment

• MagicMirror 2.34.0
• MMM-Remote-Control 4.2.2 (commit b854832)
• Node.js v22, Electron 39.5.2
• Raspberry Pi 5, Debian 13 (Trixie)
• Process manager: pm2 with file-watch on config.js

Workaround

For now, I’ve documented this for my setup: never use the restart button in Remote-Control. Monitor ON/OFF works fine, only the restart is
affected.

Thanks for considering this — happy to test any fix if needed!

Warmest regards,
Ralf

hey guys…

having some issues using the shutdown/reboot commands…they throw this error, even though I have the API key in the config

{“success”:false,“message”:“Forbidden: API Key Not Provided!”}

here’s the config

            {
                    module: 'MMM-Remote-Control',
                    // position: 'bottom_left', // Required to show URL/QR code on mirror
                    // you can hide this module afterwards from the remote control itself
                    config: {
                            showModuleApiMenu: true,
                            secureEndpoints: true,
                            apiKey: "111111111-2222-3333-4444-555555555555",
                            customCommand: {
                                            monitorOnCommand: 'loginctl unlock-session 1',
                                            monitorOffCommand: 'loginctl lock-session 1',
                                            shutdownCommand: 'systemctl poweroff',
                                            rebootCommand: 'systemctl reboot',  // Optional, See "Using Custom Commands" below
                                            },

            }
            },

i figure it out…had to append the apiKey at the end of the url for all commands
http://192.168.1.5:8888/api/command/rebootCommand?apiKey=111111111-2222-33333-4444

having some issues using the shutdown/reboot commands…they throw this error, even though I have the API key in the config

{“success”:false,“message”:“Forbidden: API Key Not Provided!”}

here’s the config

            {
                    module: 'MMM-Remote-Control',
                    // position: 'bottom_left', // Required to show URL/QR code on mirror
                    // you can hide this module afterwards from the remote control itself
                    config: {
                            showModuleApiMenu: true,
                            secureEndpoints: true,
                            apiKey: "111111111-2222-3333-4444-555555555555",
                            customCommand: {
                                            monitorOnCommand: 'loginctl unlock-session 1',
                                            monitorOffCommand: 'loginctl lock-session 1',
                                            shutdownCommand: 'systemctl poweroff',
                                            rebootCommand: 'systemctl reboot',  // Optional, See "Using Custom Commands" below
                                            },

            }
            },

{"success":false,"message":"Module alert does not have any actions defined."}

http://magicmirrorip:8080/api/module/alert/showalert?message=Hello&timer=2000&apiKey=********-****-****-****-**********

TypeError: Cannot read properties of undefined (reading 'showalert')
    at Class.answerModuleApi (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/API/api.js:457:35)
    at /home/bloodknot/MagicMirror/modules/MMM-Remote-Control/API/api.js:296:14
    at Layer.handleRequest (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/lib/layer.js:152:17)
    at next (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/lib/route.js:157:13)
    at Route.dispatch (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/lib/route.js:117:3)
    at handle (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:435:11)
    at Layer.handleRequest (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/lib/layer.js:152:17)
    at /home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:295:15
    at param (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:600:14)
    at param (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:610:14)
    at param (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:610:14)
    at processParams (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:664:3)
    at next (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:291:5)
    at /home/bloodknot/MagicMirror/modules/MMM-Remote-Control/API/api.js:148:7
    at Layer.handleRequest (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/lib/layer.js:152:17)
    at trimPrefix (/home/bloodknot/MagicMirror/modules/MMM-Remote-Control/node_modules/router/index.js:342:13)

magicmirror2 = 192.168.4.21
http://magicmirror2:8080/remote.html#main-menu WORKS from 192.168.4.210
http://magicmirror2:8080/api/refresh Does NOT Work from 192.168.4.210

MM Config:
address: "0.0.0.0",
port: 8080
basePath: "/",
ipWhitelist:[],

module: 'MMM-Remote-Control',
config: {
	customCommand: {}
     	showModuleApiMenu: true,
     	secureEndpoints: true,
     	apiKey: '********-****-****-****-************'  
     	showQRCode: false

GET http://magicmirror2:8080/api/refresh?apiKey=********-****-****-****-************ 404 (Not Found)

What has changed? Did I miss an update? Any assistance will be great

Let me know if you want anything else? There is nothing in the “logs” now… :)

My mirror have lot’s of modules many are multi instances (like MMM-MotionEye in this example).
I see the same behavior (or similar) with other modules, mainly my “MMM-homeassistant-sensors”…
I often makes API-calls from Node Red in Home Assistant, like this clip: https://photos.app.goo.gl/K9ktuXGKawoyHEez5

Errors from the log:

0|mmdev  | [2026-01-05 12:24:13.812] [ERROR] undefined Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
0|mmdev  |     at ServerResponse.setHeader (node:_http_outgoing:700:11)
0|mmdev  |     at ServerResponse.header (/var/www/html/magicmirror/m/node_modules/express/lib/response.js:686:10)
0|mmdev  |     at ServerResponse.json (/var/www/html/magicmirror/m/node_modules/express/lib/response.js:249:10)
0|mmdev  |     at Class.sendResponse (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:687:28)
0|mmdev  |     at Class.handleSimpleSocketNotification (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:965:10)
0|mmdev  |     at SHOW (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:1024:28)
0|mmdev  |     at Class.executeQuery (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:1049:7)
0|mmdev  |     at Class.answerModuleApi (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/API/api.js:442:14)
0|mmdev  |     at /var/www/html/magicmirror/m/modules/MMM-Remote-Control/API/api.js:299:14
0|mmdev  |     at Layer.handleRequest (/var/www/html/magicmirror/m/node_modules/router/lib/layer.js:152:17)
0|mmdev  |     at next (/var/www/html/magicmirror/m/node_modules/router/lib/route.js:157:13)
0|mmdev  |     at Route.dispatch (/var/www/html/magicmirror/m/node_modules/router/lib/route.js:117:3)
0|mmdev  |     at handle (/var/www/html/magicmirror/m/node_modules/router/index.js:435:11)
0|mmdev  |     at Layer.handleRequest (/var/www/html/magicmirror/m/node_modules/router/lib/layer.js:152:17)
0|mmdev  |     at /var/www/html/magicmirror/m/node_modules/router/index.js:295:15
0|mmdev  |     at param (/var/www/html/magicmirror/m/node_modules/router/index.js:600:14)
0|mmdev  | [2026-01-05 12:24:28.662] [ERROR] undefined Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
0|mmdev  |     at ServerResponse.setHeader (node:_http_outgoing:700:11)
0|mmdev  |     at ServerResponse.header (/var/www/html/magicmirror/m/node_modules/express/lib/response.js:686:10)
0|mmdev  |     at ServerResponse.send (/var/www/html/magicmirror/m/node_modules/express/lib/response.js:163:12)
0|mmdev  |     at ServerResponse.json (/var/www/html/magicmirror/m/node_modules/express/lib/response.js:252:15)
0|mmdev  |     at Class.sendResponse (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:687:28)
0|mmdev  |     at Class.handleSimpleSocketNotification (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:965:10)
0|mmdev  |     at HIDE (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:1023:28)
0|mmdev  |     at Class.executeQuery (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/node_helper.js:1049:7)
0|mmdev  |     at Class.answerModuleApi (/var/www/html/magicmirror/m/modules/MMM-Remote-Control/API/api.js:442:14)
0|mmdev  |     at /var/www/html/magicmirror/m/modules/MMM-Remote-Control/API/api.js:299:14
0|mmdev  |     at Layer.handleRequest (/var/www/html/magicmirror/m/node_modules/router/lib/layer.js:152:17)
0|mmdev  |     at next (/var/www/html/magicmirror/m/node_modules/router/lib/route.js:157:13)
0|mmdev  |     at Route.dispatch (/var/www/html/magicmirror/m/node_modules/router/lib/route.js:117:3)
0|mmdev  |     at handle (/var/www/html/magicmirror/m/node_modules/router/index.js:435:11)
0|mmdev  |     at Layer.handleRequest (/var/www/html/magicmirror/m/node_modules/router/lib/layer.js:152:17)
0|mmdev  |     at /var/www/html/magicmirror/m/node_modules/router/index.js:295:15

I also experience that when calling a specific module to show with “module_number_modulename”, it often shows the “wrong” module-instance (of that type of module, like MMM-homeassistant-sensors, but the wrong one)… I don’t know if it’s related to this.

Let me know if you need anything more…
Thank you for this great module! :)

Ok, I renamed MMM-Remote-Contol directory and re-installed following the github instructions. All is working now!
Thank you for your help and a great module!