NVR DS-7608NXI-I2/8P/S Model Identification, EOL Status, Firmware Updates, and HTTPS Configuration?

[Sunchaser]

I'm seeking insights on a few matters regarding my Hikvision NVR (DS-7608NXI-I2/8P/S) and its connected cameras:

1. Model Confusion and Firmware Update: I have the Hikvision NVR model DS-7608NXI-I2/8P/S. I originally believed it to be the latest (E) model, but after a firmware update mismatch issue, I successfully installed the firmware for the (C) variant, specifically version Firmware_V4.62.210_230619. Does this successful update indicate that I indeed have the (C) model? I'm a bit puzzled about how to definitively ascertain the model version.

2. Concerns About End-of-Life Status: I've come across information suggesting that my NVR model is now end-of-life (EOL), which is disconcerting given its recent installation. The implications for security and firmware updates are quite worrying. How can I verify when the (C) version was declared EOL? If anyone has insights on the notification process regarding EOL status, especially in relation to installers, it would be immensely helpful. Understanding the support timeline for my NVR model is crucial for addressing this with my installer. Knowing when the (C) version was declared EOL would be very handy.

3. Ineffective Automatic Updates: Despite setting up automatic updates, my NVR and cameras haven't been updated automatically, even though I'm aware of newer firmware releases. Is this failure a known issue, or could it be a bug specific to my setup? Any troubleshooting tips or shared experiences with this feature would be appreciated.

------------------------------------------------------------------

4. HTTPS Configuration Challenges: After enabling HTTPS for secure browsing on my NVR, which now works exclusively over HTTPS, I attempted to replicate this for one of the cameras connected to the NVR. Previously, I accessed this camera through

http://192.168.20.200:65004

without issues. Post-HTTPS attempt, I can no longer access it, even when trying the HTTPS protocol. Could there be an inherent issue with enabling HTTPS on cameras connected through an NVR, or is this a configuration error on my part?

I am thankful for any assistance or direction anyone can provide on these matters

 

[JB1970]

Does this successful update indicate that I indeed have the (C) model?

I would say so. Usually if I'm not sure on the hardware revision, I'll first look for the existing firmware version and match that before selecting the latest version from the same location. That's not so easy now, since the download portals are no longer up to date to browse historic files.

How can I verify when the (C) version was declared EOL?

I think it would be considered EOL to some extent as soon as a newer hardware variant of the same model was released. That may just be down to a change of component but they'll not go back to the previous hardware. Ultimately it doesn't affect the warranty, and firmware updates may well continue for some time.

3. Ineffective Automatic Updates: Despite setting up automatic updates, my NVR and cameras haven't been updated automatically, even though I'm aware of newer firmware releases. Is this failure a known issue, or could it be a bug specific to my setup? Any troubleshooting tips or shared experiences with this feature would be appreciated.

A known issue and nothing to be concerned about. My understanding is that the automatic updates being on may allow an update to take place if it's specifically to address a security patch but not for general revisions, bug fixes and features.

I'm not sure on the https issue. If you've enabled https on the NVR and the camera is connected directly to it, there should be no reason to enable https on the camera at all. You've a secure connection to the NVR so nothing is sent as plain text over that part of the connection and if the NVR is connected directly to the camera, nothing should be accessible between the camera and NVR (different if the cameras are connected via the LAN) So the connection is secure using virtual host.

 

[Sunchaser]

Thank you very much for your comprehensive response.

I have implemented HTTPS to ensure that my login credentials remain encrypted while I upgrade the firmware on each camera. Is there a more efficient method for upgrading the cameras that doesn't require individual logins?

As for the camera that has became inaccessible after enabling HTTPS, I presume a factory reset is necessary to fix? I'm puzzled as to why the activation of HTTPS would cause such an issue.

 

[JB1970]

I have implemented HTTPS to ensure that my login credentials remain encrypted while I upgrade the firmware on each camera.

What I was getting at is that it's fine to enable https on the NVR for the reason you state, but if the cameras themselves are connected to the PoE ports of the NVR (rather than via the local network); it shouldn't be necessary to set the camera itself to https.

Is there a more efficient method for upgrading the cameras that doesn't require individual logins?

It can be carried out using iVMS-4200. However I prefer to do them individually. When you update the cameras via iVMS that are connected directly to a recorder, you only get limited information as to the progress. You can't even see the existing firmware version of the camera.

As for the camera that has became inaccessible after enabling HTTPS, I presume a factory reset is necessary to fix?

No. I've got an easy way around that (well 2 easy ways). You need to connect to the camera directly rather than using virtual host on the NVR (which is how you're doing it using port 65004 for cam 4)...

1 - In the camera config page of the NVR, check what IP address the NVR has assigned for camera 4. If the cameras are plug and play, it's likely to be 192.168.254.5 (the NVR is .1 and the cameras are given IP's in that range in the order they are added, though not necessarily in channel order). But check it anyway.

2 - Set a laptop with a static IP address of 192.168.254.100 (it could be 254.anything but 100 ensures it can't conflict)

3 - Connect the laptop to a spare PoE port of the NVR, then just access the camera at https://192.168.254.x (do not append with a port number).

4 - Login is usual and set it back to http

If you don't have a spare PoE camera port on the NVR you can just temporarily disconnect another camera to connect the laptop.

 

[Sunchaser]

Perfect, thanks again for the detailed and complete response.
I will try directly connecting to the NVR tomorrow to disable HTTPS.