I misunderstood the nip.io workaround and thought it involved adding things or creating an account of some sort. So tried the much more efficient way, but that bothered me you can’t make it full screen. I really liked you could see all camera’s in 1 tile, but tapping a screen didn’t make it large enough.
So then I looked at the nip.io again and that was easy, just add it to the IP and done
At least now my tablet can simply update instead of running an old webcore. That’s how I used to do it, but suddenly my tablet decided to update anyway and broke it again.
Still having the issue - mixed content set to always allow on fully and origin ip added to chrome flag. Video loads in browser and media resources but not fully kiosk. Nip.io didnt work (broke preview in media resources). Anything else I can do on Fire tablets?
Fully kiosk must have just recently updated to chrome 111. If anyone has a link to an older full kiosk I’ll take it but for now, Thanks! npi.io solved my pic from my camera streams but to access my camera streams in the ip address I have my user and password for the camera, how secure is nip.io? as secure as sharptools or actiontiles I suppose
ugh, am i gonna have to install the play store on my fire tablets? or can i sideload apks an easier way? this is becoming a hassle for one video feed on my home dashboard…
Why do you need to sideload an APK? You should be able to view media tiles even with the Chromium 111 update, but you would need the mixed content and nip.io approach. You mentioned that things weren’t working in Fully Kiosk with nip.io, but it wasn’t clear what you had tried as that should work.
Maybe you could share some screenshots of:
The working media URL in a regular browser (with the URL visible)
The configured media URL in Fully Kiosk using the nip.io format not working in the preview in Manage Media
the only thing i havent tried is the aforementioned old apks for fully or browsers. for nip.io, the new address just didnt do anything and using that actually broke the preview within sharptools when editing the resource. i dont have access to it now, but ill post screenshots.
The only thing that passes through nip.io is the DNS request for the subdomain. The rest of the URL does not get sent to nip.io.
In other words, your browser only sends the domain name 192.168.1.50.nip.io to nip.io and nip.io responds that it’s available at the IP address 192.168.1.50. From that point forward, anything else in the URL or the request gets sent directly to the IP address (eg. your camera).
The flow looks something like the following:
Your browser gets a request for http://192.168.1.50.nip.io/mycontent
Your browser sees that the request is a subdomain of nip.io, so it asks nip.io where it can find the subdomain 192.168.1.50.nip.io
nip.io replies that the subdomain is available at the IP address 192.168.1.50
Your browser then makes the http request to the provided IP address along with the rest of the URL (eg. at this point, the full path of the URL gets sent to the IP address).
Your IP camera is at the IP address, so it sees the http request (along with the full URL at this point), and is able to respond with the requested resource
Here’s a visual version of the above that I quickly put together:
(tap the right or left side to move through the slides)
DNS by Joshua Lyon
Images (tap to expand if the embed above doesn't work)
I’m on a Kindle with FK, and it does not seem to work, it does work in Chrome though. I assume that is has to do with the SSL/Mixed, even when I change the settings.
Could be… hard to tell without more details. Fully Kiosk uses the ‘webview’ bundled with the system. So if that webview is running version 85 or newer, it would be impacted by the mixed content issue (HTTP image on HTTPS page)… or if it’s running 111 or newer, it would be impacted by the local IP limitation.
Both are discussed in detail in the posts above including workarounds for both.
wanted to update; everything all of a sudden started working, including using nip.io. i didn’t touch it or change anything, and one day it started showing up. i assume something was updated on the browser side.
That’s close. If your original URL doesn’t have a port, then you don’t need to include a port in the wildcard DNS version either.
In your original sample URL, the port was not included and since it was an HTTP request, it would be implied to be port 80. In your sample nip.io converted URL, you had appended a port of :88. Also note that your sample nip.io URL had some weirdness where that path seemed to have extra stuff added like /cgi-bin twice and 92.168.1.xx included in the path as well.
I also suspect that the st_uuid came from the SharpTools autorefresh, so I dropped that, but if that’s something else, you could of course add it back in if needed.
So reading between the lines from your example, that would become something like the following, assuming your sample nip.io URL was the actual local IP and the port wasn’t on the original URL:
Thanks a lot!
Took me a couple of days to figure it out
The links work fine on media on my PC with chrome browser.
However it doesn’t work on my android phone, nor on my android tablet which are in the same house /wifi AP “failed to load image”
You may need to disable Mixed Content blocking on those browsers as well as noted in the first post of the thread.
As a first step in trouleshooting, I would also double check that those devices are able to view the media URL you are using directly in the browser – directly in the URL bar of the browser rather than embedded within a Media Item – that helps verify that they can resolve the URL as expected and communicate directly with the camera.
