---
title: "The certificate for this server has expired (NSURLErrorDomain -1201) on Mac · Kilobat Guides"
url: "https://kilobat.app/guides/nsurl-error-1201-certificate-for-this-server-has-expired"
description: "An app shows The certificate for this server has expired, error -1201. Check the Mac date first, then the server."
---

# “The certificate for this server has expired” (NSURLErrorDomain -1201) on Mac

The certificate is out of date, or the Mac thinks that it is. A wrong Mac clock is a common cause.

**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 has expired” (NSURLErrorDomain -1201) on Mac. Read https://kilobat.app/guides/nsurl-error-1201-certificate-for-this-server-has-expired.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 has expired.”
- Console shows NSURLErrorDomain Code=-1201.
- The same site can open on another device or network.

## Likely causes

- **A wrong Mac clock.** The Mac date is later than the real date.
- **The server did not renew its certificate.** The site owner must fix it.
- **An old certificate that a proxy presents.** A filter can show its own certificate.

## 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. If the date is right, tell the owner of the site or the API.
3. Try another network.
4. See [NET::ERR_CERT_DATE_INVALID in Chrome on Mac](https://kilobat.app/guides/err-cert-date-invalid) for the same cause in Chrome.

## 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 does the Mac clock matter?**

The Mac checks the dates on the certificate against its own clock.

**Can I wait?**

If the server certificate has expired, only the site owner can fix it.

## 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.
- [“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.
- [“The certificate for this server is not yet valid” (NSURLErrorDomain -1204) on Mac](https://kilobat.app/guides/nsurl-error-1204-certificate-for-this-server-is-not-yet-valid): The certificate starts later than the date that the Mac knows.
- [Corporate proxy certificates break Terminal tools on a Mac](https://kilobat.app/guides/corporate-proxy-certificates): Some company networks inspect HTTPS traffic.
