{% endhighlight %}

If your builds are failing with`Failed to validate connection to Docker daemon; caused by Error: certificate has expired`, you can verify if your certificates have expired, and if needed replace them.

See[Troubleshooting this error on ArtifactHub](https://artifacthub.io/packages/helm/codefresh-onprem/codefresh#error-failed-to-validate-connection-to-docker-daemon-caused-by-error-certificate-has-expired){:target="\_blank"}.

If your builds are stuck in Pending or failing with`Failed to validate connection to Docker daemon; caused by Error: certificate has expired`, you can verify if your certificates have expired, and then replace them if needed.

* Re-apply the[`cf-runtime` helm chart](https://artifacthub.io/packages/helm/codefresh-runner/cf-runtime){:target="\_blank"}.

Post-upgrade, the`gencerts-dind` Helm hook regenerates the DinD certificates using a new CA (Certificate Authority).

1. Delete`codefresh-certs-server` k8s secret;

2. Download[`./configure-dind-certs.sh` script](https://github.com/codefresh-support/cf-utils/blob/master/configure-dind-certs.sh) and run it:

[Codefresh platform deployment]({{site.baseurl}}/docs/installation/installation-options/)

[Codefresh on-premises deployment]({{site.baseurl}}/docs/installation/on-premises/codefresh-on-prem/)

[Codefresh API]({{site.baseurl}}/docs/integrations/codefresh-api/)