Hassio 90.1 warning: hassio.updater cert failure

Got this message in the logs during booting (may have begun in 90.0):

18-06-22 11:12:17 WARNING (MainThread) [hassio.updater] Can’t fetch versions from https://s3.amazonaws.com/hassio-version/stable.json: Cannot connect to host s3.amazonaws.com:443 ssl:True [SSLCertVerificationError: (1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1056)’)]

I noticed this on first boot but did a reboot and it had gone. Have you seen it more often?

With every reboot, tried several times.

1 Like

Started removing recent addon’s: the most recent was spotify-card. It works, but I keep having to authorize, which it did.

My configuration for this card was concurrent with the Hassio Spotify addon. I did create separate Spotify apps, and client_id’s, etc… After spotify-card was installed, the hassio spotify player would report errors (token expired) at times.

I am not at all sure where the loose bit is: it could be spotify-card, or the way dual client_id are handled, or ?

When I have seen a certificate not yet valid error the date or time settings on the computer were incorrect. Be sure the time zone is correct too.

Thank you for the suggestion.

After watching this for a few days, it is about 50/50 if Hassio reboots without this error message. I have about 50 devices on the network, many using same time server. For now, the problem is local to Hassio. (on as Rasphberry 3 PI+).

Whenever it fails to boot cleanly, the time is not correct until a few lines after the reported error. Soo, Hassio ability to reliably obtain time early in the bootup sequence is the issue.

Agreed - same observation. I get the errors mentioned above, with a date of 11 months prior, then a few lines later the log entries are timestamped correctly.

I recently switched to a native NUC based HA, it does not exhibit this issue.