“curl: (35) SSL connect error” on Mac
curl exit code 35 reports a failed step. The curl documentation says: “A problem occurred somewhere in the SSL/TLS handshake.”
My Mac has this problem: “curl: (35) SSL connect error” on Mac. Read https://kilobat.app/guides/curl-35-ssl-connect-error.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.
Symptoms
- Terminal shows
curl: (35) SSL connect erroror a longer message such asLibreSSL SSL_connect. - The connection opens, but the secure handshake fails.
- Scripts stop with exit code 35.
Likely causes
- A proxy or filter. A proxy or security app that inspects TLS can break the handshake.
- A wrong port or scheme. The URL uses https on a port that serves plain HTTP.
- A wrong clock. A clock that is far off breaks certificate checks.
- A server TLS fault. The server can use a TLS setup that curl does not accept.
How to check
Run curl with details. The error buffer text pinpoints the problem.
curl -v https://example.comCheck the date.
dateTest the handshake with OpenSSL.
openssl s_client -connect example.com:443 -servername example.comTry
http://to test the port.
How to fix it
Use the right scheme and port.
Set the clock to automatic under
System Settings › General › Date & Time.Turn off TLS scanning in security software for a short test. Turn it on again after.
Try another network.
With Kilobat
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.comThese Kilobat checks are free. AI agents run them through MCP with
diagnose_connectionanddiagnose_network. See Find why one site or API won't connect.
Questions
Why read the error text with curl -v?
The curl documentation says that the error buffer message pinpoints the problem more closely.
Is (35) the same as (60)?
No. Code 35 is a handshake failure. Code 60 is a failed certificate check. See “curl: (60) SSL certificate problem” on Mac.
Sources
Checked on 29 October 2026.