I've suggested that a few times, but I finally had the problem myself and I don't really think that is going to help (though it doesn't hurt to try). I'm thinking the clock drift might be more of a symptom than the root cause.
.
.
.
I'm stumped as to what the trigger might be. It's really weird that only traffic to myAcurite is impacted. Or maybe it's only encrypted traffic that's impacted.
SSL certificate validation is dependent on the local clock. Did the clock drift far enough (or reset to 1970-01-01) to make the SSL library puke for an expired certificate?????
I didn't see any large drift of the clock in my case. The splash page doesn't present the actual time, but the times each sensor was last heard, so I just look to see if the minutes line up with my laptop clock.