Guzzle Curl Error 60 SSL unable to get local issuer

Guzzle Curl Error 60 SSL unable to get local issuer

  1. Blog
  2. 15 November 2026
  3. 4 min read

Stefan Bogdanescu

Founder & Senior Architect

Guzzle Curl Error 60 SSL Unable to Get Local Issuer

When you encounter curl error 60, reporting an "SSL certificate problem: unable to get local issuer certificate," your PHP client is refusing to connect because it cannot verify the server's identity. This specific failure mode often confuses developers because the underlying network connection usually works fine; the issue lies entirely in how the system validates the SSL handshake.

In the scenario described, a Symfony application using Guzzle attempts to hit https://www.googleapis.com. The error occurs on an Ubuntu 14.04 environment. While the URL and the YouTube API v3 endpoint are correct, the client is rejecting the certificate presented by Google. This typically happens when the local machine lacks the specific Root CA certificates required to build the chain of trust for that domain.

The Missing Trust Store

The core issue is almost always a missing or outdated Certificate Authority (CA) bundle. Modern SSL/TLS security relies on a hierarchy of trust. When your server requests a certificate from Google, it signs that certificate with an intermediate CA, which itself is signed by a root CA. Your system needs the root CA's public key to verify the chain back up to a trusted anchor.

On Ubuntu, these certificates are managed by the ca-certificates package. If this package was not installed correctly, or if it hasn't been updated since the certificate authority changed its root store (which happens periodically), your system won't recognize Google's signature as valid.

To fix this on an Ubuntu development environment, you must ensure the CA certificates are up to date:

sudo apt-get update
sudo apt-get install --reinstall ca-certificates

After running these commands, you may need to regenerate the bundle if the system has been misconfigured previously. You can verify that the local issuer is now recognized by checking the contents of /etc/ssl/certs/ca-certificates.crt. If this file is empty or incomplete, your SSL requests will continue to fail until it is populated with valid root certificates.

Guzzle and cURL Configuration

Guzzle relies on the underlying libcurl library to handle HTTP requests. When you configure a Guzzle client, it inherits the system's default certificate bundle path unless explicitly told otherwise. In most standard Linux installations, Guzzle will automatically look for /etc/ssl/certs/ca-certificates.crt.

However, if your application is running in a container (like Docker) or on a server where the default certificate location differs, you might need to provide an explicit path. You can do this via the verify option when creating the client:

$client = new \GuzzleHttp\Client([
    'base_uri' => 'https://www.googleapis.com',
    'verify'   => true // Defaults to true; set to '/path/to/custom-bundle.pem' if needed
]);

If you are using Service Descriptors in Symfony, ensure that the Guzzle client associated with your service descriptor is instantiated with these default settings and hasn't been configured to skip verification. Explicitly setting verify to false resolves the error but opens a massive security vulnerability by allowing man-in-the-middle attacks. You should never disable SSL verification in production or even on development machines unless you are debugging a specific internal certificate issue.

Environment-Specific Considerations

The fact that this is running on Ubuntu 14.04 adds a layer of complexity. This version of Ubuntu is End of Life (EOL) and no longer receives security updates, including those for OpenSSL and CA certificates. If you have recently updated your system or if the CA bundle was not updated when the transition to new root CAs occurred, older versions of libcurl bundled with that OS might lack the necessary trust anchors.

If updating the package doesn't resolve it immediately, you can manually download the latest CA bundle from a trusted source like Mozilla's Root Store and copy it to your expected location:

sudo wget https://cacerts.mozilla.org/certificates/root.crt -O /tmp/root.crt
sudo cp /tmp/root.crt /etc/ssl/certs/ca-certificates.crt

This forces the system to trust the current root CAs immediately. While moving to a supported OS like Ubuntu 20.04 or 22.04 is the long-term solution, this manual intervention gets you back online while maintaining your legacy stack.

Conclusion

The error is not a bug in Guzzle or the YouTube API; it is a standard security rejection from your operating system. By ensuring that your ca-certificates package is current and that your libcurl library can access the correct trust store, the SSL handshake will complete successfully, allowing your Symfony application to retrieve video data without throwing a CurlException.

Our network