CORS, MotionEye & MMM-Remote-Control

[SdeGeata]

So this is not so much of a bug as a conflict within the system. It seems that since verson 2.17, CORS is preventing MMM-MotionEye from loading an image. I just get a broken image icon. If I change address: "0.0.0.0", to address: "localhost",, I get an image, but can no-longer run it from the web interface or command line. Further, MMM-Remote-Control requires address: "0.0.0.0", be set in config.js.

I have messed with all kinds of ip whitelist stuff to no avail, as well as played with all kinds of options in motion.conf and motioneye.conf. Nothing seems to work.

Does anyone here have a solution or work-around? I can’t get any answer back on the MotionEye Git Hub.

Any help would be greatly appreciated! I need this module to work!

[sdetweil]

@SdeGeata try the real ip address of the pi in the address:“???”

192.168.??.??

this I consider to be a NETWORKING error…

if I am listening on all interfaces, (0,0,0,0) and I send a request out… it should USE one of them
not send 0.0.0.0 to the remote site…

[SdeGeata]

@sdetweil Hello Sam;

In playing with the address, I have discovered that MotionEye does seem to display an image using address: "192.168.1.200", (the direct URL of the Magic Mirror, and running MotionEye). However, Motion Webhooks show the image then won’t hide anymore. They just stay onscreen.

Currently, I have my config set as so:

address: "0.0.0.0",

…

ipWhitelist: ["::1", "::ffff:192.168.1.200", "::ffff:192.168.1.1/120", "127.0.0.1", "::ffff:127.0.0.1", "::ffff:192.168.1.42", "::ffff:192.168.1.23", "::ffff:192.168.1.69", "::ffff:192.168.1.100"],

trying to cover all bases here. The Mirror still shows a broken image icon, but if I log into the web portal of the mirror, that show’s the camera feed no problem. How can I fix this??>

[SdeGeata]

I did notice that MotionEye and the Mirror are both listening on “0.0.0.0”. Is that normal? Could that be my conflict? Can i set MotionEye to listen on another ip, if so, which one???

[sdetweil]

@SdeGeata turn off the ipWhitelist til you get it all working. then play with the filter

[sdetweil]

@SdeGeata the cors check is at the server.

they check the IP address/name of the client making the request.

localhost is inside the same system
192.168 or 10. or 172. are non routablebip addresses, so sekfvcontainedvsyatens like localhost

0.0.0.0 is undetermined… and is mostly rejected .

as I said, it’s not a valid IP address, so it should never be sent to the other side as part of the request

[SdeGeata]

@sdetweil

I turned off the ipWhitelist, I was unable to connect MMM-Remote-Control or send any command line to the MM.

[SdeGeata]

@sdetweil said in CORS, MotionEye & MMM-Remote-Control:

they check the IP address/name of the client making the request.
localhost is inside the same system
192.168 or 10. or 172. are non routablebip addresses, so sekfvcontainedvsyatens like localhost
0.0.0.0 is undetermined… and is mostly rejected .
as I said, it’s not a valid IP address, so it should never be sent to the other side as part of the request

Its funny though, it is only since MM v.2.17 I have been having issues with MMM_MotionEye and the address: "0.0.0.0" issue. It was fine before. I don’t know what changed other than CORS.

[sdetweil]

@SdeGeata we updated libraries we use, so it could be anywhere.

[SdeGeata]

@sdetweil So what would you suggest? Is there another address I can have MotionEye listen on while leaving the Magic Mirror address on 0.0.0.0? I see an option to configure that in MotionEye.conf. I just don’t know what to set it to.