Im having similar issue with my Hikvision cams on MS edge, I gave up on chrome for this a while ago. A week ago they worked and now they dont. I can pull the cam snapshot up in a stand alone URL, but it wont display in sharptools media tile anymore. And yes I have unsecure content enabled for these local IP addresses which was working fine for a couple years.
So after scanning these responses, what I take away is that Chrome doesnāt work anymore because it has been updated. (I am also running v111.0.5563.111)
Opera worked for a bit, but it has been updated.
Edge doesnāt work.
SSL Certificates are a pain, and not for the faint of heart.
What is it you are suggesting we do? What can we do it restore all the functionality that weāve embedded into our dashboards?
The third quote from my reply above includes another community memberās feedback on how they downloaded a version of Opera that works along with instructions on how to prevent it from auto updating.
An update to Chromium ā which powers Google Chrome, Opera, Microsoft Edge, and many other browsers ā introduced a bug that is causing the setting not to be respected. So as a workaround, you can use a browser version from before the bug was introduced to Chromium. Ideally, the Chromium team will resolve this issue so newer versions of Chromium based browsers can continue to be used as normal.
I may just be stupid. I downloaded a version from Dec 22, and then another version from Jan 2021.
Neither one fixed the problem. Neither display the webcams.
Iāve looked in the settings for Opera to see if there is a ādisplay insecureā and based on my web search, it doesnāt look like they have the setting like Chrome does.
How do I go about setting up my Foscamās with certificates if I canāt get around this browser issue? Without being able to see my webcams, Sharptools is much less valuable to me and I might just drop the whole thing.
From a quick test, it seems to be roughly the same concept as Chrome on PC. Tap the lock icon by the URL, tap Site Settings, change āInsecure Contentā to Allow.
This was on Opera 96. I didnāt try disabling the auto-updates, but Hendre linked to instructions on how to do that (the last quote from my post above).
I donāt have Foscam cameras, so I canāt speak to the details of it, but the overall concept would be to get a valid SSL certificate and install it on the camera (assuming the camera supports that). Alternatively, some people prefer to use a reverse proxy like Caddy, Apache, or Nginx as thereās a lot of articles for those particular reverse proxies describing how to set them upā¦ though it is quite a technical process.
I canāt speak to the Edge rollback process, but I suspect it would need to be less than version 111 and like most Chromium browsers, the auto update process tends to be pretty aggressive. And of course the āAllow Insecureā / Mixed Content setting would need to be enabled for it to work in Edge.
Opera is based on the Chromium project just like many other modern browsers including Chrome and Microsoft Edge. The bug seems to have been introduced in version 111 of these browsers, so some people are running older versions of their preferred browser until this is properly fixed in the Chromium project.
I suspect that some people donāt want to rollback their primary browser (Chrome/Edge) and since Opera was a bit slow to update to 111, it was an easy choice at the time for people to just install that.
Regarding the issue on the bug introduced in Chromium 111 that breaks IP Camera images over HTTP, make sure to follow the Mixed Content thread as updates are being posted there including some discoveries that this seems to impact images from IP addresses and there is a workaround with local domain names:
