stable 04-06 :: SSL error in most logs, during first part of update

[Olzeke51]

Describe the bug this was also noted in earlier 'latest' updates 2021-01-02 16:06:26.003 | WARNING | 271 | mycroft.api:check_remote_pairing:549 | Could not get device info: SSLError(MaxRetryError("HTTPSConnectionPool(host='api.mycroft.ai', port=443): Max retries exceeded with url: /v1/device/e05bbe67-f0e6-44ab-aba7-d6324451632f (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1123)')))"))

To Reproduce Steps to reproduce the behavior: part of the update process - and most/all reboots of any kind

Expected behavior I even set my TZ to Kansas and still got similar error about 2 'latest' updates ago

Log files mycroft_stable_04-06.tar.gz Restart log files mycroft-Restart.tar.gz

*Environment:**

• Device type: Mark-II -rPi4-DEVKIT on network cable, uSDC
• OS: default (per Mycroft) Ubuntu 20.04.2 LTS
• Mycroft-core version: 20.08.1 -per Home.Mycroft.AI device information
• Other versions: stable 04-06

[krisgesling]

Ken or @chrisveilleux might chime in and correct me but I believe this is because the Raspberry Pi doesn't contain a real-time clock (RTC).

What this means is that anytime the device powers down it reverts to it's factory standard datetime until it can boot, connect to an NTP server and get updated. Before the time gets updated, it will believe it's in 1970 and so the SSL cert process rejects the requests. Once it gets the correct time the connection handshakes start to succeed.