Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Still not able to run uv on corporate network with custom root certificates (uv 0.0.11) #2020

Closed
carlosjourdan opened this issue Feb 27, 2024 · 3 comments
Labels
network Network connectivity e.g. proxies, DNS, and SSL question Asking for clarification or support

Comments

@carlosjourdan
Copy link

#1474 was not fixed by #1512 for me on v 0.1.11

Corporate network with ssl inspection firewall, custom ca on every site. Root certificate is trusted by windows, and environment variables REQUESTS_CA_BUNDLE and SSL_CERT_FILE are setup. Python requests work fine. Pip install as well. uv fails with error below.

error: error sending request for url (https://pypi.org/simple/zeep/): error trying to connect: invalid peer certificate: UnknownIssuer
  Caused by: error trying to connect: invalid peer certificate: UnknownIssuer
  Caused by: invalid peer certificate: UnknownIssuer
@zanieb
Copy link
Member

zanieb commented Feb 28, 2024

We do not respect the REQUESTS_CA_BUNDLE variable, what do you set that to? We do respect SSL_CERT_FILE but if your certificate are registered with the Windows certificate store then that should not be necessary.

It may be worth seeing if there are any upstream rustls-native-certs issues that apply to your situation and confirm that your certificates are available through the schannel API.

All of the certificate loading and validation is done outside of uv, generally these issues are a problem with the certificate configuration or an upstream bug.

@zanieb zanieb added the question Asking for clarification or support label Feb 28, 2024
@carlosjourdan
Copy link
Author

Thanks for the info @zanieb

I'm unable to replicate the issue now, it was probably something transient within the host environment

@zanieb zanieb added the network Network connectivity e.g. proxies, DNS, and SSL label Feb 28, 2024
@LordFckHelmchen
Copy link

LordFckHelmchen commented Sep 2, 2024

For me, the --native-tls option did the trick

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
network Network connectivity e.g. proxies, DNS, and SSL question Asking for clarification or support
Projects
None yet
Development

No branches or pull requests

3 participants