This repository was archived by the owner on Feb 5, 2026. It is now read-only.
Replies: 1 comment
-
|
This is a TLS certificate role issue or a problem with your CA. You are probably using a certificate that is marked as a CA (i.e. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey there, I am new to this rye tool, it was recommended by the colleague of mine, but ever since I install it I am facing issues with certificate. Even I am on Windows platform, I have set up the env variables that are redirecting directly the company certificate (SSL_CERT_FILE, PIP_CERT, REQUESTS_CA_BUNDLE). All three variables are set up to same certificate, even with that I tried multiple set of options to apply on the rye but it was not helpful at all. Below I will try to display configuration of rye and error that I am getting, I hope that someone will know how to fix it because I spent two days on this issue and to be honest I am losing my mind a little bit 😄
Config:
[behavior]
use-native-tls = true
user-ca-store = "~/.rye/certs/rootcaCert.pem"
global-python = "true"
Terminal:
$ rye sync
Reusing already existing virtualenv
Generating production lockfile: C:\Users\firstname.lastname\IdeaProjects\app\requirements.lock
× Failed to fetch:
https://pypi.org/simple/black/├─▶ Request failed after 3 retries
├─▶ error sending request for url (https://pypi.org/simple/black/)
├─▶ client error (Connect)
╰─▶ invalid peer certificate: UnknownIssuer
help: Consider enabling use of system TLS certificates with the
--native-tlscommand-line flagerror: could not write production lockfile for project
Caused by:
Failed to run uv compile C:\Users\firstname.lastname\AppData\Local\Temp.tmptiysby\requirements.txt. uv exited with status: exit code: 1
Beta Was this translation helpful? Give feedback.
All reactions