cURL error 60: ssl certification issue when attempting to use symfony

cURL error 60: ssl certification issue when attempting to use symfony

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

Stefan Bogdanescu

Founder & Senior Architect

cURL error 60: SSL certificate issue when attempting to use symfony

When you run php symfony new blog on a freshly installed Windows machine, receiving a GuzzleHttp\Ring\Exception\RingException with the message "cURL error 60: SSL certificate problem: unable to get local issuer certificate" is a common friction point for developers jumping from Linux or macOS environments. This isn't an issue with the Symfony framework itself or the underlying PHP installation; it is a mismatch between how cURL handles SSL verification on Windows and the state of your system's root certificate store.

The error occurs because the symfony new command relies on the CLI to download packages from Packagist, which uses HTTPS. The Guzzle HTTP client, used internally by Symfony's console application, defaults to strict SSL verification (CURLOPT_SSL_VERIFYPEER). On many Windows installations, particularly those using older versions of PHP or specific configurations, the system does not automatically include the root certificates required to validate the certificate chain issued by trusted authorities like Let's Encrypt or DigiCert. Without these, cURL rejects the connection even if your internet connection is perfectly fine.

To resolve this without reinstalling PHP or upgrading the OS, you must explicitly tell cURL where to find the CA bundle containing those root certificates. The most robust method involves modifying the cURL options in your environment so that it points to a valid CA bundle file.

You can achieve this by setting the REQUESTS_CA_BUNDLE environment variable. This variable is specifically designed for PHP environments using Guzzle and RingPHP to bypass the default system certificate store lookup in favor of a specific, trusted CA bundle. You can create a text file named cacert.pem containing the certificates (often available from the official curl website or your system's existing certificate store) and point the environment variable to it.

In Windows Command Prompt, you would run:

set REQUESTS_CA_BUNDLE=C:\path\to\cacert.pem
php symfony new blog

Alternatively, if you are using PowerShell, which is standard on modern Windows versions, you can set the variable in your session or permanently by editing your shell profile. This approach ensures that every subsequent command executed in that terminal session respects the correct certificate store.

Another option available to you is passing the --no-check-certificate flag directly to the curl command used internally by Guzzle, though this is less secure as it disables verification entirely for all requests. While technically accurate, relying on --no-check-certificate introduces security risks if your application later makes external API calls that could be intercepted or spoofed. It is generally better practice to fix the root cause—missing certificates—rather than disabling security checks.

If modifying environment variables feels cumbersome in your specific workflow, you can also configure this within a php.ini file by adding the curl.cainfo directive pointing to your CA bundle path. However, note that REQUESTS_CA_BUNDLE is often preferred for CLI applications like Symfony because it overrides system defaults more predictably without needing a restart of PHP services.

If you are unsure how to obtain the correct cacert.pem, you can download it directly from the official cURL website or extract it from your existing installation if you have tools like OpenSSL installed. Ensure that the file path in your environment variable contains no spaces or use quotes around the path to prevent parsing errors, especially in PowerShell scripts.

By explicitly defining the CA bundle, you align your Windows environment's behavior with Linux counterparts, ensuring that php symfony new proceeds to create your project without SSL handshake failures. This distinction is vital for maintaining consistency across development environments and avoiding "it works on my machine" scenarios that plague many distributed teams.

Our network