-
Notifications
You must be signed in to change notification settings - Fork 913
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
error trying to connect: invalid peer certificate: UnknownIssuer - Even with SSL_CERT_FILE mapped #1819
Comments
Thanks for the report! I'm not sure what's going on here, it's all upstream of us now that we're using Related: |
No worries, will keep my eyes open for the |
If there's any way you can help us reproduce the issue or investigate with verbose logs e.g. |
I have attached a snippet of the log below, it appears to be failing to connect here, it cycles through this several time before returning the error.
Also to confirm that |
Resolved, appeared to be an issue with certificate mapping my end. Sorry! |
Quick work around is to activate the environment and configure the SSL_CERT_FILE enviroment variable and then run the command:
|
Hey, I saw #1474 should have resulted in uv being able to work via SSL_CERT_FILE, but when running.
I am still encountering
I have validated that my trust store and environment variables are correctly mapped, should the merge for 1474 not have fixed this?
Using uv has a lot of scope to speed up so many internal package deployments so would be very keen to get to test this further.
Thanks for all the great work so far on it!
The text was updated successfully, but these errors were encountered: