Ca.pem file - After 4 years of use we suddenly had many devices fail to reconnect

I think this needs to be fixed, you have paying customers in this forum who have missed this detail and are being caused pain. Would be very beneficial to include this information in the mDash/Mongoose OS documentation somewhere.

@cesanta can you point me to some details on where the build process so I can educate myself?

What I don’t understand is why this is just happening now - my ca.pem that exists on all my devices seems to be the same which is:

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            44:af:b0:80:d6:a3:27:ba:89:30:39:86:2e:f8:40:6b
        Signature Algorithm: sha1WithRSAEncryption
        Issuer: O = Digital Signature Trust Co., CN = DST Root CA X3
        Validity
            Not Before: Sep 30 21:12:19 2000 GMT
            Not After : Sep 30 14:01:15 2021 GMT
        Subject: O = Digital Signature Trust Co., CN = DST Root CA X3

Looks like the cert expired a few years ago and never had an issue somehow?

From my limited testing, fortunately the fix seems to be as easy as creating a new FW that includes the ca.pem file I’ve created per the instructions in the Cesanta post and adding it to the filesystem.

Still trying to work out what I do for devices that have been offline for a little while and may come back online after the 30 day countdown…