[MMM-Remote-Control] Cannot GET /remote.html

mvrlogins

@sdetweil

Interesting

I’ve had that on an instance of MM I’ve been running for 5-6 years with Remote -Control and it’s always worked fine.

I’ve been able to access the display and remote from anywhere on the network.

So I just copied it over to the new one

mvrlogins

@sdetweil

I’ve now changed it to

var config = 
{
  address: '0.0.0.0',
  ipWhitelist: [],
  modules: [




    {
      module: 'MMM-Remote-Control',
      config: {
        secureEndpoints: false
      }
    },

Same problem with Canot GET /remote.html

http://10.0.1.87:8080/ works fine and I see the MM display
http://10.0.1.87:8080/remote.html leads to the error

mvrlogins

I removed the Remote-Control installation using

rm -r -f  MMM-Remote-Control/

Installed it using the instructions on the github repository

cd ~/MagicMirror/modules
git clone https://github.com/Jopyth/MMM-Remote-Control
cd MMM-Remote-Control
npm ci --omit=dev

I now get the following - which doesn’t seem fatal at first glance -

npm warn ERESOLVE overriding peer dependency
npm warn While resolving: react-inspector@6.0.2
npm warn Found: react@19.1.1
npm warn node_modules/swagger-ui/node_modules/react
npm warn   react@">=16.8.0 <20" from swagger-ui@5.29.0
npm warn   node_modules/swagger-ui
npm warn     swagger-ui@"^5.29.0" from the root project
npm warn   2 more (react-dom, react-immutable-pure-component)
npm warn
npm warn Could not resolve dependency:
npm warn peer react@"^16.8.4 || ^17.0.0 || ^18.0.0" from react-inspector@6.0.2
npm warn node_modules/swagger-ui/node_modules/react-inspector
npm warn   react-inspector@"^6.0.1" from swagger-ui@5.29.0
npm warn   node_modules/swagger-ui
npm warn
npm warn Conflicting peer dependency: react@18.3.1
npm warn node_modules/react
npm warn   peer react@"^16.8.4 || ^17.0.0 || ^18.0.0" from react-inspector@6.0.2
npm warn   node_modules/swagger-ui/node_modules/react-inspector
npm warn     react-inspector@"^6.0.1" from swagger-ui@5.29.0
npm warn     node_modules/swagger-ui

sdetweil

@mvrlogins do

npm install

Instead of

npm ci

Will ONLY do exactly watch matches package-lock.json which is rarely correct

mvrlogins

@sdetweil

Redid the install using

npm install

No errors during install

Same problem

mvrlogins

Below from the pm2 log

0|MagicMir | [2025-09-21 16:44:59.284] [ERROR] Error when loading MMM-Remote-Control: require() of ES Module /home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/uuid/dist-node/index.js from /home/pi/MagicMirror/modules/MMM-Remote-Control/API/api.js not supported.
0|MagicMir | Instead change the require of index.js in /home/pi/MagicMirror/modules/MMM-Remote-Control/API/api.js to a dynamic import() which is available in all CommonJS modules.

See https://stackoverflow.com/questions/70541068/instead-change-the-require-of-index-js-to-a-dynamic-import-which-is-available

sdetweil

@mvrlogins yes, someone will have to update the module or downgrade the dependency in package.json

KristjanESPERANTO

@mvrlogins said in [MMM-Remote-Control] Cannot GET /remote.html:

0|MagicMir | [2025-09-21 16:44:59.284] [ERROR] Error when loading MMM-Remote-Control: require() of ES Module /home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/uuid/dist-node/index.js from /home/pi/MagicMirror/modules/MMM-Remote-Control/API/api.js not supported.

To make it clear here as well: “require() of ES Module ... not supported” shows that you are using a very old (unsupported) Node version. Like I said in the GitHub issue, you have to update Node.

I recommend using NVM to update Node (like recommended on the Node website).

kasperb

@KristjanESPERANTO said in [MMM-Remote-Control] Cannot GET /remote.html:

the Node website

Experiencing the same issue… Created a clean install of MM over the weekend and am getting the same error. NVM is updated. :-(

sdetweil

@kasperb in config.js

address:”0.0.0.0”,
ipWhitelist:[],

kasperb

@sdetweil Yup, that’s what I have - sample of config here:

let config = {
	address: "0.0.0.0",	// Address to listen on, can be:
							// - "localhost", "127.0.0.1", "::1" to listen on loopback interface
							// - another specific IPv4/6 to listen on a specific interface
							// - "0.0.0.0", "::" to listen on any interface
							// Default, when address config is left out or empty, is "localhost"
	port: 8080,
	basePath: "/",	// The URL path where MagicMirror² is hosted. If you are using a Reverse proxy
									// you must set the sub path here. basePath must end with a /
	ipWhitelist: [],	// Set [] to allow all IP addresses
									// or add a specific IPv4 of 192.168.1.5 :
									// ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.1.5"],
									// or IPv4 range of 192.168.3.0 --> 192.168.3.15 use CIDR format :
									// ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.3.0/28"],

Ypsimm

@kasperb

In case you’re still interested…

After fighting with this for I don’t know how long, for poops and giggles I changed the permissions on my modules/MMM-Remote-Control folder to full r/w for all users…

Now I can access the remote control.

YMMV, change permissions at your own risk, etc.

sdetweil

@Ypsimm interesting. Git clone should set the permissions that way.

Did you install the module some other way than git?

Ypsimm

@sdetweil Originally? Quite possibly something other than git, but it’s been such a long time since I first installed that I couldn’t tell you for sure.

Most recently, yes, git clone was one of the methods I tried after completely removing the module and attempting reinstalls. Not sure if the module install doesn’t do it like the full application clone would or what, but it’s been running just dandy since the manual change. I’m curious to see if anything changes after the next update or three.

sdetweil

@Ypsimm ok, please make sure NOT to use sudo with any MagicMirror commands