As of Chromium 111 – which is the engine behind many modern web browsers like Chrome, Edge, Opera, and more – a bug seems to have been introduced which breaks the ‘Allow Insecure’ option which is used for allowing mixed content when used with a local IP address for your media.
We’ve put together a Domain → IP resolver that can help with this in many cases. You can append.st-ip.netto the IP address to get a valid domain.http://192.168.1.10.st-ip.net:8083/your/camera.jpgThere are also several other similar services available on the web if you prefer one of those (eg. nip.io, sslip.io, traefik.me). They use the same approach where you add the service domain, such as
nip.io, between the IP address and the port in your media URL.The only data sent to
st-ip.netornip.iois the host name (eg.192.168.1.10.nip.io) for it to resolve the IP address. See the below reply for an explanation of how it works.
Some users have chosen to download an older version of their preferred browser, from before this bug was introduced, and disable auto updates so they can continue to use their image feeds.For example, one user has documented how they downloaded an older version of Opera and disabled auto updates.
Please note that this Chromium bug also affects modern Android devices. Community members have suggested that the same general approach of rolling back to an older version works.Uninstall the System WebView in the Google Play store so it rolls back to an old version. You can stick with that or download version 110 from a site like APK Mirror. --Austin
I’ve also posted a reply in the Issue Tracker from the Chromium with a sample reproduction, so hopefully the Chromium team will pick it up from there.