---
title: "The certificate for this server is not yet valid (NSURLErrorDomain -1204) on Mac · Kilobat Guides"
url: "https://kilobat.app/guides/nsurl-error-1204-certificate-for-this-server-is-not-yet-valid"
description: "An app shows The certificate for this server is not yet valid, error -1204. The Mac clock is behind, or the server is new."
---

# “The certificate for this server is not yet valid” (NSURLErrorDomain -1204) on Mac

The certificate starts later than the date that the Mac knows. Most often the Mac clock is behind.

**Fix this with your agent**Copies a prompt for Claude Code, Codex or any agent that can use Terminal.

My Mac has this problem: “The certificate for this server is not yet valid” (NSURLErrorDomain -1204) on Mac. Read https://kilobat.app/guides/nsurl-error-1204-certificate-for-this-server-is-not-yet-valid.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.

Applies to: macOS 13 Ventura and later. The text was checked in CFNetwork on macOS 27.2. · Checked: 29 October 2026

## Symptoms

- An app shows “The certificate for this server is not yet valid.”
- Console shows NSURLErrorDomain Code=-1204.
- The same site can open on another device or network.

## Likely causes

- **A wrong Mac clock.** The Mac date is earlier than the real date.
- **A new certificate.** The server uses a certificate that starts later than today.
- **A Mac that was off for a long time.** The clock can be wrong until it syncs.

## How to check

1. Show the certificate that the server sends.

   ```
   openssl s_client -connect example.com:443 -servername example.com </dev/null
   ```
2. Compare the Mac date with another device. Use System Settings › General › Date & Time.
3. Request the page and show each step of the connection.

   ```
   curl -v -o /dev/null https://example.com
   ```

## How to fix it

1. Turn on automatic date and time in System Settings › General › Date & Time.
2. Connect to the internet so that the clock can sync.
3. If the date is right, tell the owner of the server.
4. Restart the Mac after the clock is right.

## With Kilobat

1. Check Wi-Fi, the router, the internet, DNS and login pages in one step.

   ```
   kilobat diagnose
   ```
2. If one site or service fails, find the layer that stops it.

   ```
   kilobat why example.com
   ```
3. The CLI is free. In the app, the advice from these checks is part of Kilobat Pro. See [Find why one site or API won't connect](https://kilobat.app/guides/recipes/why-cant-it-connect).

## Questions

**Why can a Mac clock be wrong?**

A dead clock battery, a long time off or a failed time sync can do it.

**What about the opposite?**

A clock that is ahead gives the expired message. See [“The certificate for this server has expired” (NSURLErrorDomain -1201) on Mac](https://kilobat.app/guides/nsurl-error-1201-certificate-for-this-server-has-expired).

## Sources

- Error text in CFNetwork.framework, macOS 27.2 (Localizable.loctable)
- curl(1) and nc(1), man page installed with macOS 27.2

Checked on 29 October 2026.

## Related guides

- [NET::ERR_CERT_DATE_INVALID in Chrome on Mac](https://kilobat.app/guides/err-cert-date-invalid): The server's certificate looks expired or not yet valid by the Mac's clock.
- [“The certificate for this server has expired” (NSURLErrorDomain -1201) on Mac](https://kilobat.app/guides/nsurl-error-1201-certificate-for-this-server-has-expired): The certificate is out of date, or the Mac thinks that it is.
- [“This Connection Is Not Private” and certificate warnings on a Mac](https://kilobat.app/guides/connection-not-private-mac): Safari shows a certificate warning when it cannot confirm the identity of a website.
