When a browser shows NET::ERR_CERT_DATE_INVALID, it is saying that the certificate's validity period does not match the current date on the device. Every SSL certificate carries two dates, notBefore and notAfter, and the browser checks the device clock against that window. The check has two sides, so the first job is to work out which side is wrong before changing anything on the server.
Is it the site or the device?
Open the site from another device. If it loads on your phone over mobile data but fails on one office computer, the problem is almost certainly that computer's clock. If it fails everywhere, on different networks, the certificate has expired or the server is still serving an old one. Another clue: a wrong clock breaks almost every HTTPS site at once, including Google, banks and webmail. If only one site fails, look at its certificate.
Why device clocks go wrong
A few seconds or minutes of drift does not trigger this error; it takes days, months or years. Typical causes are a dead CMOS battery that resets the date on every power-off, automatic time sync being disabled, a phone left off for a long time and started without internet, or a confused date versus time zone. On Windows, enable "Set time automatically" under Time & language, or force a sync from an administrator command prompt:
w32tm /resync
On Linux desktops and servers:
timedatectl
sudo timedatectl set-ntp true
On Android and iPhone, turn on automatic date and time.
Example: a school computer lab
A school in Samarkand has twenty old computers in its IT room. After the summer break, students could not open any website, all showing ERR_CERT_DATE_INVALID, while phones on the same network worked fine. The computers turned out to be showing a date several years in the past: they had been unplugged all summer and their CMOS batteries were dead. New batteries plus automatic time sync solved it completely. Contacting site owners or touching any server would have achieved nothing.
Checking the certificate dates yourself
If the error appears everywhere, inspect the certificate the server is sending, either through the padlock in the browser or from a terminal:
openssl s_client -connect example.uz:443 -servername example.uz </dev/null 2>/dev/null \
| openssl x509 -noout -dates -issuer
If notAfter is in the past, the certificate really has expired. If the dates look fine but some visitors still get the error, their clocks are the likely cause. If the site runs on several IPs, check each one, since one may still serve an old certificate.
When Let's Encrypt stops renewing
Let's Encrypt certificates are short-lived and designed to renew automatically, but renewal can fail silently after certain changes. The most common one is pointing the domain's A record or nameservers elsewhere, so the validation request reaches a different server. Another is a rule that blocks or redirects /.well-known/acme-challenge/. For example, the owner of a small Tashkent online shop on misol.uz pointed the A record to a test server and forgot to switch it back; weeks later renewal failed, the certificate expired and customers saw the error. Once DNS was corrected, the certificate was reissued in the hosting panel.
On sayt.uz hosting, Let's Encrypt certificates renew automatically as long as the domain points to the hosting server. If one has expired, check DNS and nameservers in the sayt.uz cabinet first, then reissue the certificate from the hosting panel or contact support.
Intermediate certificates and old systems
Sometimes the site certificate is valid but an intermediate or root in the chain is the issue. Very old operating systems have outdated trust stores and may treat some chains as expired or unknown; updating the device or browser is the fix. On the server side, always serve the full chain, because omitting the intermediate causes different errors on different devices.