Hi there
previosly has worked since the earliest version from web. Now I do not know what am I doing wrong?
here is the address which can be access from any browser so you can check it
http://gyrmaq.mooo.com:51276/videostream.cgi?user=admin&pwd=dtr4guil&resolution=32&rate=0
best regards
@odranreb I need more information to help you.
What do you see in the iframe?
Also, can you open the Javascript console (ctrl + shift + j on Chrome, ctrl + shift + k on Firefox) and tell me if you see any red error messages?
Usually this is caused by bad CSP settings on the remote server, but I don’t have enough information to know for sure.
@odranreb I tried to put your URL into an IFrame inside of a CodePen and it also fails, which leads me to believe the problem is the server at mooo.com and not the Web App.
My guess is that a recent browser update is not allowing you to display non-HTTPS content in an HTTPS context (The Web App has mandatory HTTPS).
yes my web can is not https is only http
this is how it looks like in a separate tab
gyrmaq.moo.com is only my ddns i could use only 192.168.35.144 instead from outside my LAN
accually
http://192.168.35.144:51276/videostream.cgi?user=admin&pwd=dtr4guil&resolution=32&rate=0
also works on a separate Chrome Tab
@odranreb Opening a page in a tab is not the same thing as opening a page in an iFrame. Browsers follow a number of security policies for handling iframes which do not apply to tabs. I understand your reason for using a dynamic DNS, and it does not contribute to the problem.
The error message on Firefox is a bit easier to understand:
You can read about Chrome’s decision to block all mixed content (Oct 3 2019) here.
You can read about Firefox’s mixed content blocking (and why browsers do it) here.
This is a problem with your browser / web cam. Your best option would be to upgrade to HTTPS, purchase a camera that hosts HTTPS streams or find a way to proxy traffic over an HTTPS endpoint.
I understand perfectly
yes, my camera is a bit old. let me try to find a way do upgrade it.
thank you for your help
If I get it right, it doesn’t depend on your camera. It’s just the DynDNS service which has to offer https:// instead of http:// That should fix it.
