“The certificate for this server was signed by an unknown certifying authority” (NSURLErrorDomain -1203) on Mac

The Mac does not know the authority that signed the certificate. A private authority, a self-signed certificate or a missing link in the chain causes this.

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

My Mac has this problem: “The certificate for this server was signed by an unknown certifying authority” (NSURLErrorDomain -1203) on Mac. Read https://kilobat.app/guides/nsurl-error-1203-certificate-signed-by-an-unknown-certifying-authority.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 was signed by an unknown certifying authority.”
  • Console shows NSURLErrorDomain Code=-1203.
  • The same site can open on another device or network.

Likely causes

  • A self-signed certificate. A test or internal server signs its own certificate.
  • A private authority. A company root is not in the Mac trust store. See Corporate proxy certificates break Terminal tools on a Mac.
  • A missing intermediate certificate. The server did not send the full chain.
  • An interceptor on the network. A filter signs traffic with its own authority.

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. For a company network, install the company root certificate and set it to trusted, as the administrator tells you.

  2. If the server is yours, send the full chain, with the intermediate certificates.

  3. For a local test server, use a certificate that you trust on this Mac.

  4. Do not trust an authority that you do not know.

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.

Questions

Where do I trust a root?

Use Keychain Access. Double-click the certificate, open Trust, and set When using this certificate. Follow your administrator.

Is a self-signed certificate unsafe?

It is fine for your own test server. Do not trust one on a site that you do not run.

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.