Amcrest Forum

Posted: **Wed Oct 09, 2024 2:18 pm**

I have several IP8M-2493E-V2 devices with 2.820.00AC000.0.R,build:2022-03-25 firmware and an IP4M-1041B with 2.800.00AC003.0.R,build:2022-08-11.
Other Amcrest and hikvision cameras that I have do not suffer from the problem below.

All of these devices reboot every hour at approximately the same time, generally 52-54 minutes past the hour. I've verified this using their REST API and by running a syslog server. They are on their on a dedicated subnet. The problem happens with or without access to the internet (they seem to be constantly trying to reach the Amcrest cloud). I have a Ubiquiti network and these are a mix of PoE powered by the switch or via an injector. The switches show that the connected device is reconnecting rather than the switch causing the issue, I also turned STP off on the camera ports.

Has anyone seen anything like this before. I've filed tickets with amcrest support but have yet to receive a response.

Posted: **Wed Oct 09, 2024 3:08 pm**

Hello and Welcome to the Forum..

Not sure what the issue is, Doubt it is from turning off the Spanning Tree, and only time I have ever had an issue like this is from a camera that has some type of damage in the circuit

What I would do is when the camera is working, Log into the cameras WebUI going to the cameras IP address, Then go to Network. then look for the P2P either in the list on the left or under TCP/IP depending on FW and Device. Once you get to the P2P disable that and after about 2 hours there should be no more access from a P2P server and your camera.. As long as you disable and apply/save before the camera reboots it should hold after the reboot and may end before the 2 hours. But normally it isn't the camera that is lagging it is the server that is taking time to complete its mission of hosting the Device..

Some device might reboot when it is trying to access the internet. Some devices at a FW normally in 2019 or 2020 was said required internet access to function. I am not sure that is the case with the 22 FW on both of your devices my guess is that is no longer an issue..

What I would do personally is Do a factory Reset of the cameras and set it back up. Not changing anything in the cameras settings outside of the normal network changes and see if the camera keeps rebooting. If it does I would double check your Switch looking at the port it is connected to and see if there is some type of error that is going on and maybe the Switch is rebooting the port trying to keep it connected..

Posted: **Wed Oct 09, 2024 4:06 pm**

I've already done factory resets, turned off all the P2P options etc. Turning off STP just means that the switch won't ever shut down that port;' the reboots happen regardless of whether it is set or not. There are no errors reported on the switch ports for any of the cameras. The cameras otherwise work fine, with or without, internet access. They just reboot every hour.

Posted: **Wed Oct 09, 2024 4:34 pm**

Don't know it is really strange that 2 Amcrest cameras are rebooting at the same time or time intervals.

One being wifi and one POE are you using the 1041 with an Ethernet cable? If you are using POE to power the POE camera i would double check by using a 12v power and standard Ethernet port.

If you are powering both cameras using a PDU and some type of buck converter to power the 5v camera I would change power supply feed as well. I don't know how you have your cameras connected but again very odd both camera are having same issues.

Posted: **Wed Oct 09, 2024 7:01 pm**

cosn wrote: ↑Wed Oct 09, 2024 4:06 pm I've already done factory resets, turned off all the P2P options etc. Turning off STP just means that the switch won't ever shut down that port;' the reboots happen regardless of whether it is set or not. There are no errors reported on the switch ports for any of the cameras. The cameras otherwise work fine, with or without, internet access. They just reboot every hour.

Is the time correct? Or to better phase the question, is the NVR time set and the cameras synchronized to that time?
I've heard of this problem before, the camera's clock off from the NVR and either the camera reboots or locks out the NVR until the camera reboots.
Since I imagine it still is using self signed certificates and one of the fixes they can deploy as an error trap is to reboot the IOT device in this instance a camera to obtain a new client certificate from the NVR.

Posted: **Thu Oct 10, 2024 3:31 pm**

This is not a POE or wiring problem since I've checked/tested for that, and some of the devices below are powered directly by an injector rather than a switch. The times are all set correctly via NTP. I do not have an Amcrest DVR, and I don't see any attempts by the cameras (networking monitoring via wireshark) to connect to a local NVR. I do see attempts to connect to amazon AWS but allowing those connections or blocking them makes no difference, the reboots continue. I can see the reboots via the amcrest API and I include some of the outputs below.

All of these devices reboot once per hour:

3D printer: 2.800.00AC002.0.R,build:2022-09-08
3D printer: IP5M-T1273E-AI
BBQ: 2.820.00AC002.0.R,build:2023-04-08
BBQ: IP8M-2493E-V2
Backyard Redwood: 2.820.00AC002.0.R,build:2023-04-08
Backyard Redwood: IP8M-2493E-V2
Front Drive: 2.820.00AC002.0.R,build:2023-04-08
Front Drive: IP8M-2493E-V2
Front Yard: 2.820.00AC002.0.R,build:2023-04-08
Front Yard: IP8M-2493E-V2
Laundry Room: 2.820.00AC000.0.R,build:2022-03-25
Laundry Room: IP5M-T1179E
Main Lightwell: 2.820.00AC002.0.R,build:2023-04-08
Main Lightwell: IP8M-2493E-V2
Patio: 2.820.00AC002.0.R,build:2023-04-08
Patio: IP8M-2493E-V2
Pool Equipment: 2.820.00AC002.0.R,build:2023-04-08
Pool Equipment: IP8M-2493E-V2
Side Gate: 2.820.00AC002.0.R,build:2023-04-08
Side Gate: IP8M-2493E-V2
ratcam: 2.800.00AC003.0.R,build:2022-08-11
ratcam: IP4M-1041B

