We are deploying latest updates to a device - based on the Asset Tracker Template using the memfault OTA releases for our test cohort.
This worked yesterday but today all 5 test devices are showing the following error:
[24:16:24.359,436] <inf> downloader: Setting up TLS credentials, sec tag count 1
[24:16:24.359,741] <inf> downloader: Connecting to 34.200.153.177
[24:16:27.614,105] <err> downloader: Server responded with code 0xa5
Over and over again. We obviously need to detect this issue and stop trying as its going to kill the batteries but what is going on with the FOTA servers and has this happened before?
FYI - the server is not reporting rate limit issues and we have developer mode enabled.
