NVR sending me to loopback
Firefox browser on Fedora 42. Latest version.
Error message: "Ch1:Load Failed.Please visit https://192.168.1.220:8443 for certificate trust to view videos. Then come back here to refresh this page to view videos."
Clicking SHOULD send you to cert page to auth. Then back to NVR so you could successfully watch live view. However now it just says "unable to connect" and sends you to loopback 127.0.0.1 all the time: "Firefox can’t establish a connection to the server at 0.0.0.0."
I can view playback and camera feed via settings perfectly fine. Just not under "Live view".
What gives???
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
We’ve identified the issue—it only occurs in Firefox ; Edge and Chrome are unaffected. A fix will be included in a future firmware release; timing is not yet available, so please watch our website for updates.
- Copy Link
- Report Inappropriate Content
Thank you for your post.
Could you please tell us the exact model of your camera?
Have you tried viewing the stream in Google Chrome?
Kindly record a short screen-capture video so we can examine the issue in detail.
Also, confirm whether the problem occurs when you access the NVR’s web management page directly via its IP address.
Lastly, which device does the IP 192.168.1.220 belong to?
- Copy Link
- Report Inappropriate Content
Hello same problem here - after logging into NVR, selecting channel and clicking link for accepting cert exception I'm taken to 127.0.0.1.
Firefox 140.4.0esr
Debian 12.12
Device Model VIGI NVR1008H(UN) 2.20
Device Name VIGI NVR1008H(UN) 2.20
Total Channels 8
Firmware Version 1.4.2 Build 250918 Rel.78880n
Release Date 2025-09-18
Cameras:
1 VIGI C300HP-4 2.0 - FW 1.0.11 Build 230411 Rel.57861n
2 VIGI C540 1.0 - FW 3.0.0 Build 231229 Rel.57108n
- Copy Link
- Report Inappropriate Content
Ethan-TP wrote
Thank you for your post.
Could you please tell us the exact model of your camera?
No. The issue is with the NVR. Not the cameras.
Have you tried viewing the stream in Google Chrome?
No.
Kindly record a short screen-capture video so we can examine the issue in detail.
I have no software to do this.
Also, confirm whether the problem occurs when you access the NVR’s web management page directly via its IP address.
That's how I was accessing it. I'm not aware of how you could access it any other way.
Lastly, which device does the IP 192.168.1.220 belong to?
The NVR.
- Copy Link
- Report Inappropriate Content
It was working perfectly fine before. I'm guessing a recent update broke compatibility with Firefox. I am not switching browsers. If it doesn't work with Firefox than I'll switch to a company that does support it. I'm hearing good things about Ubiquiti.
- Copy Link
- Report Inappropriate Content
We’ve identified the issue—it only occurs in Firefox ; Edge and Chrome are unaffected. A fix will be included in a future firmware release; timing is not yet available, so please watch our website for updates.
- Copy Link
- Report Inappropriate Content
@Ethan-TP Thanks for addressing the issue with a future update. It is still unfortunate that there has been no explanation why a previous update broke something that was working perfectly fine before. So clearly your firmware was fine with the stricter security policy that Firefox enforces but for some unknown reason, you decided to release an update that broke that compatibility.
Perhaps the firmware update that you released had an unintentional affect that caused this problem. But considering the thin ice TP-Link is on with regards to potentially being banned from selling its products in countries like the US due to security concerns, I strongly recommend TP-Link make extra effort to ensure its products work and are compatible with browsers that enforce the absolute strictest of security policies.
- Copy Link
- Report Inappropriate Content
The issue stems from the fact that, after IPv6 support was added to the NVR, IPv6-format addresses are now in use. The redirect interface has not been updated to handle IPv6 addresses; it still attempts to parse them as IPv4, which fails and causes the redirect URL to become 0.0.0.0. This is neither a security nor a compatibility problem.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 236
Replies: 7
Voters 0
No one has voted for it yet.