“curl: (60) SSL certificate problem” on Mac

curl exit code 60 reports a failed step. The curl documentation says: “The remote server's SSL certificate or SSH fingerprint was deemed not OK.”

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

My Mac has this problem: “curl: (60) SSL certificate problem” on Mac. Read https://kilobat.app/guides/curl-60-ssl-certificate-problem.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: The curl that comes with macOS and the Homebrew curl, on all current macOS versions.Checked: 29 October 2026

Symptoms

  • Terminal shows curl: (60) SSL certificate problem: unable to get local issuer certificate.
  • The text can also say “self signed certificate”.
  • The same address may open in a browser.

Likely causes

  • A TLS-inspecting proxy. A work proxy signs traffic with its own certificate. See Corporate proxy certificates break Terminal tools on a Mac.
  • A self-signed certificate. A local server or device uses a certificate that no trusted authority signed.
  • A wrong clock. A far-off date makes a valid certificate look expired.
  • A missing intermediate. The server may not send the full certificate chain.

How to check

  1. Read the certificate issuer.

    curl -v -o /dev/null https://example.com 2>&1 | grep -i issuer
  2. Check the date.

    date
  3. Test the same address in a browser. Compare the issuer.

  4. Show the certificate chain.

    openssl s_client -connect example.com:443 -servername example.com -showcerts

How to fix it

  1. Set the clock to automatic under System Settings › General › Date & Time.

  2. For a private authority, point curl at its certificate.

    curl --cacert /path/to/ca.pem https://example.com
  3. On a work Mac, ask the administrator for the proxy root certificate.

  4. Do not use -k or --insecure in scripts. It turns off the check.

With Kilobat

  1. Kilobat's connection doctor tests the address layer by layer: network, proxy, DNS, rules, IPv4, IPv6, TLS and the server. It names the layer that failed.

    kilobat why https://example.com
  2. These Kilobat checks are free. AI agents run them through MCP with diagnose_connection and diagnose_network. See Find why one site or API won't connect.

Questions

Is it safe to use curl -k?

It turns off certificate checks. Use it only to test a server that you run, never in scripts.

Why does the browser work?

The browser may trust a certificate that curl does not. Compare the issuer.

Sources

Checked on 29 October 2026.