The following devices do not reboot:

BBQ Cabinet: 2.800.00AC004.0.R,build:2023-07-12
BBQ Cabinet: IP4M-1041B
Garage Inside Door: 3.200.00AC000.0.R,build:2024-01-17
Garage Inside Door: IP4M-1066EW

The API shows once per hour, approximately synchronised, reboots.

Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T08:54:06Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T09:54:06Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T11:54:05Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T12:54:05Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T13:54:05Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T14:54:06Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T15:54:05Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T16:54:06Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T17:54:06Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T18:54:05Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T19:54:05Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T20:54:06Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T21:54:06Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T22:59:20Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T23:54:08Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T00:54:07Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T01:54:06Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T02:54:06Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T03:54:06Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T04:54:06Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T05:54:05Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T06:54:04Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T07:59:13Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T08:54:03Z
Side Gate -- http://172.16.9.41:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T09:54:03Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T08:54:11Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T09:54:10Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T10:54:10Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T11:54:09Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T12:54:08Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T13:54:08Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T14:54:08Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T15:54:07Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T16:59:23Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T17:54:10Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T18:54:11Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T19:54:10Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T20:54:10Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T21:54:08Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T22:54:08Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-09T23:54:08Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T00:54:08Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T01:54:10Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T02:54:10Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T03:54:10Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T04:54:09Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T05:54:09Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T06:54:09Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T07:54:09Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T08:54:09Z
ratcam -- http://172.16.9.46:80/cgi-bin/configMan ... LastReboot -- table.OnvifDevice.LastReboot=2024-10-10T09:54:10Z

Posted: **Thu Oct 10, 2024 4:20 pm**

Can I see your Log from the Cameras WebUI?

Here is what mine is for today. I have it setup to reboot every night at 2am..

Code: Select all

1 2024-10-10 18:14:36 admin Set Time 
2 2024-10-10 18:11:35 admin Login 
3 2024-10-10 07:04:25 System Event End 
4 2024-10-10 07:04:24 System Event Begin 
5 2024-10-10 03:01:24 System Set Time 
6 2024-10-10 02:00:05 System Reboot 
7 2024-10-09 23:28:40 admin Logout 
8 2024-10-09 23:28:30 admin Login 
9 2024-10-09 23:18:25 admin Logout 
10 2024-10-09 22:43:53 admin Save Configuration 
11 2024-10-09 22:43:52 admin Save Configuration 
12 2024-10-09 22:43:51 admin Save Configuration 
13 2024-10-09 21:19:11 admin Logout 
14 2024-10-09 21:16:11 admin Save Configuration 
15 2024-10-09 21:15:58 admin Save Configuration 
16 2024-10-09 21:14:48 System Event End 
17 2024-10-09 21:14:46 System Event Begin 
18 2024-10-09 21:14:45 admin Save Configuration 
19 2024-10-09 21:14:08 admin Save Configuration 
20 2024-10-09 21:13:39 System Event End 
21 2024-10-09 21:13:37 System Event Begin 
22 2024-10-09 21:13:36 admin Save Configuration 
23 2024-10-09 21:00:28 System Event End 
24 2024-10-09 21:00:20 System Event Begin 
25 2024-10-09 20:56:40 System Event End 
26 2024-10-09 20:56:33 System Event Begin 
27 2024-10-09 20:55:36 System Event End 
28 2024-10-09 20:55:35 System Event Begin

Only other thing I could think of is if you are using MicroSD cards in your camera and they are failing the camera can reboot but it would be random and the thought they both fail at the same time and reboot at the same time isn't normal..

Posted: **Thu Oct 10, 2024 4:38 pm**

cosn wrote: ↑Thu Oct 10, 2024 3:31 pm This is not a POE or wiring problem since I've checked/tested for that, and some of the devices below are powered directly by an injector rather than a switch. The times are all set correctly via NTP. I do not have an Amcrest DVR, and I don't see any attempts by the cameras (networking monitoring via wireshark) to connect to a local NVR. I do see attempts to connect to amazon AWS but allowing those connections or blocking them makes no difference, the reboots continue. I can see the reboots via the amcrest API and I include some of the outputs below.
.......

The one thing to ask: Log into a camera that is rebooting and under the auto maintence tab/window is the auto reboot checked? If so that is your problem and uncheck it.

I don't know why its connecting to an Amazon AWS, but I would block and check all the setting especially if you bought those cameras used or on ebay.

Posted: **Thu Oct 10, 2024 4:59 pm**

Reaching out to the P2P server as I am still here, Is not the same thing is connecting to the server.. That is part of the P2P and all cameras that are connected with P2P enabled on the camera even if you don't have that camera setup to an app using P2P it will reach out to a P2P server to make sure that it is ready when an App pings the server looking for a hand off connection..

With the camera having a factory Reset there is no way that there is another person that has access to the camera unless they know the current password for the camera if it was used.. I mean sure they would have the SN but without the password it would do them no good..

Posted: **Thu Oct 10, 2024 6:36 pm**

I would update the firmware on the rebooting cameras by downloading its firmware from Amcrest. Especially if the auto reboot option was not checked in the maintenance screen. It would at least make sure they are current firmware.

Amcrest Forum

hourly reboots

hourly reboots

Re: hourly reboots

Re: hourly reboots

Re: hourly reboots

Re: hourly reboots

Re: hourly reboots

Re: hourly reboots

Re: hourly reboots

Re: hourly reboots

Re: hourly reboots