• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
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.

Access MagicMirror with HTTP?

Scheduled Pinned Locked Moved Troubleshooting
14 Posts 4 Posters 14.9k Views 4 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.
  • P Offline
    psteimann @shashank
    last edited by Sep 2, 2017, 9:18 PM

    @shashank

    I started MM2 with the console now:-) Thanks Mikle1.

    It works in the local network now as I wrote in the posting above. But I get an issue-report. Is this important?

    Whoops! There was an uncaught exception…
    { Error: listen EADDRINUSE :::8088
    at Object.exports._errnoException (util.js:1050:11)
    at exports._exceptionWithHostPort (util.js:1073:20)
    at Server.setupListenHandle [as _listen2] (net.js:1263:14)
    at listenInCluster (net.js:1304:12)
    at Server.listen (net.js:1402:7)
    at new Server (/home/pi/MagicMirror/js/server.js:26:9)
    at /home/pi/MagicMirror/js/app.js:219:18
    at loadNextModule (/home/pi/MagicMirror/js/app.js:168:5)
    at /home/pi/MagicMirror/js/app.js:163:6
    at Class.loaded (/home/pi/MagicMirror/modules/node_modules/node_helper/index.js:19:3)
    code: ‘EADDRINUSE’,
    errno: ‘EADDRINUSE’,
    syscall: ‘listen’,
    address: ‘::’,
    port: 8088 }
    MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
    If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
    Launching application.

    Greez Peter

    ? 1 Reply Last reply Sep 2, 2017, 9:24 PM Reply Quote 0
    • ? Offline
      A Former User @psteimann
      last edited by A Former User Sep 2, 2017, 9:35 PM Sep 2, 2017, 9:24 PM

      @psteimann you are already using port 8088, is there any program which is using that port? Or you executed mm twice at same time. Common pitfall is not killing pm2 and starting another npm (or node serveronly) for test…

      P 1 Reply Last reply Sep 2, 2017, 9:32 PM Reply Quote 0
      • P Offline
        psteimann @Guest
        last edited by Sep 2, 2017, 9:32 PM

        @Sean Port 8088 is not used by another program and there Is no other port-forwarding to this port.

        8080 is used by my NAS, so I changed the standard-port to 8088 in the config.js

        i start mm2 automatically with pm2, thats correct. but I do not start it twice.

        do you mean to try to start another instance of mm2 with npm start?

        Thanks!

        ? 1 Reply Last reply Sep 2, 2017, 9:33 PM Reply Quote 0
        • ? Offline
          A Former User @psteimann
          last edited by A Former User Sep 2, 2017, 9:34 PM Sep 2, 2017, 9:33 PM

          @psteimann sorry for my poor English. You SHOUD NOT execute twice, before killing pm2.

          P 1 Reply Last reply Sep 2, 2017, 9:39 PM Reply Quote 0
          • P Offline
            psteimann @Guest
            last edited by Sep 2, 2017, 9:39 PM

            @Sean So you mean I shall kill pm2 and start with npm?

            how do I kill the pm2-process? If I try to close the pm2-window, it starts again immediately… in the console I guess, but whats the syntax?

            ? 1 Reply Last reply Sep 2, 2017, 9:42 PM Reply Quote 0
            • ? Offline
              A Former User @psteimann
              last edited by Sep 2, 2017, 9:42 PM

              @psteimann pm2 stop mm

              P 1 Reply Last reply Sep 3, 2017, 3:58 PM Reply Quote 0
              • P Offline
                psteimann
                last edited by Sep 2, 2017, 9:49 PM

                Ok, that worked so far. stopped mm2 and startet it manually with npm in the console.

                Errors have gone, great. So is it an issue with pm2?

                Unfortunately, still no access from outside.

                link:
                timesoft.internet-box.ch:8088

                1 Reply Last reply Reply Quote 0
                • P Offline
                  psteimann @Guest
                  last edited by Sep 3, 2017, 3:58 PM

                  @Sean

                  OK. it works now

                  I entered a second whitelist entry for the external ip:

                  ip is currently:
                  178.198.19.38

                  so i added ffff:178.198.19.1/24…

                  thanks for help

                  1 Reply Last reply Reply Quote 0
                  • 1
                  • 2
                  • 2 / 2
                  2 / 2
                  • First post
                    11/14
                    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