Amcrest Smart Home "Server" down?

[amcrest168]

hmm... my nvr shows the doorbell went offline 02:01:11am and came back on 02:01:47am pdt. could it be a scheduled reboot? my night vision has been on 'auto' hence i would not be able to tell whether it's night vision related. a night vision cycling would have triggered a motion detection recording on nvr which i don't see in mine.

[GaryOkie]

Yes, there is a scheduled reboot hard coded in the firmware "AutoMaintain" settings that I hadn't noticed before. (day 2 = Tuesday, at 2:00AM). There are also autoshutdown and autorestart settings, but not enabled.

I guess that's one way to solve potential slow memory leaks. Would have been nice to have this configurable in the app rather than a fixed reboot time for every AD110 doorbell that could theoretically be taken advantage of.

"AutoMaintain" : {
"AutoRebootDay" : 2,
"AutoRebootEnable" : true,
"AutoRebootHour" : 2,
"AutoRebootMinute" : 0,

Note: these settings were present in the original firmware as well

[amcrest168]

hi @GaryOkie, i noticed the cloud servers ips have changed today to 3.210.92.130 and 35.168.244.201. last week they were 50.19.133.142 and 34.199.92.115. it's a good the doorbell stayed connected with the ip changes.

[Revo2Maxx]

Wonder at what time it made the change over because I see there is a time on my NVR that shows there is recording however when I play the area before an outage it goes offline about 40 min before the area missing on my NVR...

However looking at my Current config backup I am still connected to the same .142 that was there after last Reset.. Strange thing though as of yesterday my Camera is now showing GREEN HUE and I hate it... I did a Reboot by App but that didn't correct the issue

[tgfarrell]

So coincidentally (or not) I cannot login into my amcrest account where I registered my doorbell. Its like they lost my account. I tried the password reset link and it never sent a reset message. That tells me they probably don't have my account any longer. Maybe someone reloaded an old backup and lost accounts. I'm thinking that might be some of my problem since I never went down in the beginning and just recently went offline. I'm going to see if I can recreate my account. I don't even remember the details of doing it right now. Maybe the app walked me through the setps.

[tgfarrell]

I can reset my password via the app and login and logout using the app fine but not the support website. Maybe support requires yet another account setup? Anyway false trail I think. I think I'll hard reset now that I can login via the app.

[tgfarrell]

Even better, after resetting my password in the app, I get an email from amcrestcloudsupport verifying that the password was changed.

[tgfarrell]

FYI, probably posted before but thought I'd throw it out here. Not the doorbell but I wonder how much shared code there is and the cloud service is part of the problem too.

https://threatpost.com/amcrest-critical ... es/145507/

[GaryOkie]

hi @GaryOkie, i noticed the cloud servers ips have changed today to 3.210.92.130 and 35.168.244.201. last week they were 50.19.133.142 and 34.199.92.115. it's a good the doorbell stayed connected with the ip changes.

Interesting. That's because last weeks 2 IP's still respond on TCP port 15301. So do the 2 new IP's this week. No telling how much longer last weeks IP's will still connect. Things are sure being shuffled around at AWS a heck of a lot.

[rd988]

I have the iptables hack to keep my doorbell online, and today it wants to do a firmware update.
I am on 1.000.00AC004.0.R.200509
and it can upgrade to
V1.000.00.AC004.0.R.20200701

I am gonna hit update....

Anyone else do it yet?