Closed IronOxidizer closed 2 months ago
I see a similar error at https://github.com/scottlamb/moonfire-nvr/issues/277#issuecomment-1627480506 but haven't managed to figure out the fix.
But question here:
This only happens on Firefox when I'm outside of my local network. While inside the network, or when using a chromium based browser, the live view works as intended.
How does your outside-the-network setup work? You have two different domain names as in that error message (https://nvr4.us.to/
vs https://mydomain.com/
)?
Also, am I correctly inferring from this comment that it worked in v0.7.5? There have been a lot of server-side changes since then but really not much on the frontend side. The biggest thing was upgrading to React v18 but I don't see anything relevant in the release notes.
https://mydomain.com/
was just an example as to not leak my actual domain, but I guess I forgot anyways 😅. My in-the-network setup involves me connecting directly to the host via http://192.168.1.123:8080
.
Also, am I correctly inferring from https://github.com/scottlamb/moonfire-nvr/issues/285#issuecomment-1627452748 that it worked in v0.7.5?
Last working version of live-view for me was v0.7.2.
v0.7.3 introduced https://github.com/scottlamb/moonfire-nvr/issues/219 which broke live view, and wasn't fixed until v0.7.6 because of https://github.com/scottlamb/moonfire-nvr/issues/230. It's possible that this is new behavior that was introduced into Firefox in 15 months since v0.7.2
Some more data points:
Hmm. Skimmed Firefox release notes. Didn't notice anything relevant. I'm kind of stuck. :-(
This seems like a Firefox bug based on:
There's also dozens of mentions of it on Github, with no root-cause: https://github.com/search?q=%22may+not+load+data+from+blob%22&type=issues
Though it's weird that this hasn't been an issue till now. @scottlamb Are you able to reproduce it on Firefox?
Yes, I am able to reproduce. I also found some similar error messages on the web, but I'm not sure how relevant those things are, e.g. the first two you linked:
At first I thought this was related to Content-Security-Policy
but messing with that didn't help anything.
I might try firing up v0.7.2 with current Firefox and see if it's affected, and/or find some old Firefox versions to bisect.
Okay, here's something:
I guess I'll do a git bisect
to narrow down what changed.
Hmm, looks like it broke with 098b54c. Not sure why...
...and specifically, updating to React 18 alone doesn't break it, but doing the recommended switch from ReactDOM.render
to createRoot
does. Not seeing anything in their docs that looks relevant though.
I finally distilled this down to a relatively minimal reproducible example and asked for help on stackoverflow. Fingers crossed someone will help me understand what's going on, and I can get it fixed.
I just upgraded today, Oct 14, 2023, and encountered the same problem with Firefox 115.3.1esr (64-bit). However, if I use Chrome Version 109.0.5414.120 (Official Build) (64-bit), I am able to view live "sub" feeds in the Live Views. I loaded up the screen using the 3x3 and successfully displayed 9 cameras in Chrome.
Describe the bug When attempting to use the live view, I get a black screen and the browser shows the error:
Security Error: Content at https://mydomain.com/ may not load data from blob:https://mydomain.com/44abc5dc-750d-48d1-817d-2e6a52445592.
This only happens on Firefox when I'm outside of my local network. While inside the network, or when using a chromium based browser, the live view works as intended.
To Reproduce Steps to reproduce the behavior:
https://mydomain.com
orhttps://123.456.789.10
Expected behavior Live view appears
Server (please complete the following information):
scottlamb/moonfire-nvr:v0.7.6
Desktop (please complete the following information):
Additional context I understand this is probably not a moonfire issue, but is there a workaround that can be implemented in moonfire? Based on some quick research, the trigger might be paramaterized blobs, still not sure though.