Amcrest Forum

Me too. Joined just to say thanks, since I just obtained my NVR yesterday and installed today only to have the endless reboots.
Not being a networking guy, I need all the help that I can get.
Now I am in the process of running cable all over the attic (in 90+ degree heat no less).
Thanks.

Hi All, I have same issue, could you explain what you made step by step to fix that issue. Because in my URL filtering i added dh.amcrestsecurity.c
om in my blocked section but my unit still reboot? thanks

I'm not sure what type of router or firewall you have to say how to do it step-by-step. But you may try blocking by destination IP address 54.84.228.44.

I read somewhere that there were quite a few reasons why some units were rebooting. Have you unplugged your NVR from the network or even disconnect your router from you modem if you want to the cameras to function while you test to see if it stops rebooting first? If it does, effectively blocking access to the host or IP address seems to be a temporary workaround.

Hi and Thanks for your answer, but unfortunatly the issue seem no fixed by your solution or my blocking rules was created wrong. the following items are what i tried. my NVR is NV4108 and my router is Tplink TL-R470t+ and/or Cisco e1200 (I tried both with no success)

1-NVR+HDD+Camera+Lan+no blocking site in my router = Reboot
2-NVR+HDD+Lan+no camera+no blocking site in my router = Reboot
3-NVR+HDD+Camera+no blocking site in my router and no lan = OK
4-NVR+No HDD+no camera+Lan+no blocking site in my router = Reboot
5-NVR+Lan+no blocking site in my router = Reboot
6-NVR+Lan+camera+HDD+blocking site in my router = Reboot
7-NVR+Lan+no camera+ no HDD+ blocking site in my router = Reboot
8-NVR+No Lan+camera+HDD+blocking site in my router = OK

So the only way my unit work is when the lan are disconnect.
any Idea? or procedure to make sure my blocking site are correclty configured.

To add some color to this I have an NVR4108 that I setup about a month ago that worked just fine with the network cable plugged in. For security when I finished with the setup I blocked outgoing traffic from the NVR in my firewall and except for some snapshot issues the unit has worked well. Last weekend I was making some changes to my network and removed the firewall blocking rule. As soon as I did this my NVR began rebooting with the same issues described in this post. I put the firewall rule back in place and things are running smoothly again. My assessment is that Amcrest must have changed something in the last month that broke how these units talk to their cloud. My rules block outgoing traffic from the NVR to the WAN as follows:

NVR Allow: 52.23.159.0 - 52.23.159.255 (If you want to use LiveView you need this open)
NVR Allow: 8.8.8.8 (Google DNS)
NVR Deny: Everything else

I had same issue as rest on this forum. I am not going to struggle with firewall settings to compensate for Amcrest issues - I am going to return and find a company with a better product. It seems hard to believe Amcrest actually did any testing on this software before shipping it to customers and even more surprising they have not come out with a firmware update yet given the number of people with the issue.

Probably not the best place to ask, but some have mentioned returning their units and going with another AVR than Amcrest. Since I have the Amcrest POE cameras, what AVRs would or should I look at?
Tried a search, and all I got were "systems"...

I just received my NVR yesterday (04/08/16). Have installed HDD and it is showing exactly the same issue. Rebooting, rebooting and rebooting, saving data, cloud stuff... etc... calling tomorrow to return it. Horrible experience...

guycyr wrote:Hi and Thanks for your answer, but unfortunatly the issue seem no fixed by your solution or my blocking rules was created wrong. the following items are what i tried. my NVR is NV4108 and my router is Tplink TL-R470t+ and/or Cisco e1200 (I tried both with no success)

guycyr,

I don't know much about your router or how the little home type router units block config work, I deal with larger enterprise firewalls. No offense, but I'd put money that you are not blocking appropriately. Get the manual for your router.

I've never tried this, but if you leave the LAN unplugged from your NVR, configure a static IP address ... try to set BOTH DNS servers to 127.0.0.1. Don't allow it to use your router or google's DNS. After your sure its using 127.0.0.1, plug the cable back in and it would probably continue to function. HOWEVER, this would break any cloud or remote functions from outside of your home.

This is clearly a workaround at best. If Amcrest would fix this ASAP with a maintenance release I'd be willing to spend more time with this unit. This is ridiculous that they are allowing this to occur. I feel that I have already spent too much time helping them to debug a product that should have been tested in house before shipping.

I'm having compatibility issues with 4 of my Foscam cameras and motion detection too right now. So if I don't get some answers here real soon I'm sending it back and I'll be sure to provide some honest feedback on Amazon as well as to anyone that asks.

crashmw wrote:Probably not the best place to ask, but some have mentioned returning their units and going with another AVR than Amcrest. Since I have the Amcrest POE cameras, what AVRs would or should I look at?
Tried a search, and all I got were "systems"...

I'll second that! Anyone else have a better solution or forum for competitive products? I'm wanting to stay with a small appliance but I may consider a Zoneminder or BlueIris solution soon.