7

I am getting the following error when using wget to fetch a file:

  Issued certificate not yet valid.
To connect to www.atlassian.com insecurely, use ‘--no-check-certificate’.

Testing with openssl returns a similar message:

Verify return code: 9 (certificate is not yet valid)
AXE Labs
  • 1,519
  • 5
  • 19
  • 24

5 Answers5

19

Your system clock is likely set in the past.

Phil
  • 1,222
  • 1
  • 7
  • 15
2

When checking the ssl certificate 'notBefore' date with openssl it was valid... It turns out my calling machine's system time was way in the past.

AXE Labs
  • 1,519
  • 5
  • 19
  • 24
1

Sync system clock:

timedatectl set-ntp true
Miguel Mota
  • 351
  • 3
  • 6
0

I fixed that following this tutorial: Network - NTP

Check if your system clock is correct:

timedatectl status
Local time: Fr 2018-02-23 08:47:13 UTC
                   Universal time: Fr 2018-02-23 08:47:13 UTC
                         RTC time: Fr 2018-02-23 08:47:13
                        Time zone: Etc/UTC (UTC, +0000)
        System clock synchronized: yes
 systemd-timesyncd.service active: yes
                  RTC in local TZ: no

If not, install chrony:

sudo apt install chrony

And start chronyd - the actual daemon to sync and serve via the NTP protocol

sudo chronyd
0

For me the issue was system clock out of sync. I wanted to also provide a lync to the fix (setup ntp). How do I update a CentOS server's time from an authoritative time server?

abe
  • 1