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.

    EADDRINUSE port error

    Scheduled Pinned Locked Moved Troubleshooting
    5 Posts 2 Posters 2.3k 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.
    • S Offline
      screechyboy79
      last edited by

      Hi,

      Everytime my PI boots and it tries to start Magic Mirror V2.1.3 I get an error which google tells me is becuase the Port specified is in use. I changed this to port 8099 which was not in use and I get the same error. When i check to see what is using that port its Node.js.

      Any suggestions?

      Steve

      1 Reply Last reply Reply Quote 0
      • S Offline
        screechyboy79
        last edited by

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • S Offline
          screechyboy79
          last edited by

          The error:
          – Ready to go! Please point your browser to: http://localhost:8099
          Whoops! There was an uncaught exception…
          { Error: listen EADDRINUSE 127.0.0.1:8099
          at Object._errnoException (util.js:1019:11)
          at _exceptionWithHostPort (util.js:1041:20)
          at Server.setupListenHandle [as _listen2] (net.js:1344:14)
          at listenInCluster (net.js:1385:12)
          at GetAddrInfoReqWrap.doListen [as callback] (net.js:1494:7)
          at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:100:10)
          code: ‘EADDRINUSE’,
          errno: ‘EADDRINUSE’,
          syscall: ‘listen’,
          address: ‘127.0.0.1’,
          port: 8099 }
          MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?

          ? 1 Reply Last reply Reply Quote 0
          • ? Offline
            A Former User @screechyboy79
            last edited by

            @screechyboy79 That is well-known bug. Sometimes, MM couldn’t be killed CLEARLY. In that case, just restart pm2 or npm.
            Maybe at the next time, This error might appear again. However currently there is no perfect solution found.

            S 1 Reply Last reply Reply Quote 0
            • S Offline
              screechyboy79 @Guest
              last edited by

              @Sean I’ve rebooted several times i have also as you suggested tried pm2/npm restarts which also doesnt have any effect. This isnt intermittent its every time I reboot

              1 Reply Last reply Reply Quote 0
              • 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