Hmmm…not sure I am following. Do I have to install anything for nip.io to work? Or just adjust my address.
Eg. https://192.168.1.15:8083/axis-cgi/mjpg/video.cgi?camera=6
Do I simply switch off SSL on Tinycam, then insert:
http://192.168.1.15.nip.io:8083/axis-cgi/mjpg/video.cgi?camera=6?
Or do I have to install an open source nip.io component somewhere?
Just following up as I still can’t seem to get this to work.
Also, if I have one device not using Chromium 111, the other using it, will that cause issues using the nip.io thing or should both work fine?
I would suggest reading through some of the discussion above as there’s some good discussion about what the issue is, why nip.io solves it and how it works, and how to use it.
nip.io is just a DNS server. In other words, it just resolves the ‘domain name’ to a local IP address. Nothing needs to be installed as it’s a fundamental part of how the internet works and nip.io hosts the wildcard DNS service for free.
If you can provide more details, we might be able to help.
Yes, if that was the original camera URL, then that sounds like the right adjustments. I would start with the basics though. Make sure you have a valid URL for your camera that opens directly in your browser without any login prompts or warnings about SSL errors. (It might help to try it in an incognito window as a test).
Once you have that known working URL, you should be able to convert it to the nip.io format and open it directly in your browser.
Once that’s confirmed working, as long as you have made the adjustment to Allow Mixed Content, you should be able to use the nip.io URL that you tested directly in your browser within a Media Tile.
Okay, so the below URL properly opens in a Chrome browser and displays the feed along with the “
Not secure” message. Surprised as I didn’t think I would actually see the picture for whatever reason.
http://192.168.1.15:8083/axis-cgi/mjpg/video.cgi?camera=6
Even after I clicked “Allow insecure content”, I still have the warning message.
However, when I then insert the nip.io into the URL, I get the usual NXDomain error implying the domain doesn’t exist.
Check if there is a typo in 192.168.1.15.nip.io.
DNS_PROBE_FINISHED_NXDOMAIN
We would really need the details to be able to help. Otherwise we’re guessing at lots of details that could impact things (like what the full URL you used for testing was).
Also, is there anything special about your network configuration? Especially things around DNS resolution? I would also make sure you can visit nip.io directly in your browser without issue. And you could try using the dash format instead:
http://192-168-1-15.nip.io:8083/axis-cgi/mjpg/video.cgi?camera=6
Or one of the other providers mentioned above:
http://192-168-1-15.traefik.me:8083/axis-cgi/mjpg/video.cgi?camera=6
http://192-168-1-15.sslip.io:8083/axis-cgi/mjpg/video.cgi?camera=6
Again, the details would really help here. Especially a screenshot.
You shouldn’t have been prompted to Allow Insecure Content in Chrome if you were visiting the camera URL directly. If you did, that could be indicative of something wrong. Since you played around with the SSL settings, make sure you completely restarted TinyCam to make sure they took effect once those settings were reverted. Or try restarting your phone too.
If you are prompted in any way (in a fresh incognito tab), that’s likely going to cause an issue. For example, you shouldn’t see a login prompt and you shouldn’t have to explicitly accept insecure content.
Sorry, not sure what details I’m omitting. But…
Using TinyCam Pro with webserver enabled on a NVidia Shield, port set to 8083, 192.168.1.15 is the address of the Shield.
Have resources set up in my Sharptools.io dashboard with the URLs to various cameras (have 7 cameras on the TinyCam). For instance, http://192.168.1.15:8083/axis-cgi/mjpg/video.cgi?camera=1 is my front door camera.
The tiles work on my Amazon FireHD8 2017 tablet, but do not work on my Amazon FireHD8 2020 tablet.
I’m testing this on a laptop using Chrome.
Clicking on nip.io works fine on the desktop.
I tried all links above, get the same NXDomain error.
Nothing special that I can think of around my network/DNS setup.
No prompts for passwords etc, goes right to the image.
Something is wrong with DNS somewhere along the line if you are getting the DNS_PROBE_FINISHED_NXDOMAIN error in Chrome with all of the above examples.
The screenshot doesn’t look like an incognito window. If you were ever prompted for your credentials or accepted any prompts, the browser could be saving those. That’s why it’s important to try a fresh incognito session.
Bingo…nip.io URL embedded link works fine from my home laptop. So probably a DNS or restriction somewhere my company puts on the laptops. Now to see if it works with Fully.
@Jordan_Welker, by chance did you figure out how to get Fully to work again? I seem to be having the same issue that you are where even adding in nip.io into the address doesn’t work.
I suspect that Jordan’s issue was slightly different as they mentioned that nip.io didn’t work at all for them and they had mentioned that in the context of Chrome. Without more details, it’s unclear what their configuration was though.
I just tested on a Fire HD 8 Plus (10th gen) with the version details shown in my screenshot below and it worked for me.
Have you gone through these steps, noting the results of each, to help narrow things down?
Desktop / Laptop on Chrome (if available)
Test the camera URL directly in your browser:
http://192.168.1.15:8083/axis-cgi/mjpg/video.cgi?camera=6
Test the nip.io URL directly in your browser:
http://192.168.1.15.nip.io:8083/axis-cgi/mjpg/video.cgi?camera=6
Test the nip.io URL within a SharpTools Media Resource
(SharpTools User Page > Manage Resources > Media)
Fire Tablet (Silk Browser)
Test the camera URL directly in your Silk browser:
http://192.168.1.15:8083/axis-cgi/mjpg/video.cgi?camera=6
Test the nip.io URL directly in your Silk browser:
http://192.168.1.15.nip.io:8083/axis-cgi/mjpg/video.cgi?camera=6
Test the nip.io URL within a SharpTools Media Resource
(SharpTools User Page > Manage Resources > Media)
Fire Tablet (Fully Kiosk Browser)
Test the camera URL directly in your Fully Kiosk browser:
http://192.168.1.15:8083/axis-cgi/mjpg/video.cgi?camera=6
Test the nip.io URL directly in your Fully Kiosk browser:
http://192.168.1.15.nip.io:8083/axis-cgi/mjpg/video.cgi?camera=6
Test the nip.io URL within a SharpTools Media Resource
(SharpTools User Page > Manage Resources > Media)
Sorry just getting back to this.
Just tried it on my 2017 Fire HD8 tablet.
The nip.io link opens up fine in the Silk browser.
It won’t open in the Fully browser…
The standard camera URL works fine in the Fully browser.
Have to try it on a non work laptop as well.
Also, the nip.io link works fine on my iPhone in Safari, not in Chrome.
Tried it on a non-work laptop. Same issue, Chrome and Firefox give the “We can’t connect to the server at 192.168.1.15.nip.io.” error.
So it works on Safari and Silk, but not Fully, Chrome or Firefox. Could have sworn it worked on another one of my personal laptops but can’t recall which it was.
Unfortunately, I’m unable to help without the details.
It’s really important to include the results of each step along with the details of any error messages (screenshots preferred). And in general, it’s important to include details like version numbers, device make/model, and any other relevant details about the configuration or testing.
As a free user, we try to offer as much support as we can through our community and documentation. Providing these details will enable both us and the community to assist you more effectively.
–
I’ve tested each of these steps on a variety of new and old devices and I’m not able to reproduce the issue. The DNS_PROBE_FINISHED_NXDOMAIN issue mentioned above is clearly a DNS / networking issue. It’s not clear exactly what error messages you were seeing when things weren’t working with some of your recent tests but “We can’t connect to the server at XXX” sounds like a networking error.
That’s part of the reason I asked for result of each of the steps above: it starts with a fundamental validation of network connectivity to your camera, then tests nip.io which should only be a difference in DNS resolution, then tests it as an embedded resource which is where most browsers get the most finicky.
Okay. First series of pictures is all on Silk Browser.
Top right on dashboard is driveway stream. Rest are all not on nip.io. In Silks case using the sharp tools dashboard it does not show either nip.io or direct URLs.
Next is Fully. Again, Top right on dashboard is driveway stream. Rest are all not on nip.io.
Versions of Tablet and OS.
Just curious, but if Silk works for nip.io but Fully won’t on the same tablet, doesn’t that rule out a DNS issue?
Unless each browser allows you to change DNS settings which I don’t believe is the case?
@josh Just getting back to this. Did I provide everything you needed above? I don’t think it’s a DNS issue since some browsers in the same device work while others don’t, which unless there are specific DNS resolution options within each browser (and I don’t think there is), implies it’s not DNS?
I didn’t see which WebView version is being used. 
The error message ERR_NAME_NOT_RESOLVED reads as a DNS resolution issue. That doesn’t necessarily mean it’s an issue with your internet, but it points to a DNS resolution issue in that screenshot.
Understanding what WebView version you are on and ideally updating it to as new of a version as you can would be ideal here.
I would also be curious about these results.
