-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CORS problems... #17
Comments
Yes. Here same problem with 2.18 too! |
Ok, this sorta works... it fixed something i've been swearing at for two days. Now |
Addendum: It works when sending the command from terminal, not from MMM-Remote. So again, the dilemma seems to be |
So has anyone found a work-around for this yet? I have been playing with the I don't know why this needs to be such a pain, I am running Motion/MotionEye on the same Rpi as my Magic Mirror. They just can't seem to speak to each other. |
Have exactly the same problem ... any solutions until now? |
Hello @StefanTR96 ! I didn’t find a working solution to this, but i did find a work-around. I ended up installing MMM-WebView on the mirror, pointing it to an RTSP feed from my Home Assistant. That seems to do the trick for me. I have some Home Assistant automations that hide/show the module via some command line prompts. |
For me...its working now. 192.168.178.80 = IP of my MagicMirror [Adress ](address: '0.0.0.0) is uncommented so this line is not needed anymore |
Hi there! Been using your module for years now. :)
However, now it's not working anymore, the picture from the cameras does not show (it shows a broken picture icon only).
It has to do with the "CORES" security rule in Electron (now activated).
Access to fetch at 'http://10.0.0.112:8080/motioneye/show/2' from origin 'http://0.0.0.0:8080' has been blocked by CORS policy: The request client is not a secure context and the resource is in more-private address space
private.
I'm not sure how to fix this... :)
The text was updated successfully, but these errors were encountered: