1
0
mirror of synced 2025-12-22 03:16:52 -05:00

Remove mentions of restricting custom certificates to CfB (#49355)

Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com>
This commit is contained in:
Devraj Mehta
2024-02-26 06:37:55 -05:00
committed by GitHub
parent fe924aebb3
commit ded2774cdb
5 changed files with 1 additions and 28 deletions

View File

@@ -59,12 +59,6 @@ If you know you are connecting via a proxy, make sure the proxy is configured co
Depending on your proxy setup, you may encounter errors like "certificate signature failure," "custom certificate," or "unable to verify the first certificate." These errors are usually caused by a corporate proxy setup that uses custom certificates to intercept and inspect secure connections.
{% note %}
**Note:** {% data variables.product.prodname_copilot %} only supports custom certificates if you have a {% data variables.product.prodname_copilot_business_short %} or {% data variables.product.prodname_copilot_enterprise_short %} license. For more information, see "[AUTOTITLE](/copilot/about-github-copilot)."
{% endnote %}
Some possible ways to resolve certificate-related errors are:
- Configure a different proxy that does not intercept secure connections.
- If you are using a corporate proxy, contact your IT department to see if they can configure the proxy to not intercept secure connections.