MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

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

    Scheduled Pinned Locked Moved Unsolved Troubleshooting
    10 Posts 3 Posters 360 Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M Offline
      mvrlogins @sdetweil
      last edited by

      @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

      1 Reply Last reply Reply Quote 0
      • M Offline
        mvrlogins @sdetweil
        last edited by 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

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          mvrlogins @mvrlogins
          last edited by

          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
          
          S 1 Reply Last reply Reply Quote 0
          • S Offline
            sdetweil @mvrlogins
            last edited by

            @mvrlogins do

            npm install

            Instead of

            npm ci

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

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            M 1 Reply Last reply Reply Quote 0
            • M Offline
              mvrlogins @sdetweil
              last edited by mvrlogins

              @sdetweil

              Redid the install using

              npm install
              

              No errors during install

              Same problem

              M 1 Reply Last reply Reply Quote 0
              • M Offline
                mvrlogins @mvrlogins
                last edited by 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

                S KristjanESPERANTOK 2 Replies Last reply Reply Quote 0
                • S Offline
                  sdetweil @mvrlogins
                  last edited by

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

                  Sam

                  How to add modules

                  learning how to use browser developers window for css changes

                  1 Reply Last reply Reply Quote 0
                  • KristjanESPERANTOK Offline
                    KristjanESPERANTO Module Developer @mvrlogins
                    last edited by 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).

                    1 Reply Last reply Reply Quote 1
                    • 1 / 1
                    • First post
                      Last post
                    Enjoying MagicMirror? Please consider a donation!
                    MagicMirror created by Michael Teeuw.
                    Forum managed by Sam, technical setup by Karsten.
                    This forum is using NodeBB as its core | Contributors
                    Contact | Privacy Policy