Amcrest Smart Home "Server" down?

[amcrest168]

AWS changes public IPs all the time.

hence we should anticipate more outages until amcrest releases another firmware. thanks to @GaryOkie, a workaround has been validated.

[djsteve]

There are clear domain names and DNS shown in the config file. Why on earth are those even there if the AD110 is programmed to ignore and instead use a stored static IP? Who comes up with this mess?

I assume the prior firmware did not have the static IP defined. Looking through the config file I see a TON of questionable content — Chinese domains, clear text storage of my WiFi password, etc.

[GaryOkie]

The static "DMSServerIP" was there in the original firmware as well. Why the AD110 is programmed to not connect to the hostname is a question only Amcrest can answer. The hardcoded IP makes no sense, especially given that the IP's have been changing for whatever reason that AWS deems necessary.

Here is how I suspect this is all going down. We know that dms.zencamcloud.com is configured in DNS to use 2 IP's for round-robin resolution. Usually the first IP to respond is the one the client will use. So an IP assigned to the AWS server in San Jose will likely be used instead of the AWS server in Virginia for someone who is on the left coast. During the AD110 setup process, for some inexplicable reason, the IP selected by round-robin is stored in the config and appears to be used exclusively from then on.

There is no known way to change this IP without repeating this setup process, initiated by a factory reset.
The doorbell then picks up one or the other now-working IP's returned by DNS during setup.

So a little over 2 weeks ago, I think the folks that had the San Jose server IP saved in their AD110 config went offline due to the IP going dead. My AD110 was still working fine using the VA server IP - until a few days ago, when it too went dead. This may explain why Amcrest was quizzing us about State locations. But the fact they are asking this concerns me a lot - what happened to the developers who should fully understand this IP issue already?

@srags - it's great you were able to utilize the IP redirection hack to get both your systems back online. Glad I could help!

[Revo2Maxx]

Wonder if the the servers are the same for the Round Robin or if they should be using Weighted Round Robin? Maybe the fail is that the first server on normal is less ram and cpu power and gets over loaded with traffic and fails? Maybe if there is only 2 servers for this maybe they need a 3rd if they are using the same? However from the sounds and everything that is in the backup it sounds like neither are being used and are using one called a Sticky and is why there is a IP in the backup rather then being able to follow or change IPs when the balance goes all off and server switches the Camera keeps trying to run off the same ip and when it is down changes the the doorbell to false on being online...

If they are using Sticky they need to change the times that the camera can change IPs to a lower time to avoid this Seeing all contact will be on that IP listed in the backup until the set times expire then when it looks for a request for the server it can get any that are able to respond rather then one that is over loaded...

[GaryOkie]

I'm not really sure what you are theorizing here. The AD110 is storing one of the IP's internally from the initial setup and running with that until it gets reset again. How exactly it is obtaining the IP is not certain and not all that relevant, but my take is that is simply getting the first DNS round-robin IP that responds. If it uses some other method to save a static IP, well... it's wrong too.

[Revo2Maxx]

Sorry i am not in R&D and the Sticky is what seems to be happening and that is why I mentioned it.. It is a Round Robin setup that when it lets say for this issue (When camera Resets the Camera then goes out looking for the cloud and it has a couple or a few IP's that it can connect to for load balancing in Sticky when it gets the IP it is Stored and next time Camera looking for Server it will be at the same IP until Sticky time is over, Then next request will result what ever IP is able to take the request..)))

I am not saying this is how it is going I am guessing with it having a IP that it fails to keep access this method of Round Robin seems likely. I am going to guess they have it setup with much to long time for keeping the IP.. Also to me looks like it might be 60 days? If that is the case that is way to long..

[tgfarrell]

Can we go back to the old firmware? Is that possible?

[Revo2Maxx]

Sadly no one for me to ask in office this weekend with the world being locked back down in some places Texas is one of them.. As soon as I get an answer I am going to guess on this it might be not able to go back because there was some updates in the FW that going back would remove and might make the AD110 not work right...

[GaryOkie]

What are you thinking the old firmware will resolve @tgfarrell ? Is your system offline now or is it that you still can't access SD-Card recordings? I've not read anyone else having that issue whose system was online so I would start with formatting the SD-Card again, and failing that, get a new one. You could also try putting the card in your PC to see if it is readable but that doesn't necessarily mean the AD110 will also be happy with it.

@Revo2Maxx - so you think the AD110 will update the stored IP after a longish period of time without a reset? Huh, that's possible. I doubt it though. Whatever - it's still wrong, except as a good way to lose customers.

[Revo2Maxx]

Sadly all this has to come out during this Virus issue time and I hope they get things fixed at the FW or Hardware level before it drives people away.. If it was or would reset after long time it would be offline far to long to make people using it as a stand alone device happy... For me I don't even know it goes offline because I have it on my NVR that keeps recording the device when offline the app.. Only time I use the App is if someone presses the button and with all the cameras and PIR devices that don't happen often because I will beat them to the door...

Thanks for all your Help with this and helping others get a work around for a little time hope enough time for it to get fixed by Amcrest... Just wonder how long the 2 IP's that are used for the ones using the work around will stay as good IP's seeing last week IP was 52.3.69.209