Read the statement by Michael Teeuw here.
Error code EADDRINUSE
-
Will this work with Git Bash? This is what I’m using.
-
Tried it twice got this
npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! magicmirror@2.8.0 start: `sh run-start.sh` npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the magicmirror@2.8.0 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\user1\AppData\Roaming\npm-cache\_logs\2019-07-30T19_47_00_790Z-debug.log -
Starts fine without the &
-
@PXNDA no idea
-
I think the sh script may have become corrupt. Thank you anyway @sdetweil for sticking up to the mess I made of MM.
-
@PXNDA well, if u found it thats all that matters
-
I’ve tracked the problem to the address. I’ve changed it from localhost to 0.0.0.0. Any ideas why.
-
Ok, I’ve figured that Electron only accepts https certified addresses so how can i fix that.
-
@PXNDA electron does not do https unless u do a lot of extra work
-
I mean that Electron won’t accept 0.0.0.0
-
It works fine with localhost.
-
I’m trying to use MMM-Remote-Control.
-
@PXNDA that just says listen anywhere (all adapters)
localhost means ONLY localhost, ONLY from THAT machine to THAT machine
external machines should not be able to connectwith 0.0.0.0 you also need to open the whitelist (allowed sources) , by default NO other ip address (localhost only still)…
RemoteControl ois listening on the MM ip address (using the express server and routes/(paths in the url)
so if ONLY localhost then cannot connect from outside the pi)… makes ;remote ’ control pretty hard… -
I’ve also done that, no change.
-
@PXNDA is this windows? Open the firewall on 8080
-
This post is deleted! -
@PXNDA It was suggested with the v2.8 update that anybody running Electron should update to the latest Raspbian version prior to upgrading to v2.8. Have you updated your Raspbian to the latest version?
-
I’ve opened a new rule on firewall for port 8080 @sdetweil and there is no change. @mumblebaj I’m using Windows 10.
-
@PXNDA ok, change the config.js port to something else, 8090 for example
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login