Server Certificate Verification Failed about blacklist

[britannic]

@tlsnine, did you follow the directions on adding the signing key before installing using apt-get? Also, you should be using the latest release: v1.1.7.8

[tlsnine]

I followed your instructions in order as they appear on github. Whenever I attempt to add the key, I get: trace@ubnt:~$ sudo curl -L https://raw.githubusercontent.com/britannic/debian-repo/master/blacklist/public.key | sudo apt-key add - % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (60) SSL certificate problem: certificate is not yet valid More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. gpg: no valid OpenPGP data found. I’ve attempted this command with the -k and I get: trace@ubnt:~$ sudo curl -k -L https://raw.githubusercontent.com/britannic/debian-repo/master/blacklist/public.key | sudo apt-key add - % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 3112 100 3112 0 0 10003 0 --:--:-- --:--:-- --:--:-- 12806 gpg: key 5273D52C was created 99278413 seconds in the future (time warp or clock problem) gpg: key 5273D52C was created 99278413 seconds in the future (time warp or clock problem) gpg: key 5273D52C was created 99278413 seconds in the future (time warp or clock problem) gpg: key 5273D52C was created 99278413 seconds in the future (time warp or clock problem) OK EDIT: cleaned up

[tlsnine]

Does this have anything to do with the underlying EdgeMax software being moved to Stretch from Wheezy?
Again, my firmware is 1.10.10 now.

[tlsnine]

Closing this as ID10T on my side...
My ER4 wasn't grabbing the correct time from my NTP server. (weird!)
I had to manually run "set date ntp" and everything fell into place after that.
My bad.
Thanks!