← Back to all posts

Why curl Reports Error 60 for Revoked Certificates on Ubuntu

Read curl's TLS verification reason and check Ubuntu's upki data before deciding whether to fix a CA chain, an expired certificate, or a revoked one.

A purple envelope with a gold lock and three cryptographic cards

A monitoring script that made a successful HTTPS request on Ubuntu 26.04 can report curl: (60) on Ubuntu 26.10. Read the verification reason following the exit code. If it says certificate revoked, the TLS client has found revocation evidence for the certificate it evaluated. Reinstalling a CA bundle addresses a different condition.

Ubuntu’s November 10, 2026 engineering note describes the integration of upki with the distribution’s curl and OpenSSL packages in Ubuntu 26.10. The check uses locally available revocation data. The recommended upki package refreshes the data in the background, and the first successful data fetch matters for a fresh machine or image. Ubuntu’s upki demonstration

Capture the client and the verification reason

Run these commands on the same machine or in the same image as the failing script. Use an endpoint you administer or are authorized to check.

curl --version
dpkg-query -W -f='${db:Status-Abbrev}\t${Package}\t${Version}\n' curl upki
curl -v -o /dev/null https://service.example/

Replace service.example with the actual hostname. Record the time, curl version and TLS backend, and the verification message. For an authenticated script, make the first diagnostic request without credentials if the TLS handshake can be checked that way. Verbose logs can contain headers and other sensitive details.

Verification reason What to inspect
Certificate revoked Identify the presented certificate and the endpoint or proxy serving it. Replace the revoked certificate and verify the replacement on the affected client.
Unable to get local issuer certificate Check the intermediates sent by the server and the client’s trusted CA configuration.
Certificate has expired Check the certificate dates, client clock and renewal deployment.

The curl exit code groups these conditions under peer verification failure. Upstream curl also supports mechanisms such as --crlfile with compatible TLS backends and --cert-status for stapled OCSP on supported backends. Those options have their own prerequisites. Ubuntu’s upki integration is a distribution behavior, so check the binary actually invoked by the automation. curl FAQ and curl manual

Check whether the client has revocation data

On a systemd-based Ubuntu 26.10 host with upki installed, inspect the timer and latest fetch result.

systemctl list-timers --all upki-fetch.timer
journalctl -u upki-fetch.service -n 20 --no-pager

A minimal container image may have a different package set or lack a running systemd instance. Inspect the image’s packages and update mechanism directly. A clean connection on another machine only proves that the other client’s checks accepted what it saw.

An isolated OpenSSL 4.1.0 check verified a locally issued leaf successfully. After the test CA revoked it, checking the same leaf against a newly generated local CRL returned error 23, certificate revoked. For a local test CA that already provides these files, the two checks are:

openssl verify -CAfile ca.pem leaf.pem
openssl verify -CAfile ca.pem -CRLfile ca.crl -crl_check leaf.pem

This explicit CRL check demonstrates the verification reason. Ubuntu’s engineering example checks the distribution’s upki integration by using the same local HTTPS server with different certificates. To evaluate the Ubuntu behavior, compare a known-good certificate and a revoked one while recording the client packages and data state.

When fixing a live service, repeat the original request after deploying the replacement across every relevant endpoint or proxy. The LabEx curl HTTPS exercise is useful for practicing the request and reading its TLS behavior.

References