# Net::err\_cert\_date\_invalid

**URL:** <https://community.letsencrypt.org/t/net-err-cert-date-invalid/81001>\
**Category:** Help\
**Created:** [December 27, 2018, 12:30am UTC](https://community.letsencrypt.org/t/net-err-cert-date-invalid/81001 "2018-12-27T00:30:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![direclaw](https://avatars.discourse-cdn.com/v4/letter/d/94ad74/32.png) [@direclaw](https://community.letsencrypt.org/u/direclaw)\
**Post date:** [December 27, 2018, 12:30am UTC](https://community.letsencrypt.org/t/net-err-cert-date-invalid/81001/1 "2018-12-27T00:30:32Z")

</div>

After activating one of my websites, one of my clients complained that this error was showing up:

 ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/4/3/434928a8f49edd50505de55950788d48f89cf5ea.jpeg)

The translation would be

> Your clock is late
> 
> It is not possible to establish a connection with www.trilhasereceptivos.com.br because the hour and date of your computer (Wednesday, Decempter 26 2018 20:33:47) are incorrect

I asked her to access another website that was activated the same way and it was fine. Her clock seems to be off by one hour, but according to her, her area is not affected by daylight saving time and her clock is indeed correct.

The certificate was created today and is not close to renewal date. I've rebooted the server to make sure it is not related to that.

My domain is: trilhasereceptivos.com.br

I ran this command: sudo certbot certonly --webroot -w public -d www.trilhasereceptivos.com.br -d m.trilhasereceptivos.com.br -d trilhasereceptivos.com.br

It produced this output:

```
 - Congratulations! Your certificate and chain have been saved at:
   /etc/letsencrypt/live/www.trilhasereceptivos.com.br/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/www.trilhasereceptivos.com.br/privkey.pem
   Your cert will expire on 2019-03-26. To obtain a new or tweaked
   version of this certificate in the future, simply run certbot
   again. To non-interactively renew *all* of your certificates, run
   "certbot renew"

```

My web server is (include version): Apache/2.4.7 (Ubuntu)

The operating system my web server runs on is (include version): Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-92-generic x86\_64)

My hosting provider, if applicable, is: AWS

I can login to a root shell on my machine (yes or no, or I don't know): Yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): No

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [December 27, 2018, 12:43am UTC](https://community.letsencrypt.org/t/net-err-cert-date-invalid/81001/2 "2018-12-27T00:43:14Z")

</div>

Certificates have an expiration date and a "not valid before" date -- if you time travel to the past, or your computer's clock is incorrect, certificates can be _not yet_ valid.

Let's Encrypt certificates have a "not before" time of 1 hour before the moment they were issued. (And in fact expire 89 days and 23 hours after they were issued.)

If your clock is more than 1 hour slow, you will get that kind of error.

> [@direclaw](#):
>
> I asked her to access another website that was activated the same way and it was fine. Her clock seems to be off by one hour, but according to her, her area is not affected by daylight saving time and her clock is indeed correct.

Can you ask her to double check? It seems she was mistaken.

Edit: There's "correct" and then there's correct. If the clock is 1 hour slow, but the time zone setting is 1 hour fast, it can _appear_ correct when it's not.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [January 26, 2019, 12:43am UTC](https://community.letsencrypt.org/t/net-err-cert-date-invalid/81001/3 "2019-01-26T00:43:15Z")

</div>

Closed on January 26, 2019, 12:43am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.