Web Interface Failure and Inaccessible

[easonisharper]

Hi,


I’m running into a pretty odd issue with my Hikvision camera and wanted to ask if anyone here has experienced something similar.


Model: DS-2CD7526G0-IZ(H)S
Tested firmware: V5.6.12 build 200729.


Issue description:
Recently I just got 3 Hikvision cameras from FB marketplace. To add it to my existing Reolink NVR system to perform better night vision, but also capture the license plate. But two of them having the web interface access issue. Camera steaming works well. After doing a clean TFTP firmware recovery, the camera boots up fine and I can log into the web interface without problems. However, as soon as I go into the configuration pages (for example, the Maintenance tab) and change any settings, the web UI completely crashes and becomes inaccessible.


What I’ve tried:

• After TFTP recovery, the web UI works at first
• Once I enter Maintenance or change settings, the web UI stops working entirely
• Factory reset(camera reset button and software reset) does not fix the issue
• Only another TFTP recovery brings it back, but the problem repeats
• I tested it on the older firmware, and updated to newer firmware, the issue happens like the same.
• Hitool delivery software can configure the camera.

Is there a way to completely flash the camera or has anyone done this? I'm thinking the problem is related to the rom partition stuff...

For reference, I also have another camera (DS-2CD2087G2-L) showing very similar behavior.


Any help or advice would be greatly appreciated. If anyone has a working firmware link, that would be super helpful too.

 

[alastairstevenson]

Recently I just got 3 Hikvision cameras from FB marketplace.

Were they sold as 'used, working' or as 'spares and repairs' or equivalent?

However, as soon as I go into the configuration pages (for example, the Maintenance tab) and change any settings, the web UI completely crashes and becomes inaccessible.

What browser are you using to access the web GUI?

To add it to my existing Reolink NVR system

Is this a PoE NVR, or are the cameras connected to the LAN and powered separately from the NVR?

For reference, I also have another camera (DS-2CD2087G2-L) showing very similar behavior.

That does suggest the problem isn't due to the cameras themselves, but something in their environment.
How are the troublesome cameras being powered? Were they all connected to the same network port?

Is there a way to completely flash the camera or has anyone done this? I'm thinking the problem is related to the rom partition stuff...

But you've said that you have re-applied the firmware.with no apparent problems.
Have you tried resetting the camera to factory settings to see if the same behaviour persists?

 

[johnfitz]

That does suggest the problem isn't due to the cameras themselves, but something in their environment.

This is a longshot, but maybe try clearing browser cache and cookies?

 

[easonisharper]

Were they sold as 'used, working' or as 'spares and repairs' or equivalent?

He showed me it works on his Hik NVR, but no the web interface. I suppose its sold as used working. Believe it or not, I got these 3 cameras DS-2CD7526G0-IZ(H)S, DS-2CD2647G2T-LZS, DS-2CD2087G2-L in just $100! The last one is even free. So keep your eyes on the local market as you may find some really good deals.

What browser are you using to access the web GUI?

Chrome latest version, Microsoft Edge latest version. Even with Safari on my iphone

Is this a PoE NVR, or are the cameras connected to the LAN and powered separately from the NVR?

It is a PoE NVR. All of my cameras are connected to the Reolink NVR as it supports the bridge mode. I have an Amcrest PTZ camera that works well.

That does suggest the problem isn't due to the cameras themselves, but something in their environment.
How are the troublesome cameras being powered? Were they all connected to the same network port?

As I said all camera is powered by PoE NVR, all camera are in the same network environment as my phone(aka, same 192.168.0.XXX), not in the subnetwork.

But you've said that you have re-applied the firmware.with no apparent problems.
Have you tried resetting the camera to factory settings to see if the same behaviour persists?

I tried them all. But none of them work.

 

[easonisharper]

After a few days, I figured out the problem. I searched on this forum and also found other user has some similar issue like web interface not working. Here is my solution(AI altered):


