Skip to main content

Troubleshooting certificate errors for GitHub Copilot

Troubleshooting help for certificate-related errors.

GitHub Copilot est disponible pour les clients GitHub disposant d’un compte personnel sur les organisations GitHub.com et GitHub Enterprise Cloud appartenant à un compte d’entreprise.

L’utilisation de GitHub Copilot est gratuite pour les étudiants, enseignants et responsables vérifiés de projets open source. Si vous êtes ni étudiant, ni enseignant, ni responsable d’un projet open source connu, vous pouvez essayer GitHub Copilot gratuitement avec une version d’évaluation de 60 jours. Après l’évaluation gratuite, vous aurez besoin d’un abonnement payant pour continuer à l’utiliser. Pour plus d’informations, consultez « À propos de la facturation pour GitHub Copilot ».

Depending on your proxy setup, you may encounter errors like “certificate signature failure”, “self-signed certificate”, or “unable to verify the first certificate”. These errors are usually caused by a corporate proxy setup that intercepts secure connections, terminates the secure connection to GitHub, and instead uses a self-signed certificate to act like a TLS middleman. Support for this type of proxy is not available for all GitHub Copilot licenses. Possible ways to resolve this issue are:

  • If you are using a corporate proxy, please contact your IT department to see if they can configure the proxy to not intercept secure connections.

  • Properly install the proxy certificates on your machine in the OS trust chain.

    Note: This requires a GitHub Copilot for Business subscription. For more information about GitHub Copilot for Business, see "About GitHub Copilot for Business" in the GitHub Enterprise Cloud documentation.

  • Configure a different proxy that does not intercept secure connections.

  • Configure GitHub Copilot to ignore certificate errors.

    Warning: Ignoring certificate errors is not recommended, since it might cause security issues.