Error code EADDRINUSE

[sdetweil]

@PXNDA no idea

[PXNDA]

I think the sh script may have become corrupt. Thank you anyway @sdetweil for sticking up to the mess I made of MM.

[sdetweil]

@PXNDA well, if u found it thats all that matters

[PXNDA]

I’ve tracked the problem to the address. I’ve changed it from localhost to 0.0.0.0. Any ideas why.

[PXNDA]

Ok, I’ve figured that Electron only accepts https certified addresses so how can i fix that.

[sdetweil]

@PXNDA electron does not do https unless u do a lot of extra work

[PXNDA]

I mean that Electron won’t accept 0.0.0.0

[PXNDA]

It works fine with localhost.

[PXNDA]

I’m trying to use MMM-Remote-Control.

[sdetweil]

@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 connect

with 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…

[PXNDA]

I’ve also done that, no change.

[sdetweil]

@PXNDA is this windows? Open the firewall on 8080

[PXNDA]

This post is deleted!

[mumblebaj]

@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?

[PXNDA]

I’ve opened a new rule on firewall for port 8080 @sdetweil and there is no change. @mumblebaj I’m using Windows 10.

[sdetweil]

@PXNDA ok, change the config.js port to something else, 8090 for example