Issue Description and Solution:
Using HiTools Delivery, I was able to access the Advanced Settings menu(I also set the 80 port to 81, but not sure if this would affect; I put it here just in case), but it takes a very long time to load. That’s why, when accessing through a browser, the browser thinks the server isn’t responding. The camera’s default HTTP service is extremely slow.


Once it eventually loaded, I enabled HTTPS browsing in the network settings. After that, accessing via the HTTPS port worked completely fine.


Before this, I had changed the HTTP port from 80 to 81. It could load, but it would freeze at the login stage. If I changed the HTTP port again, I could log in once, which was very strange.

---

AI Analysis:

• Symptoms observed
  
  • After TFTP flashing, the web interface was accessible, but HTTP was extremely slow.
  • Browsers assumed the server was unresponsive, causing “timeout” behavior.
  • Using HiTools Delivery → Advanced Setting worked, which shows the internal web service was still functional but unstable.
  • Enabling HTTPS fixed everything; the interface worked normally over the HTTPS port.
  • Changing the HTTP port (80 → 81) temporarily allowed login once, but then it froze again.
• Likely root cause
  
  • This is not a network/browser problem but a firmware bug in the HTTP service module.
  • The HTTP daemon (lighttpd/httpd) used in older Hikvision firmware is inefficient or uses blocking I/O, which makes it very slow on modern browsers.
  • When you switch the port, the service restarts, which explains why it briefly works once.
  • The HTTPS service, on the other hand, is implemented differently (with OpenSSL, multithreading, etc.) and does not suffer from this bug.
  • Modern browsers also handle HTTPS sessions more reliably than outdated HTTP implementations in legacy firmware.
• Conclusion
  
  • This is a firmware HTTP module defect, especially common on older hardware running newer firmware versions (e.g., G0 series upgraded to 5.6/5.8).
  • The HTTP service is outdated and unstable, while the HTTPS service works correctly.
• Recommended solution
  
  • Stop using HTTP entirely. Switch to HTTPS-only for management.
  • In System → Network → Advanced → Platform Access/Web, enable HTTPS only.
  • Bookmark the camera as:
    
    
    <span><span>https:</span><span><span>/&lt;camera_IP&gt;:443/</span></span><span><br></span></span>
    (or use the custom port you configured).
  • For NVR or third-party integrations, rely on ONVIF/RTSP instead of the HTTP web interface.

In short: the camera isn’t broken — the problem is that the Hikvision firmware’s HTTP service is poorly implemented. By switching to HTTPS, you avoid the bug completely.

 

[alastairstevenson]

Chrome latest version, Microsoft Edge latest version. Even with Safari on my iphone

OK - that lets out a problem with a specific browser version.

I searched on this forum and also found other user has some similar issue like web interface not working.

Can you provide a link to that thread?
It certainly used to be the case a while back that customising the HTTP port away from 80 could cause access problems.

In short: the camera isn’t broken — the problem is that the Hikvision firmware’s HTTP service is poorly implemented.

I'm a bit skeptical that there is such a basic and obvious current problem in Hikvision's HTTP web server implementation.
I think we'd have seen lots of posts commenting and asking about this if it was so.
I don't see any slowness of the camera web GUI myself, and I've used lots of Hikvision cameras.

It is a PoE NVR. All of my cameras are connected to the Reolink NVR as it supports the bridge mode. I have an Amcrest PTZ camera that works well.

OK, so the cameras are being accessed via the NVR firmware and hardware, the PoE ports of which are set to bridge mode.
I'm speculating that the Reolink firmware might be the underlying cause of the problem - it's a common part of the environment.
A suggestion as an experiment :
With the camera powered separately, on 12V and connected to your LAN switch or router, or via a PoE switch, and with the HTTP port at it's default 80 value, test out how responsive the camera web GUI is.
That removes the NVR internal bridge-mode processing from the data path between the camera and the browser.
It would be interesting to hear what you find.

 

[johnfitz]

I'm a bit skeptical

me too