josh
June 15, 2023, 5:05pm
4
Check the article I linked above. Chromium based browsers introduce a bug in version 111 that causes the ‘Allow Insecure’ flag to not work. You can work around it by using a
Just wanted to add an update to the Chromium 111 issue noted above. I found a thread on Reddit talking about how the Chromium update broke some of their enterprise apps and they realized that it only broke HTTP images served from an IP address but did not break HTTP images served from a domain.
While I’m not explicitly recommending this, one workaround might be to use one of the many sites that automatically map a specially formatted domain into a local IP (eg. nip.io , sslip.io , traefik.me )
http://192-168-1-10.nip.io/your/camera.jpg
In your case, give the following a try…
http://192.168.68.55.nip.io:8123/dashboard-vacuuming/0?kiosk