Written 5 Sep 2026. This is a how-to, not a product card.

When the computer's clock is wrong

HTTPS fails, apt says the Release file is not valid yet, or logs look like 2019. Check the clock, turn network time on, set the house zone. You don't need a GPS clock hat.

Haven't finished the install weekend yet? Start with your first weekend. Need SSH first? That is SSH from the couch. Clock is only an hour off and you just want the city zone? That calm set is set the computer clock to your house. This note is for when the year is wrong, certificates scream, or weekly updates refuse to run because the computer thinks it is still last decade.

Skip until you can SSH in

If the computer does not answer from the couch, fix that first: when SSH won't connect. This walk assumes a login prompt on the house network.

What is going on

Browsers and apt trust certificates that only look valid for a window of dates. If the computer's clock is years early or late, every secure site looks expired or “not valid yet.” Package mirrors fail the same way. Old Marketplace desktops often lose the tiny CMOS battery that keeps time while the power cord is out. Network time (NTP) can also be off. Wrong city zone is milder: Sunday backups fire at the wrong hour, but HTTPS still works.

1. Print what it thinks

SSH in, then:

date

Compare that line to your phone. Off by a few minutes is fine. Off by hours, months, or years is the problem.

For more detail:

timedatectl

Read Local time, Time zone, and the NTP / System clock synchronized lines. If NTP shows inactive, or synchronized says no, keep going.

2. Turn network time on

On Debian or Ubuntu:

sudo timedatectl set-ntp true

Wait a few seconds, then:

timedatectl

You want NTP active and the clock synchronized when the house can reach the internet. Confirm with date again. If it snaps to the right year, you are mostly done. Still set the house zone in step 3 if Time zone is UTC or a city you do not live in.

3. Set the house zone

Pick a city zone for the house (example America/Chicago). List a short set:

timedatectl list-timezones | grep America

Swap America for Europe, Asia, or Africa if that is where you are. Then:

sudo timedatectl set-timezone America/Chicago

Confirm with date. The fuller calm walk is set the computer clock to your house.

4. When NTP cannot fix a wild clock

If the year is still wrong after step 2, check that the computer reaches the internet:

ping -c 3 1.1.1.1

Numbers fail? Fix the cable or house network before you fight time. Numbers work but names fail? See see which name server the computer is using.

When the net is fine and NTP still will not catch up, set the clock once by hand (swap the stamp for roughly now in UTC or local, then let NTP refine):

sudo timedatectl set-ntp false

sudo timedatectl set-time '2026-09-05 22:55:00'

sudo timedatectl set-ntp true

Use today's real date and a close time. Then date again.

If every reboot after a night unplugged drops the clock back to 2019, the coin battery on the board is likely dead. Common on old OptiPlex and EliteDesk boxes. Leave it plugged in so NTP can heal it after each boot, or replace the CR2032 when you next open the case. You do not need a GPS hat for a house PC.

5. Retry the job that broke

When date matches the house:

sudo apt update

Then the usual upgrade if that was the failure: keep the computer updated. Browser HTTPS errors on the computer itself should clear after a reload. Weekly update still stuck for other reasons (locks, full disk)? That is when weekly updates won't install.

What this is not

This is not a reason to buy a new mini PC, a GPS NTP appliance, or a Raspberry Pi clock hat. It is not a dual-boot Windows clock lecture. It is not editing random files under /etc on day one when timedatectl works. Fix the clock, then leave it alone.

What next

Calm weekly fixes: keep the computer updated. If apt still fights you after the clock is right: when weekly updates won't install. Just want a print of the clock later: see what time the computer thinks it is. Weekly backup timers only make sense on the house zone: back up the folder every week without remembering.

Optional: jot that the clock was years off (and whether you replaced the CMOS battery) in Lab plan — username + passkey, no email. Skip if you just want to keep reading.

Skip

• Skip a GPS clock hat or NTP appliance for one old PC.
• Skip buying a new mini PC because the year was wrong.
• Skip dual-boot Windows clock essays on day one.
• Skip hand-editing /etc/ntp.conf when timedatectl set-ntp true works.
• Skip this if the clock already matches your phone. Use the zone note only if the hour label is wrong.